Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!ncar!gatech!hubcap!ncrcae!ncr-sd!iss-rb!tortuga!jim
From: jim@tortuga.SanDiego.NCR.COM (Jim (James) Ruehlin)
Newsgroups: comp.windows.ms
Subject: Re: How to clean WIN.INI and WINDOWS directory?
Message-ID: <1991Apr29.191020.5406@SanDiego.NCR.COM>
Date: 29 Apr 91 19:10:20 GMT
References: <67620009@hpcupt1.cup.hp.com> <2815B8B4.4000@maccs.dcss.mcmaster.ca>
Sender: @SanDiego.NCR.COM
Reply-To: jim@tortuga.SanDiego.NCR.COM (Jim (James) Ruehlin)
Organization: NCR Corporation, Rancho Bernardo
Lines: 24

In article <2815B8B4.4000@maccs.dcss.mcmaster.ca> ns@maccs.dcss.mcmaster.ca (Nick Solntseff) writes:
>>Is there a procedure or tool documented/offered somewhere that will cleanup
>>my WIN.INI file and WINDOWS directory?

>I will second that!  To make things worse old drivers left around can
>produce untoward effects!  I have had to re-install Win 3 a couple of
>times and then there is no way of knowing what stuff to leave and what
>stuff to remove from all of the .INI files.
>
>Managing Win 3 systems is a real drag.  It is about time we users rise
>1-416-525-9140 xtn 3443.
I agree completely.  Comparing the Mac to Win 3.0, the Mac requires very
little in the way of system management.  If you don't need a driver anymore,
you can throw it out of the system file - no changes in win.ini or any other
xxx.ini.  Most configuration and initialization information for any
type of application on the Mac is stored entirely within the program
itself.  Since Win 3.0 still uses the old DOS file management scheme it
my be a problem that exists until DOS goes bye-bye (at least as far as
a platform for launching Windows is concerned), so lets have a Windows
file system that can use DOS, instead of vice-versa.

(Hmm... sounds like the beginning to the old "Here comes OS2" stream...)

- Jim Ruehlin