Lessons Learned (Volume 1)
Or, rather: Lessons Learned in the least convenient way possible, in the most painful manner possible, with the maximum amount of stress, time pressure, and personal agony.
Chapter 1: January
This January, in the middle of composing my Division III (essentially my final project of college), my biggest hard drive, upon which all my archives and stored data resided, blew its servo. I had the data, still, but it was inaccessible- mechanical failure of a bizarrely non-destructive type. Unfortunately, this occurred at the same time that my power supply quite literally exploded, taking the motherboard with it. If you’ve never seen a power supply explode, it’s quite a sight- bright lights start flashing inside it, popping and sizzling sounds are emitted, and everyone in the room reacts according to their experience with said event. If you’ve EVER seen it happen, you practically dive across the room in bullet-time, praying that you’ll be able to yank out the power cord before the PSU fries everything it’s connected to. If you haven’t seen it before, you stand there, thunderstruck by the awesome power of unleashed electricity, much like the people who watched Thomas Edison electrocute an elephant as a graphic demonstration of why he was both more clever and infinitely more of an evil asshole than Nikolai Tesla. Where was I? Right, power supplies. So the servo in the drive died, and that was it. I let it sit around for the next eight months while I, in order: Lost over a month of worktime due to the aforementioned incident, dealt with (more like ignored, heh) a supremely uncooperative Div III committee, and somehow managed to complete my Div III on time and graduate (!).
Chapter II: Nine Months Later
Nine months later, I’m fully in the Real World, working the same job I’ve had for the last four years, using absolutely nothing I paid to learn in college (in fact, the skills I’m using are the ones I WAS PAID TO LEARN by working for Hampshire IT!). I decided that, hell, since we do data recovery, why not avail myself of ye olde employee-e discounte? Favors are called in and three days later, I have my data back. I copy it to my current storage drive… and hilarity of hilarities, IT DIES. I’ve already called in all the favors that I had, so this one’s my problem. Utilizing some truly space-age, very proprietary software, I manage to discover exactly what’s wrong with the drive- there’s a big ‘ol fat patch of horribly corrupted data about 60% of the way through… right in middle of where I copied my recovery!
So what happened?
During the entire time I’d had this particular drive, (since January, actually) I had never actually filled it all the way up. I had about 2-300GB of data sitting on it, so I hadn’t even gotten it half full. But the recovery was around 400GB, which pushed me up to ~800GB out the terabyte available. This means that the corruption was probably a defect in the actual drive itself- I had just never noticed it because nothing had ever gotten that far into the drive yet.
I know this isn’t literally how hard drives work, but consider this- if that patch was corrupted and throwing out CRC errors whenever it was read, any writes to that patch would just fail over to a different sector… unless there was no other space left, in which case they would be ‘written’ to the bad patch and promptly disappear into the nether.)
Amazingly, the way that this drive had failed was, actually, not a problem. The data from before the recovery was copied over was 100% fine, and I had that recovered data on another drive, as well. I could copy the recovery from the second drive, and the original data from the corrupted drive, and as long as I had a third drive to merge those two datasets onto, everything would be great.
The Great Copy
New drives in hand, I set out to transfer all my data to the virgin media… and man, it’s taking a long time. Even allowing for CPU overhead, my calculations say that this should be taking half as long as it is. Odd. Nothing to do but wait, though.
The first copy finishes and I shut down, remove the old drive, and reboot… and get this: BOOTMGR MISSING, PRESS CTRL+ALT+DELETE TO RESTART
Well, shit. However, I am an IT professional, so I just put everything back the way it was and reboot again. Everything comes up fine. Into the Disk Management extension!
Lots of people don’t realize that even the ‘user’ versions of Windows come with an astonishing array of cool and useful administrative tools that can fix pretty much any wierd problem that crops up for you. The Local Disk Mangement console lets you see exactly what WIndows thinks your disks look like, how they’re partitioned, and where you’re booting from.
It turns out that Windows 7 has some… interesting… ideas about where your bootloader should go. Instead of installing it on the drive where you installed Windows, it seems to take the lowest-indexed drive in the HDD hierarchy, and puts BOOTMGR there. If you’re like me, and are operating under the impression the SATA doesn’t care what order you connect your drives in, this can be VERY BAD.
In my case, I have no IDE drives, so Windows skipped them. But I had three SATA drives connected: User/ Misc, OS, and Storage, in that order. See the problem? User/ Misc was the lowest-index drive, so it got BOOTMGR, and the OS drive got nothing! This is all fine and dandy… until your replace User/ Misc or swap the order of the drives around, which will result in BOOTMGR MISSING.
Quiz time! Can you figure out why this happened? I’ll give you a hint- This is NOT the intended behavior, and I’ve already made some incorrect assumptions. In addition, there’s a GLARINGLY OBVIOUS clue that I missed.
…
…
…
What I missed:
The data transfer rate. Why was it so slow? If I had bothered to do some more math, I would have discovered that the data transfer rate between my two SATA drives was exactly the maximum transfer rate allowed by IDE drives… which meant that my SATA drives were emulating IDE drives! Why? My motherboard, like pretty much every motherboard that has onboard SATA, lets you set the SATA ports to one of three modes- Legacy, Chipset RAID, and AHCI. Mine was set to Legacy, for maximum compatibility. This means that the motherboard presents the SATA drives to the OS as IDE drives, in case the OS can’t use SATA drives properly. Because of this, when I installed Windows, it looked at the drives connected, and saw them as traditional IDE masters and slaves. In the case of IDE drives, connection order is of paramount importance, so placing BOOTMGR on the first Master was a no-brainer. My OS drive was showing as the first slave, so of course it didn’t get BOOTMGR.
Fixin’ It:
You’d think that the solution would just be to set the SATA drives to AHCI, (which lets them act like REAL SATA drives instead of emulated IDE drives) but unfortunately it isn’t that simple. If you do that, Windows bluescreens on startup. saying STOP 0x0000007B INACCESSABLE_BOOT_DEVICE.
According to Microsoft KB922976, Windows disables unused storage drivers after the first startup, to speed up boot. So when you switch over of AHCI, Windows can’t read the OS drive anymore, because it hasn’t loaded the right driver. The same article gives you a fix, though. It’s a simple registry tweak that re-enables the AHCI driver. Reboot again after doing that… boom, all fixed.
As to fixing the BOOTMGR problem, I’m not sure that you’d need to after setting the drives to AHCI, but just in case, you can use BCEdit, like Scott Hanselman and I did. (after a little more research, natch)
The Upshot:
Everything is now back in its place and much faster, too! I also got to blow out my case and rewire everything, so it was a good excuse to do some cleaning. I also got to learn more about Windows 7’s internals, and you can be SURE I’m going to have to do something like this again. It all came out of a boneheaded mistake that anyone could make, and it was quite hard to figure out exactly what had gone wrong, because there was no failure per se: It took a completely unrelated problem for me to even notice something was wrong!
I wonder how many people are running their expensive, multi-terabyte SATA drives in IDE emulation mode, and don’t even know it?
September 3rd, 2010. Duken Nukem Forever… release date confirmed. A day that will live forever in the annals of gaming history.
An Interesting Observation
Activision’s Infinity Ward debacle has, to date, cost them:
- The integrity of the Modern Warfare 2 team: IW is going to need major rebuilding if it’s going to put out a game any time soon.
- The confidence of the gaming public.
- Two proven high-level developers who command a high amount of personal loyalty, further proving their skill.
- 40% of the developers who actually worked on Modern Warfare 2.
- An ultimately fruitless lawsuit that EA will no doubt fight with every penny it can muster.
- Possibly $125 million in unpaid royalties and bonuses, but more likely a LOT of legal fees that’ll come to much the same number.
- Their CEO and President, Mark Griffith.
- A full dollar of share value.
Let this be a lesson to uppity publishers: You don’t just go stepping on committed people. These guys busted their asses and lived through hell to get this game to market. What makes you think that single-minded determination won’t be turned against you if you piss them off?
Anyone taking bets?
I Still Hate Roger Ebert
“Why are gamers so intensely concerned, anyway, that games be defined as art? Bobby Fischer, Michael Jordan and Dick Butkus never said they thought their games were an art form. Nor did Shi Hua Chen, winner of the $500,000 World Series of Mah Jong in 2009. Why aren’t gamers content to play their games and simply enjoy themselves? They have my blessing, not that they care.”
— Roger Ebert, “Video games can never be art”
Why do I want games designated as art? Well, Roger, do you remember something called the Hays Code? How about the Legion of Decency? No bells rung? Why don’t you go look up the history of censorship in the U.S. motion picture industry prior to 1968. The reason games need to be designated as art is this: artistic expression is protected under the Constitution.
Michael Jordan never demanded that basketball being designated art because nobody ever tried to censor basketball, or prohibit it from being played on moral grounds. Nobody ever tried to outlaw certain variations of chess on the grounds that they were objectionable. If someone tried to outlaw Mah Jong on the grounds that it promoted gambling, they’d be laughed out of the room.
Games, on the other hand, have faced all these challenges, and are holding on by the skin of their teeth. If the Ultimate Fighting Championship and “pro-wrestling” (both essentially legalized bloodsport) are legal, uncensored, and unchallenged, then games should enjoy the same acceptance. If I want to play Manhunt, a game centered around creating snuff films via brutally murdering people, I should be able to play it. I should be able to make it, too, and advertise it on television, just like the WWE and UFC get to do.
If someone says horse-racing is morally reprehensible, wonderful for them. That doesn’t mean they can decide to ban it or discriminate against people who enjoy it, though. The same should apply to games. If we’re looking at this from a moral standpoint, the horse-racer is worse than the person who plays Manhunt: The horse-racer actually goes and participates in the objectionable action, the person playing Manhunt just performs a grossly inaccurate simulation of the action.
Let me conclude simply: Roger Ebert, the reason games must be defined as art is because of people like you. Given half a chance, you’d erase them from the face of the Earth, leaving only your beloved film industry. That’s why we need the protection that art provides— so that we don’t have to live in your world if we don’t want to.
Rules?
Humans play games. Games, in the sense I’m referring to them, are activities with lists of actions that are acceptable and unacceptable (rules). We play two types of games, and I divide them by their manner of mediation. One is mediated by humans, aided or unaided by technology. This covers sports, tag, etc. The other category is that mediated by technology, with humans as a secondary. This could include modern fencing (as the word of a judge is inadequate when timing touches down to the hundredth of a second), but what fits better are video and computer games. Now, there are are always rules in games- Don’t go outside this area, don’t punch the ball-carrier in the mouth, and so on. In technologically mediated games, those rules can’t be broken. Even hackers and cheaters are still technically playing by those rules, they’ve just found unintended ways to interpret them. In normal games, people can break or ignore those rules, and it takes the player group at large to make sure people don’t.
Up until this point, all is well and good. But then things start to get wonky. People make up all sorts of ‘house rules’ for games, rules that run the gamut from ‘dad always plays green’ to ‘let the little kid win.’ These rules are arbitrary, and often specifically made to benefit one player at the expense of others. For example, the concept of the fighting game ‘scrub.’ He’s that guy that never learned one part of a gmae, or never got good at it, and so he always complains and calls you ‘cheap’ when you use it. Throw him while he’s blocking? “OMG, cheap!” Anti-air him out of a jump-in? “WTF, cheap shot.” In some cases, it gets so bad that whenever you hit him, for any reason, he’ll start whining and puling. Got news for you, scrubs: The things you call ‘cheap’ are in the game. They’re valid tactics, because if they weren’t, the developers wouldn’t have them in the game. Same thing goes for human-mediated games. Within the confines of the overall ruleset, ANYTHING GOES. ANYTHING. That means if I figure out a way to make you trip every time you serve in Badminton, and it doesn’t violate a pre-existing rule, I can go to town and use it as much as I want. It’s legal.
So why the heck am I writing this? Because I am sick and tired of people making up bullshit ‘fairplay’ rules in the middle of a game. If I am going around and hitting people with fake swords, in something that pretends to imitate medieval combat, I should be able to stab people. I shouldn’t have to back off when two people are having a ‘duel.’ That pure crap. Battle are won through subterfuge, trickery, and plain old dick-moves, like snakes in a general’s bed. You know all those people who fought ‘honorably,’ every time? Guess what happened to them? They died! They got shot in the back, because they had gotten so good with their own definitions of the rules that when someone else agreed to play by that set, they’d basically already lost. Tactical genius is changing the game without telling your opponent. If you play by the scrub’s rules, he’s already won.
Will Wiles’ blog, Spillway
http://willwiles.blogspot.com/2010/02/i-have-always-relied-on-strangeness-of.html
“It is not illegal to kill at the pole. There are no laws in Antarctica prohibiting it.”
John Benson shook his head as he stared down at the unprepossessing collection of articles on the steel morgue table. And this is how human life invariably ends. Benson glanced over at the doctor. “Vitaly, are you sure this is all?” The burly Russian shrugged and answered in heavily-accented but practiced English. “Is probable. Was very, very bad storm.” He chuckled, his beard spreading the sound through his whole face. “Still is bad storm. Which is why you are stuck here with us, asking questions about this man, stupid enough to wander around outside.” Vitaly shook his head and his voice took an almost mournful tone. “They come here, touristi… Not even knowing anything about weather, in their expensive polarfleeces.” He clapped John on the shoulder. “Come. Now is the time for honored Antarctic tradition.” John stood, cracking his back. “What, we commit his remains to the sea?” Vitaly laughed, then, a deep belly laugh that shook the surgical instruments in their cases. “Wahahaha, no no.” His face cracked into a gigantic smile full of improbably white teeth. “No, we get PISSED drunk, and stay so for next twelve hours. Is good fun!” Shaking his head, John followed Vitaly out of the impromptu morgue, leaving behind the slowly thawing mortal remains of someone who the researches insisted was a careless tourist, but John knew was an accomplished, retired SAS Combat Magician. As he walked the halls of the base, John Benson’s thoughts were dark. There’s seomthing rotten at the South Pole, and these guys are devoted to hiding it, even if it means killing someone that 99% of humanity would much rather just left have his way. He snorted. And I’m supposed to figure this mystery out? Yeah, right. Fat chance.
I feel a story coming on!
(Inspired by http://everything2.com/title/Things+nobody+tells+you+about+the+South+Pole)

