What's your strangest computer-related error?

Recommended Videos

Formica Archonis

Anonymous Source
Nov 13, 2009
2,312
0
0
Sassafrass said:
Oh, and my key-baord keeps switching from English key settings to American settings for some bizarre reason. " becomes @ and vice versa and ~ becomes |. It's annoying when writing a review and you look up only to see half the sentence is rubbish. :p
Sounds like you have multiple input languages. What version of Windows? If XP, Control Panel/Regional and Language Options/Languages/Details and then remove the keyboard layouts that don't match yours.
esperandote said:
Once upon a time when FAT32 system was around i couldn't get a PC to read a secondary HDD with NTFS because FAT32 doesn't recognize NTFS
You mean that older OSes can't recognize NTFS? Because XP on a FAT32 partition doesn't mind if you have drives with NTFS.

esperandote said:
I recently replaced a Computer System made with Office 97 because it didn't work on computer with 1GB RAM or more so my client used to have to change RAM memories from his new computers from 1GB to 512+256MB
Windows 98? My nVidia driver did that. Easier solution: mask off the excess RAM. There's a win.ini or system.ini option for that. Worked well - dual boot, 98 saw 512 Mb of RAM (plently for 98!) and XP saw the whole gigabyte.

I fix PCs for a living; I stopped keeping track of weirdness long, long ago. Most memorable recent incident? Turned on a PC that had been working for days (and passed every test we could throw at it) to demonstrate it to a customer, and halfway through XP booting the power supply LIT UP (pure white light out of every hole) and made a loud BZZZZZZZZZZZZZZZZZZZZZZZ sound (like vacuum cleaner loud), then the computer went off. Oddly enough, it was only the power supply that died. Usually spectacular PSU failures take something with them. (Edit: Not an error per se, but still.)

Grubnar said:
"ERROR: There was no error."

To this day I have no idea what that means.
Simple. Error-handling was rather stupid. It thinks there's an error, so it calls the error display routine, which screams ERROR and then checks a variable and outputs the contents. But since there was no error, that's all it reports. You see this in DOS or Windows sometimes, with an "ERROR 0: The operation completed successfully." because the handler's too stupid to realize that errorlevel 0 is "no error".