Hi,
I think there is a special place in hell for people that write not
only dysfunctional windows software, but even worse, dysfunctional
windows software *installers*.
My latest favourite: vmware "infrastructure client", which is what you
need to remotely manage ESX[0] stuff (no unix client, no macos client).
Ships as a 280 Mb sized .exe, claims to need some 500 Mb disk space.
Click on .exe - starts extracting stuff. Lots of stuff.
Then takes that stuff and builds a .msi installer file from it(!) (it's
not like "the .msi is inside the .exe").
*Then* runs the .msi, which dutifully checks available disk space, and
notices that "oh, this nice piece of installer has now used up over
700 Mb for temporary files, and *now*, there is no longer enough disk
space available to actually install the piece of sh*t that's inside
the .msi".
Beautiful, no?
What happened to the art of building installers that will just install
the software to the final place (configurable, not insisting that half
of it MUST GO TO C:), without littering the hard disk with temporary
bullshit in the process? Comes in especially handy when the machine
in question is a bit short on disk space[1] and the installer is started
from a network drive...
*grumble*
gert
[1] the target machine for this beautiful product is actually a very
much stripped down Windows XP virtual machine, running on a Linux nettop
for the very purpose of running software that is needed but not available
for operating systems that people might want to use. Not that Win7 is
particularily bad, but it's just not My OS Of Choice.
[0] I've now decided to use KVM
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
