So why aren't we doing it? Because it's a stupid idea. We still want noon to be when the sun is overhead, and midnight to be the middle of the night. Internet be damned, it's arbitrarily more convenient for most people, because most people don't travel all that often, and spend most of their time in their local time zone.

Try EAC, it will compensate for differences in drives to ensure a perfect digital rip every time.

With crappier rippers maybe. With a direct digital rip, it should be the same every time, in theory, from any CD drive.

Exact Audio Copy uses the AccurateRip system which somehow manages to tell me that my rips are exactly the same as hundreds of other random people via some central DB. The only time it doesn't match up, is when I have a massive scratch in a very old CD, and EAC took hours ripping and re-ripping the same sector to get the best results possible with what I gave it to work with.

One file may be legal for one person, and illegal for another. For example, if you rip your CD yourself, the resulting MP3 is legal. Copy the same MP3 onto a friend's computer, and it's illegal. I don't think such a software is even possible to write. Every pirated / illegal MP3 file would have to be already watermarked as such in order for the software to function. What if the "common" version of the file floating around on Napster was just a basic 128Kbps rip with a common MP3 encoder, and you used the same encoder to rip the same song from the original CD yourself? In theory, it is very possible that the resulting MP3 is bit-for-bit the same as the one millions of other people pirated from Napster, even though you own the original CD and ripped the file yourself.

They likely could be PCI compliant by claiming that "old versions" were still secure and any "known" issues had their fixes backported. The whole PCI compliance thing is just a bunch of crap in my experience, where somebody magically decides that old versions are automatically vulnerable, so using the latest RHEL or CentOS won't automatically pass compliance. You have to file exceptions for everything saying fixes are backported. They just take your word for it and sign off, letting you basically claim compliance no matter what.

Run a binary diff on the original, or even just a fc /b from a command prompt, and you'll find that most no-cd cracks only change a handful of bytes at best. Sometimes they remove a large chunk of code entirely. I've never actually seen substantial modification or additional code added to the exe with "legit" cracks.

Nova is probably what I remembered that from, as I don't watch a whole lot else.

Isn't this the flight that flew right into a huge huge storm that was obscured on their radar by a smaller storm which was safe enough to fly through. As soon as the larger storm was in view, it was too late to change course and fly around it. I heard the most likely case is extreme icing of the sensors that monitor airflow, causing autopilot to disengage as the plane no longer knew its own speed. Without any way to know the current speed, the plane lost altitude and crashed, due to a small window of safe speeds that don't result in altitude loss.

So my only choices for smartphone development are Objective C or Java? Seems like a lose-lose situation to me. Why can't I use native C or C++ on either of them?

Seems like STARTTLS would solve this problem. I know that STARTTLS is preferred for pop3/imap/smtp over using the pop3s/imaps/smtps ports.

I was thinking more like Volcano in New York or something equally as stupid.

Windows 98 (but not 95 or 95 OSR2) has this feature in the system Help (winhelp.exe). I have every old version of Windows in VMware, in their default install state with auto-revert.
Just load a fresh Win98 install, press F1, and go to the Search tab. Whatever you search for is highlighted in blue in the help topic that appears on the right side.
The Options button at the top can disable this if you select "Highlighting Off" and you can turn it back on by selecting "Highlighting On"
winhelp.exe is dated May 11, 1998. Must be prior art.

I've seen that on cheap PS/2 keyboards too. It's really annoying when you can't even type a 3 letter word like TWO without it coming out as WTO every single time. At first I thought I was crazy, but it's very reproducible if you type fast.

Or be a gamer. I've had similar issues on cheap keyboards, even PS/2 ones though. Try to hold up+left to walk forward while strafing left and then press Ctrl to duck and shift to disable run so you sneak slower. Oh wait, you can't because that's too many keys down at once and now your computer stopped to issue a PC speaker BEEP!! and lag your game for a second or two.

Unfortunately, in many BIOSes, you need to use a PS/2 keyboard to even get into the BIOS to change that setting. They've probably fixed that on newer motherboards, but I don't know. I still use PS/2 keyboards exclusively.