worm riders
well, i was going to say worm writers suck something, but I really have no words that can convey HOW MUCH YOU BASTARDS SUCK!
here I am, at work, trying to get a Win2K3 Web Edition test machine set up, and LESS THAN 30 SECONDS after getting it to recognize the ethernet card and plugging it into the network... BAM!
"The RPC process has unexpectedly quit. Your machine will now reboot."
F[iretr]UUUUUUUUUUUUUUUUUUUUUUUUUUUUUCKKKKK!
Thirty seconds. THIRTY MOTHERTRUCKIN SECONDS!
You bastards need to burn in the sun for 10000 years for this shit.
[UPDATE] It got better... due to some sort of networking problems (outside of the University) nobody here could get to www.micro$oft.com OR window$update.micro$oft.com. Makes it hard to get the patches, no?
So, upon confirmation that some of my friends in other states could access those sites, I decided to pull an old trick of mine to get the patches I needed. SSH into my friends' server in California.
Well... surprise surprise, Micro$oft's shitty websites are totally unusable unless you're on a Window$ machine running IE. Talk about inaccessible. What if I were a differently-abled sys-admin (uncommon/unlikely as that sounds)? I wouldnt be able to patch the holes in Micro$oft's shitty OS without using their own tools to access their shitty website.
So, what did I do? Since tech articles reside on support.micro$oft.com, I could read those, and look at the properties for the links to the downloads I needed. (downloads reside on www.micro$oft.com, which, you'll remember, I couldnt get to). So then, on my other machine, I had to retype the url in the lynx browser... including some 30 hexidecimal digit number which uniquely identifies the particular patch you wish to download. My hands looked like pretzels...
So, once downloaded to my friends' server, I was able to retrieve them back to my local machine and burn them to cd, allowing me to patch a machine disconnected from the network.
Oh, and I never did tell you the network card drama. One of the most common ethernet cards still around, the 3 c 509 by 3Com is unsupported in Win2k3. Guess what we have laying around, and in almost every box here? Yep.
So, I found a work-around for XP, and used that on Win2K3. It worked. And then 30 seonds later I had that f'king worm.