You Can't Get There From Here
(Even though I've said "no more Windows rants, after the huge waste of my time this weekend due to "Driver Hell", I felt the need to vent. That and the cats are tired of hearing "#*&$(# Microsoft *($#*($# Drivers #*$#)($*#)( ". So if you've read my anti-Windows rants before then please feel free to move right along.)
It has been, shall I be polite? Oh I don't know -- the hardware weekend from hell. Close to nothing in the Wintel world worked. This particular set of utterly "joyful" experiences culminated with the discovery this morning that I can have EITHER my USB CD-RW drive working or my Firewire hard drive -- but not both. Oh and my Firewire drive doesn't work at all (I mean doesn't even display in Explorer) unless the machine is shut down between restarts. Joy oh freaking joy. Clearly this makes it hard to burn the Redhat 9 cd images to migrate my new desktop to Linux.
So I figure that I'll be smart and use another computer -- I just installed Windows XP Pro onto my Thinkpad to use for testing some stuff (this install is literally under 24 hours old -- no winrot at all) so I think to myself "I'll just install the CD-RW on that machine and burn them from the Laptop". Nope! Despite a fresh set of drivers from HP for the CD-RW drive, it won't install. Unrecognized hardware errors. Try again. No dice. I'm now installing SP1 -- just the 1st of 35 critical updates in the admittedly foolish hope that hardware support will be fixed in SP1 and I'll be able to use my CD burner again. If that doesn't work then I guess I'll have to move disc space around until the ISOs and the temp space need fit on my internal hard drives and then dpo the burning from my desktop.
Oh and the crowning humor in this excursion into "Driver DisasterFest 2003" was when Windows told me, on my main desktop, that for both the Firewire drive and the CD-RW drive it couldn't find the drivers. Now both these pieces of hardware worked previously. So I just told it "c:\winnt\system32\drivers\" and it worked perfectly.
I think Windows has Alzheimers.
Note: Microsoft very often blame drivers written by 3rd party companies on Windows problems. Yeah I'll buy that in a lot of cases but not in this last one -- the problem here is clearly a flawed driver model. Two drivers for two different types of devices written by two different companies that fail in the same way. That clearly isn't their fault -- this is a Windows issue.
When:
7:46:33 AM |
Permalink: |
|
IM Me About This
|