home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!sun-barr!olivea!veritas!amdcad!angelo!ching
- From: ching@angelo.amd.com (Mike Ching)
- Newsgroups: comp.os.os2.misc
- Subject: Re: What is needed to install CHKDSK on a bootable floppy?
- Message-ID: <1992Jul24.044127.10015@amd.com>
- Date: 24 Jul 92 04:41:27 GMT
- References: <22JUL199216502541@vmsb.is.csupomona.edu> <1992Jul23.125405.15555@scott.skidmore.edu> <Bruvyv.69H@ux1.cso.uiuc.edu>
- Sender: usenet@amd.com (NetNews)
- Organization: Advanced Micro Devices, Santa Clara, CA
- Lines: 20
- Nntp-Posting-Host: angelo
-
- In article <Bruvyv.69H@ux1.cso.uiuc.edu> meyer@ux1.cso.uiuc.edu (Don Meyer) writes:
- >pvonk@scott.skidmore.edu (Pierre VonKaenel) writes:
- >
- >
- >Unfortunately, I really doubt it. I wrote MAKEBOOT.CMD, using the files
- >'blueprint' by someone else. (Can't remember his name now, it's noted in
- >the comments of the .CMD file.) Anyway, I tried 'losing' some of the files,
- >and things started not to work. The only one I can think of offhand is the
- >PRINT0#.SYS, which is not necessary unless you are going to be printing. But
- >this only saves 7994 bytes.
- >
- >If a one-disk solution is that important, maybe you could look into using
- >the FDFORMAT trick on 3.5" disks...
- >
- >Don
-
- Someone previously posted that you could put cmd.exe on drive b:
- and change config.sys to point to it and that works for me.
-
- Mike Ching
-