...missing files for a complete installation.
I feel a rant coming on ---
I miss the 'good old days' when software applications would install all the files they needed in one directory. Today, it seem that software installations involve creating a huge pile of directories and sub-directories, many empty, and then filling your disk full of files, many of which are read only once, or not ever. Even more annoying is the habit of also stuffing files in every nook and cranny of your system -- all with names so obscure one can never determine what they do, where they came from, or more importantly, can the be erased.
In an ideal world, a software package would create one directory tree, install everything it needs into this tree, and after initializing itself, DELETE WHAT IS NO LONGER NEEDED. Perhaps this is just too much to wish for? How about supplying Un-Install routines that do a COMPLETE job: Remove files, folders, sub-folders, support files such as .DLLs, AND REGISTRY KEYS!!!
I feel better now, PW.
P.S. Who thinks we need 10,000 fonts to write a letter?
P.P.S. I had a package load over 40 different icons for a DOS session. It seems they have a number of choices for each version from 2.2 to Win2000. One would suffice! |
