+1. I was confused by this story since I've been tethering with my iPhone 3GS just fine since I got it, and it was just like you said (turn it on and it works right away, zero hassles). I'm now amazed that Rogers enables tethering if most US providers don't...

Of course you must make sure tethering is included in your data plan, otherwise a big surprise will await you on your next bill.

GP is correct, read the rest of his post. All the info is there: an explanation of how the licensing system works, and how to fix it if you're stuck having to connect to XBL to acquire your licenses.

That reminds me, the one time I really screwed up a Linux machine was when I failed an upgrade of glibc on a running system (I was a unix newbie and didn't know what I was doing).

It's been more than 15 years but I still remember the overwhelming sense of panic when none of the standard utils worked anymore, so I could not undo what I just did.

That day I learned not to mess with the glibc symlink, and how to fix an unbootable system from a boot floppy. Good times... (not!)

Actually, I don't know why I didn't think of this before... It's possible that simply wrapping the iPad inside something like an InvisiSHIELD may be enough to weatherproof it for your uses, as it encloses the entire device.

Surely they will make a version for the iPad...

damn, I've been reading too much slashdot, I'm starting to write "your" when I mean "you're", grr!

Usually, if there's water on the touch screen, the touch input won't be responsive. You get missed inputs, or you can't drag the on-screen controls (because it thinks your multi-touching). I haven't seen phantom inputs. Wiping the water drops off the screen will take care of it... Maybe keeping a towel nearby is enough to deal with this.

You could probably simulate the problem by putting one or more drops of water on your iPhone screen, or by touching the screen with a wet finger. Controlled tests only, no need to use the phone in the shower :)

It doesn't work very well. Try to use your iPhone outside the next time there is a light rain... (it's not to bad but it's enough to be annoying!)

You do know that all console manufacturers impose a certification process on all games released, right? You cannot ship a broken console game and "patch it later" like you can do on PC.

There are exceptions of course; sometimes bugs just sneak past any amount of testing, especially multiplayer issues...

I totally agree with your post, but I have to play devil's advocate for a bit here: if they detect Quake3 and work around the bug this way, someone will post a story about how NVIDIA cheating in Q3 benchmarks, because if you rename quake.exe to quack.exe the FPS drops from 400 to 100. So either way, they can't win - someone will always complain. I used to write D3D and OGL drivers for a living (not for ATI or NVIDIA, no threats please!), so I'm all too familiar with these issues...

In this case, Q3 is fairly old (wow, 10 years!), and it is likely some other (more mainstream) game required a fix to be applied that happened to slow down Q3. If you *had* to pick a side, as a company, which one would you choose?

I think NVIDIA did the right thing, even if it "broke" Q3. If there is still a market for Q3, id will release a patch. Hell, anyone could fix it, id released the source for the entire game...