home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.msdos.apps:4514 comp.os.msdos.misc:4895
- Newsgroups: comp.os.msdos.apps,comp.os.msdos.misc
- Path: sparky!uunet!dcatlas!joet
- From: joet@dcatlas.dot.gov (Joe Trott)
- Subject: Re: CONFIG.SYS tactics
- Message-ID: <1992Aug26.165009.20536@dcatlas.dot.gov>
- Organization: U.S Dept. of Transportation
- References: <w64mapc@lynx.unm.edu> <4LDiPB1w165w@ersys.edmonton.ab.ca>
- Date: Wed, 26 Aug 1992 16:50:09 GMT
- Lines: 26
-
- chrisr@ersys.edmonton.ab.ca (Chris Ringe) writes:
-
- >rdhunt@triton.unm.edu () writes:
-
- ...
- >- (i.e. Can I redirect CONFIG.SYS output to a file?)
- >-
- ...
-
- >Could one not do something like...
-
- >DEVICEHIGH=xxxxxxx.sys > C:\CAPTURE
- >DEVICEHIGH=yyyyyyy.sys > C:\CAPTURE
-
- >?? One would assume that this type of re-direction would still work. I
- >haven't tried this, but logically, it should.
-
-
- Subsequent redirects MUST use >> instead of >, or the file will get
- overwritten (instead of appended) each time.
-
- This will work with some commands but not others; I'm not sure which, so
- try it. If the driver writes to standard output (many don't) then it
- will work.
-
- -JTT
-