home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dziuxsolim.rutgers.edu!staccato.rutgers.edu!xchen
- From: xchen@staccato.rutgers.edu (Xinghao Chen)
- Newsgroups: comp.sys.intel
- Subject: extra COMMAND copy in memory: HELP WANTED.
- Keywords: unwanted extra command copy in memory
- Message-ID: <Dec.21.11.35.51.1992.21279@staccato.rutgers.edu>
- Date: 21 Dec 92 16:35:52 GMT
- Organization: Rutgers Univ., New Brunswick, N.J.
- Lines: 32
-
-
-
- My wife and I recently have put together a PC-386/33 with SVGA, 8MB
- memory and 162MB (formated) HD disk space. We load the bear system
- with MS-DOS 5.0. The problem is this: once we loaded the DOS
- (and nothing else) and used
- mem /c | more
- to check out the memory status, there would be two COMMAND file copies
- located in the conventional memory. There two copies were of different sizes.
- As we understood, we only need one COMMAND file copy being loaded into
- the memory. We don't know how did the second copy come into the memory.
-
- The second problem is that once we load the DOS, it would fail if we
- try to switch to drive A (or B) in the case that there is no formated
- flopy diskett in the drive.
- In some cases after responde to the
- "Abort, Retry or Fail", we would get the following message (in big font):
-
- NO ROM BASICS
- SYSTEM HALTED
-
- Once this occurs we have to reset the machine.
- As we understood, even if the A drive (or B drive) had no diskett in,
- typping A: followed by RETURN should still bring us to the DOS prompt
- A:\>.
-
- We thank for any advice in regard to correcting these two problems.
- Please forward your advices to xchen@caip.rutgers.edu.
-
- Thanks.
-
- -Chen
-