Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!seismo!esosun!forseti.css.gov
From: tanida@forseti.css.gov (Tom Tanida)
Newsgroups: comp.windows.ms
Subject: Re: How to clean WIN.INI and WINDOWS directory?
Message-ID: <695@esosun.UUCP>
Date: 30 Apr 91 21:07:31 GMT
References: <67620009@hpcupt1.cup.hp.com> <2815B8B4.4000@maccs.dcss.mcmaster.ca> <1991Apr29.191020.5406@SanDiego.NCR.COM>
Sender: news@esosun.UUCP
Reply-To: tanida@esosun.css.gov (Tom Tanida)
Organization: Science Aplications Int'l Corp.
Lines: 24
In-reply-to: jim@tortuga.SanDiego.NCR.COM (Jim (James) Ruehlin)

In article <1991Apr29.191020.5406@SanDiego.NCR.COM>, jim@tortuga (Jim (James) Ruehlin) writes:
>>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...)

How about making DOS a Windows application, rather than making
Windows a DOS application?  :-)

Anyhoo, I'll second what this poster has to say.  An alternative might
be to break up the win.ini file- I'd prefer to see the win.ini file
contain only parameters for applications (kind of like an .xresourcerc
or .Xdefaults file under X-windows), and have driver/basic Windows
stuff in another file (not to be confused with system.ini :-) ).

-Tom