delorie.com/archives/browse.cgi   search  
Mail Archives: opendos/1997/12/30/12:27:06

Message-Id: <s4a92d07.061@calderauk.com>
Date: Tue, 30 Dec 1997 17:18:30 +0000
From: Matthias Paul <MPaul AT calderauk DOT com>
To: opendos-support AT delorie DOT com, paul-ma AT reze-1 DOT rz DOT rwth-aachen DOT de
Subject: Re: Help Please !!!
Mime-Version: 1.0

On 97-12-30 Zoltan Nemeth wrote:

>If I boot from C:\ than Opendos don't put on my CD-ROM driver.
>But If I boot from A:\ than everything O.K.
This is strange. Just to be sure, in both cases you are booting OpenDOS 7.02?

If you are not sure, toggle Scrollock on before the "Starting DOS" message will
be displayed. This activates OpenDOS  DIAG mode (since 7.02B2+), and you 
will see additional build info at startup. Since 7.02B2+ you can also just run the
IBMBIO.COM and IBMDOS.COM files from the prompt to display this info (but
beware, older issues will crash instead!)

And you can actually access your CD-ROM drive when the system is booted from A:\?

>When I start my computer the message is that:
>   NO DRIVES ARE ATTACHED, OR DRIVES ARE POWERED DOWN.
>     THE DEVICE DRIVER IS NOT INSTALLED.
>/My CD-ROM is Sony CDU55E, and the driver is atapi_cd.sys./
Though this message sounds a little bit ambigous to me, this is definitely not one of
OpenDOS  own error messages, so it s probably emitted by your CD-ROM hardware
driver.

>config.sys:

>SHELL=C:\COMMAND.COM C:\ /E:1024 /P
Completely of topic, but you should better copy COMMAND.COM into 
the C:\OPENDOS\ directory, and afterwards change this line to:
SHELL=c:\opendos\command.com c:\opendos\ /E:1024 /P

>LASTDRIVE=F
This is OK, if you do not attempt to apply the CD-ROM drive to drives beyond F:,
otherwise try LASTDRIVE=Z

>DEVICE=D:\PUBLIC\CD\SONY\ATAPI_CD.SYS /D:NWCD000
Looks OK. Is the error message displayed when loading this driver, or later,
(e.g. when installing NWCDEX/MSCDEX in AUTOEXEC.BAT)?  If the first case
is true, your AUTOEXEC.BAT contents could be helpful. I guess, drive D:
is just a standard 2nd hard disk partition, so special drive. You are not using
Disk-Compression or the like, which might mix up the drive letters? 

Some more ideas to isolate the problem:

- Single step through CONFIG.SYS (F7/F8) to confirm, that you are actually 
  executing the same file for C: and A: boot. 
- If this problem is caused by some kind of timeout/auto-power-off/spin-up feature
  (PowerSaving enabled in CMOS setup), single stepping through CONFIG.SYS will
   probably also change the timing.
- Actually switch of PowerSaving in CMOS setup. Any special boot orders selected
  in CMOS setup (CD-ROM/ATAPI/SCSI-boot following the El-Torito specification?).
  If so, just try standard A:/C:/none boot order.

If all this does not help, please provide more info concerning your machine, especially
the usage of drive letters as fro A: and C: boot.

Hope this helps,

 Matthias



------------------------------------------------------------
Matthias Paul
eMail: <Matthias DOT Paul AT post DOT rwth-aachen DOT de>
Web: http://www.rhrz.uni-bonn.de/~uzs180/mpdokeng.html


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019