Hi, Dieter.

DM>  On the 03/8/96  11:26, Bob waffled to Dieter..

DM>  BL> MSCDEX.EXE. For some reason, DOS didn't instal it, but there it
DM>  BL> was... lurking on the original discs unused and alone. Gee!

DM>  DM> I think DOS may detect if there is a CD-Rom installed, and load
DM>  DM> the MSCDEX automatically, either that, or the CD-ROM install
DM>  DM> disks configure all that anyway.

DM>  BL> It's a bit hard to load it when the discs are up on the shelf.

DM>  When you install DOS, dicko.

DM>  DM> Try a de-installer - they have some success at removing
DM>  DM> unwanted DLL's.

DM>  BL> I've got an de-installer... me. I am a pre-emptive de-installer;
DM>  BL> I get the bastards going in. It's the thing I hate most about Windows;
DM>  BL> the way dickhead programmers load their shit and rewite win.ini at
DM>  BL> every opportunity. I've got a thing called WordScan that rewrites its
DM>  BL> ini file every time I boot! What the hell for? These blokes are
DM>  BL> fuckwits, and there's no way I let them loose in my windows/system
DM>  BL> directory.

DM>  What about DLL's though ? How do you detect which arcanely-named
DM>  DLL's are relevant to what program ?

It's a good point. I've been thinking of writing a PissOff.Useless
program, something like...

List all DLLs, anywhere.
Scan all executables (noting that these days this isn't just *.EXE but
for example *.SCR, *.CPL and of course other DLLs too) noting which DLLs
they use and deleting those from the list.
Delete everything left in the list.

Whadya reckon?

Regards, fIM.

 * * If wishes were horses, beggars would ride.
@EOT:

---