Date: Sat, 29 Mar 1997 00:28:54 -0500 (EST)
From: Jude DaShiell <jdashiel AT eagle1 DOT eaglenet DOT com>
Sender: jdashiel AT eagle1 DOT eaglenet DOT com
To: Kent Byerley <kentb AT vnd DOT tek DOT com>
Cc: opendos AT delorie DOT com, opendos-developer AT delorie DOT com
Subject: Re: wish list 2.0
In-Reply-To: <333BE9A7.41C67EA6@vnd.tek.com>
Message-Id: <Pine.NXT.3.95.970329002717.16235X-100000@eagle1>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Only if a clear demarcation of config.sys section and autoexec.bat section labels
were placed in boot.log.  Wouldn't want users new to opendos getting confused.
On Fri, 28 Mar 1997, Kent Byerley wrote:

> Jude DaShiell wrote:
> > 
> > I just thought of something, the config.log and autoexec.log files should
> > always generate on a boot.  If there were no errors in config.sys when
> > the machine booted then config.log could be erased.
> > If there were no errors in autoexec.bat then autoexec.log could
> > be erased.  Boots should do destructive writing of these log files.
> > If an error does happen or perhaps more than one error, perhaps the offending
> > parameter on the command line could be tagged with a caret
> > in front of it.
> > I know systems especially the faster ones boot up too fast
> > even for people with 20:20 vission to read the screen much of the time and this
> > feature were it implemented would remove
> > that requirement.
> > 
> > On Thu, 27 Mar 1997, Mike A. Harris wrote:
> > 
> > > On Sat, 22 Mar 1997 jdashiel AT eagle1 DOT eaglenet DOT com wrote:
> > >
> > > > If possible, opendos shouldn't be permitted to boot
> > > > up on anyone's machine without writing a config.log and autoexec.log
> > > > file if any errors are encountered in either config.sys or autoexec.bat
> > > > files.  If those files generate under error conditions
> > > > fixing problems and documenting problems will be much easier.
> > > > Probably the line number where the error happened should be
> > > > put into the log files along with the error message.
> > > > jude <jdashiel AT eagle1 DOT eaglenet DOT com>
> > >
> > > YES!  Much like the system logs in Linux (ala syslogd and klogd).
> > > Those logs come in VERY HANDY when trying to pinpoint trouble.
> > >
> > > Mike A. Harris        |             http://blackwidow.saultc.on.ca/~mharris
> > > Computer Consultant   |                  Coming soon: dynamic-IP-freedom...
> > > My dynamic address: http://blackwidow.saultc.on.ca/~mharris/ip-address.html
> > > mailto:mharris AT blackwidow DOT saultc DOT on DOT ca
> > >
> > > EMACS: Escape Meta Alt Control Shift  :o)
> > >
> > >
> > 
> > jude <jdashiel AT eagle1 DOT eaglenet DOT com>
> 
> Couldn't we get by with just one file "boot.log".  I would hate the
> growing list of possible
> log file to track through to find a bootup problem.
> 
> 
> --
> Kent Byerley               |  We are born naked,
> kentb AT vnd DOT tek DOT com          |  wet and hungry.
> Tektronix, Beaverton, Or   |  Then things get worse.
> 


jude <jdashiel AT eagle1 DOT eaglenet DOT com>