NetNews Usenet Archive 1992 #19/NN_1992_19.iso/spool/comp/os/msdos/misc/4948

Internet Message Format | 1992-08-30 | 1.9 KB

Path: sparky!uunet!ogicse!uwm.edu!caen!news.cs.indiana.edu!news.nd.edu!bach!rwilliam
From: [e-mail] (richard williams)
Newsgroups: comp.os.msdos.misc
Subject: Re: CONFIG.SYS tactics
Message-ID: <[e-mail]>
Date: 29 Aug 92 22:38:03 GMT
Article-I.D.: news.1992Aug29.223803.24744
References: <[e-mail]> <[e-mail]> <[e-mail]>
Sender: [e-mail] (USENET News System)
Organization: University of Notre Dame, Notre Dame
Lines: 31

In article <[e-mail]> [e-mail] (Brian Phillips) writes:
>In <[e-mail]> [e-mail] (Peter L. Hurd) writes:
>
>
>>>> - (i.e. Can I redirect CONFIG.SYS output to a file?)
>
>>As a DOS moron, let me suggest a pause statement very early on in your
>>Autoexec.bat.  Time waster when booting you say, less time wasting that
>>fiddling around with reading a piped output I say.
>
>Of course, the question was how to direct CONFIG.SYS to a file, not pause
>the AUTOEXEC.BAT file.  RTFM, or in this case, RTFQ.
>
>  --Traal the BRAVE
>--
Try the suggestion out before you criticize it.  By putting a pause in
autoexec.bat, you will most likely be able to see whatever it was that was
output by config.sys.  (Unless there was more than one screenful of output).
This same tip appears in PC Mag this month (or maybe PC computing).
Sending it to a file isn't necessary if all you want to do is see what the
messages said, sending it to a file is just another way of meeting the
original poster's goal but the pause tip will probably work as well.




--
---------------------------------------------------------------------------
Richard Williams, N.D. Sociology Department         Office:   [phone]
BITNET:    F67TEL@IRISHMVS                          Messages: [phone]
INTERNET:  [e-mail]                FAX:      [phone]