After my Canon i320 printer died earlier this week, I purchased a new HP D2460 this afternoon.
One of the computers which has to use this printer is a Windows machine, which is mostly used by the people who stubbornly refuse to stop using Microsoft Office at home. Unfortunately, the onus of “supporting” the idiotic joke from Redmond which pretends to be an operating system, falls on me.
This means I have to deal with the crap that comes out of Windows developers, like the error message of the HP D2460 installation CD-ROM shown below:
As you can see the installer bombs out because it can’t access a file in the G: drive. The main problem is that the particular system has no G: drive AT ALL.
This is the installer which launches from the officially packaged driver CD-ROM, and is bundled as the “driver software” with the printer itself. I’m filing a complaint with HP early tomorrow morning, but I consider this sort of bug something that should NOT have been there in the first place.
It looks like someone forgot a hardcoded path somewhere in the program’s source, but can you configure where this path points? No, because “printer drivers” for Windows are monstrously large sets of obscurely packaged binaries. Forget about “apt-get” like your Debian can do, or the simple extractable tarball of your BSD’s “pkg_add” utility. These are “teh” drivers baby… the official, the one, the only, and unfortunately — at least in my cases — the ones with the insanely idiotic installer.
(Footnote: Downloading the latest version of the 78 MB self-extracting Windows executable “printer software” from http://www.hp.com is not going to help, thank you. The same bug is present in that version too).
Off to see if the “basic driver” executable from the same manufacturer’s web site has a better chance of working in the aforementioned joke of an “OS”.
.. and yes, I know this post may be unfair to HP, but I didn’t buy a printer to have to deal with crappy installers like this. I also don’t care if “Windows is crappy and we have to go through shit like this” is even viable as an excuse.
This sucks HP!
UPDATE (after about an hour or so): After fidding a bit with the options of the installer, and trying both the installer of the bundled CD-ROM and the installers I downloaded from http://www.hp.com, several times in a row, it occured to me that it may be possible to “trick” the installer into believing that there *is* a G: drive, by:
- Sharing any random local directory through the network
- Mapping the shared directory at G: through Explorer
- Creating (through the mapped drive, to check that writing new stuff is possible) a new G:\TEMP directory
This seems to have worked around the installer stupidity, but now the installer is stuck for the last 15 minutes in “A device has been found. Waiting to complete device installation.”
Oh well, let’s wait a bit more and see what other surprises this crapware will come up with for tonight :-)