• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Adventures with Windows

lunatic59

Moderati ergo sum
Moderator
Jun 12, 2010
40,679
43,523
Pennsylvania
www.cmgd.net
Everybody has a Microsoft story where it seems that the Windows development team was run by Machiavelli and the Marquis de Sade.

Here's my latest.

Bought a new ultrabook (see this thread). Decided to breathe some new life into the old Acer and replace the 5,200 RPM WD HD with an SSD.

I would have liked to do a straight clone but the WD drive was 320 GB and the SSD was 250 GB and clonezilla was barking at me. Understand it was setup as dual boot between Windows 7 pro and Ubuntu 13.10 with grub2 as the bootloader.

I tried a couple of freeware clone utilities but they all came back as failing because of disk errors (another reason I wanted to replace the HD) even after running chkdsk. I finally just booted into Ubuntu and used GPartEd to copy the C: partition from the WD drive to the SSD. I was a little apprehensive about being able to copy the partition because even though chkdsk completed successfully, the Windows utilities still showed errors. Anyway, the partition copied and I swapped the SSD into the laptop.

Mind you, I had every expectation of having to run bootfix from the recovery CD but to my amazement, Windows started to boot. Of course the operative word here is "started" because halfway through the process I get a strange error message.

Code:
autochk program not found, skipping autocheck

At which point it goes into a bootloop. Thrills. Out to Google and after reading through MS technet, I found someone had posted the fix by using the repair CD to fire up regedit and remove the old drive letter assignments in the registry. Fix one successful.

Next up was not being able to check for updates. Big red "X" with a warning that the Windows Update Service couldn't start. But .... in the services manager it was shown as running. Nice. Again, back to Google and MS technet. This time I found the fix in an updated Intel Driver that I downloaded from HP's website because the driver on Intel's website wouldn't work.

In the end (I hope it's the end) it was worth it. With the old drive, it would take 00:42 to boot to the login screen and a full 01:30 to get tot he desktop. Now with the SSD it boots to login around 00:25 and I get the desktop at 00:47.

Anybody else got any twisted MS fix stories?
 
Not a twisted fix exactly, but one of those mysteries that gnaw away at you for days.

Why, on restarting a 64-bit Windows 7 system that shutdown normally the previous evening, are some of my <bleepbleep> Start Menu program's bereft of their icons??? Not all of them.... that would be too simple. Nope, just a seemingly-random selection which otherwise still work fine. It's just annoying. :mad:
 
Upvote 0
not sure if this counts but i remember using Windows ME. not sure i want to even think about that one again. Not quite fixes but some twisted error messages i've encountered. Windows 3.1 used to lag and become unresponsive when i would print any document to my then-new 'bubble-jet' Canon printer. soon after, it would start printing, but i'd hear a sound effect and 'ERROR: The operation completed successfully' would pop up with an OK button. it worked anyway, and it did say successful so i was amused that it would go to the trouble of giving me an 'error' dialog. Windows 95, due to a driver problem with the Ethernet NIC card at random, would, on startup, say 'Windows has detected an undetectable error [OK]'.
 
Upvote 0
I don't have a lot to add to this thread from personal experience--I've tried to purge my brain of all the agony window$ caused it when I had the displeasure of administering some window$ boxes. But here are a few quotes I've gathered over the years; I can't vouch for the error messages actually being real--they may have been made up by fellow *nix lovers. :D

- Your mouse has moved. Windows NT must be restarted for the change to take effect. Reboot now? [ OK ]

- Windows NT encountered the following error: The operation completed successfully.

- The nice thing about Windows is - It does not just crash, it displays a dialog box and lets you press 'OK' first.

- Failure is not an option - it comes bundled with Windows.

- Q: How many Microsoft Programmers does it take to screw in a lightbulb?
A: It cannot be done. You will need to upgrade your house.

- "When you say 'I wrote a program that crashed Windows', people just stare at you blankly and say, 'Hey, I got those with the system, *for free*'." -- Linus Torvalds

:laugh:
 
Upvote 0
Have you tried turning it off and then on again?


Honestly I just remember the progress bars that used to go backwards sometimes. Priceless.



Kinda unrelated but this was the only funny windows pic I had:

(Some NSFWish text)

xv1rY4c.jpg
 
  • Like
Reactions: jefboyardee
Upvote 0
I've still got my favourite adventure with Windows this year...

wol_error.gif
This image has been resized. Click this bar to view the full image. The original image is sized 749x284.
900x900px-LL-a8a26796_windows8activate.jpeg


"Sure...go to a store that sells a Windows get genuine kit.... in China.. LOL... OK!
"Toto, I have a feeling we're not in Kansas any more." or Redmond for that matter. :rolleyes:"


Original post is here...
http://androidforums.com/computers/628602-windows-8-a-5.html#post5777945

Sufficed to say, I use Linux Mint or Mac OS X now. :thumbup:
 
Upvote 0
Never really had a lot of issues with Windows myself. Right now, it's installed for playing games that I could probably get to work through Wine but I don't have the time to screw with that
I never really had much problems either. I knew how to handle most of them.

The one error message I liked was:
Keyboard is not responding, Press any key to continue! :help:
 
Upvote 0
the actual message is '401 Keyboard not found, press F1 to continue'. the origin of this POST code is back during the old IBM PC days, and it's not as counterproductive as it sounds. in those days, if the keyboard came unplugged, this POST code would show up. believe it or not, you could actually reconnect the keyboard and press F1, as the code suggests, and continue. you did not have to power down first. that is why it says it like that.

While you can manage to get Windows-only games to run inside Wine, they play horribly even on good hardware. WINE lacks any support for anti-aliasing and DirectX so any games utilizing it run in very low resolution with lots of jagged-edges (jaggies) and framerates are horridly slow. it's not as much a problem for puzzle games, some platformers, and a sim like Rigs of Rods, but for fast-paced games like Call of Duty and First-Person-Shooters, and flight simulators, it's enough to use Windows if only to play those games until either it gets ported or until Wine gets updated.

I once had an IBM PS/1 PC (486SX/25MHz, 4MB RAM, 129MB HDD, Windows 3.1). the mouse came standard, of course, but if it was malfunctioning or not connected properly, you'd get an '1162 pointing device not found' POST code and it refused to boot. i was never sure why it 'required' the mouse. but it wouldn't work without one.
 
Upvote 0
Maybe it does represent the same issue. But these where Windows error messages.

unplugged-keyboard-error-funny-error-messages.jpg

"Keyboard not plugged"? That doesn't look right to me. "plugged" in this context is a transitive verb, meaning it has to be used with an object. "Keyboard not plugged in" is the correct grammar. It could also say "Keyboard is unplugged" where "unplugged" is an adjective.

TBH I didn't think Windows itself cared if a keyboard was present or not. It's the BIOS that does the keyboard detection.
 
Upvote 0
"Keyboard not plugged"? That doesn't look right to me. "plugged" in this context is a transitive verb, meaning it has to be used with an object. "Keyboard not plugged in" is the correct grammar. It could also say "Keyboard is unplugged" where "unplugged" is an adjective.

TBH I didn't think Windows itself cared if a keyboard was present or not. It's the BIOS that does the keyboard detection.

I wouldn't be surprised if there was some arcane 24 character limit for titles in message boxes in Win95.
 
Upvote 0
that keyboard error in Windows was Windows NT 4.0, not Windows 95. again, you could still plug it in without shutting the machine down, press F1 or F2 and go about your day. Windows NT 4.0 also had the 'press ctrl alt del to login' as well.

Computers might not enslave humanity if they ever become sentient. they might, however, flood our offices and homes with a deadly neurotoxin.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones