[SOLVED] CD-ROM don`t work, after EXIT to DOS.

[defuser]

Hello. I've encountered a problem where the CD-ROM works fine in early DOS (before WINDOWS starts), but stops working completely in late DOS (after exiting WINDOWS). Regardless of when MSCDEX is loaded, attempting to access the contents of the CD results in the following error:

"CDR103: CDROM not High Sierra or ISO-9660 format reading drive J
Abort, Retry, Fail?"

I am using the AHCICD 1.1 driver (By Rudolph R. Loew) + MSCDEX 2.95 (By Microsoft Corp). In CONFIG.SYS: "DEVICEHIGH=AHCICD.SYS /D:OEMCD001", and to call MSCDEX the line is used "MSCDEX /D:OEMCD001 /L:J" (AUTOEXEC.BAT or other place). Have you already faced this problem, is it possible to fix it? Thank you.

Edited 7 hours ago by defuser

[awkduck]

You are no novice user, so I assume most common questions aren't needed. For the sake of any novice, reading this thread, if you type C:\EXIT nothing happens?

What happens if you use ahciwrap.sys or GCDROM.SYS? That may help eliminate that the issue is specific to rloew's driver.

I'm not a huge user of cd-roms "in any O.S." with that said, the error exposes that the driver's disc filesystem functionality is blocked/unavailable; or now unable to recognize the data it observes it. Maybe, it could be the use of an updated UDF filesystem or other updates/patches; perhaps to the bit access of the drives and their controllers. A change/patch, when Windows loads, may be keeping something persistent, at the hardware level, in so doing "maybe" preventing the media from being recognized; after returning to DOS.

I do think my reply is a placeholder, until someone else comes along. But you never know, as you are a competent user, maybe something here will help trigger a thought of your own.

Looking forward to seeing this pan out for you.

 

[SweetLow]

Is something else on this AHCI controller? Especially BIOS controlled drives.

[defuser]

12 hours ago, awkduck said:

ahciwrap.sys

Thanks, this is what I need. It works (and it's even EMM386 compatible). Amazing work!

I haven't looked at GCDROM.SYS yet.

[defuser]

6 hours ago, SweetLow said:

Is something else on this AHCI controller? Especially BIOS controlled drives.

Yes, there is always at least 1 disk (the system disk) present in the BIOS (it's bootable). There might be something else besides it. I'll check it out.

update: I checked the BIOS, and there's only the system SSD and this disk drive (NEC). Only 4 devices are physically connected (including the disk drive).

Edited yesterday at 01:49 PM by defuser

[defuser]

I would also like to add that during further research, I discovered that "AHCICD" and "AHCIWRAP" (both  of these drivers individually) support on-the-fly loading through "DEVLOAD.COM" at any convenient time  when needed (they do not need to be loaded through CONFIG.SYS). However, I was unable to do anything  with "GCDROM.SYS" (it seems that it requires a pure SATA connection without AHCI, or my controller is  not yet compatible with it, or there may be something else entirely). But since "AHCIWRAP.SYS" has  already fixed the issue mentioned in the topic title, I have added "[SOLVED]" there. Thank you all.