does DOS 5.0 support ATAPI CD-ROM's?
Phil Crown
Does DOS 5.0 support IDE ATAPI CD-ROMS?
I have my boot floppy with the Mitsumi driver loaded in config.sys and
MSCDEX.EXE loaded in autoexec.bat, and the drive is detected when
booting up, but when I try to "dir E:\" the system freezes.
I have also downloaded the latest drivers from http://www.mitsumi.com.
The CD-ROM works fine under Linux and OS/2.
--
Phil Crown pcr...@ispnews.com http://www.ispnews.com
Osmo Vuorio
In article <afk65e...@pcrown.net>, Phil Crown <pcr...@airmail.net> says:
>
>Does DOS 5.0 support IDE ATAPI CD-ROMS?
>
ftp://ftp.microsoft.com/Softlib/MSLFILES/Mscdx223.exe
Osmo
Charles Mosher
Phil Crown (pcr...@airmail.net) wrote:
: Does DOS 5.0 support IDE ATAPI CD-ROMS?
: I have my boot floppy with the Mitsumi driver loaded in config.sys and
Yes.
Your question sounded interesting, so I dropped offline to check
this on my machine.
Remember, CD-Rom drives are not like floppy drives, where you get the
ARF message immediately when you log to an empty drive, or like hard
disks, where you immediately get a message
Invalid drive specification
when you change to a non-existant drive, but "network" drives,
whatever that means. In any case, in all five versions of MS-DOS
that I tested (4.01, 5.00, 6.00, 6.20, 6.22), I could change to an
empty (or drawer open, or closed with an audio CD in place) drive,
with no error message, and only got the ARF message when I attempted
any DIR command on the CD-Rom drive. That is, if your drive did not
have valid digital media in it, what you observe appears to be
normal.
Have you tried several different CD-Roms in the drive?
If the above does not sufficiently clarify the issue, I suggest that
you contact the vendor for your CD-Rom drive and see what suggestions
they have. It is possible that a newer driver might help, or that
you have some sort of hardward problem, such as a worn out (dead
laser) drive. My understanding is that a dead laser is the "normal"
end of life for CD players.
Good luck.
--
Charles Mosher
ratr...@svpal.org
Phil Crown
Charles Mosher wrote:
> Remember, CD-Rom drives are not like floppy drives, where you get the
> ARF message immediately when you log to an empty drive, or like hard
> disks, where you immediately get a message
>
> Invalid drive specification
>
> when you change to a non-existant drive, but "network" drives,
> whatever that means. In any case, in all five versions of MS-DOS
> that I tested (4.01, 5.00, 6.00, 6.20, 6.22), I could change to an
> empty (or drawer open, or closed with an audio CD in place) drive,
> with no error message, and only got the ARF message when I attempted
> any DIR command on the CD-Rom drive. That is, if your drive did not
> have valid digital media in it, what you observe appears to be
> normal.
>
> Have you tried several different CD-Roms in the drive?
Yes.
> If the above does not sufficiently clarify the issue, I suggest that
> you contact the vendor for your CD-Rom drive and see what suggestions
> they have. It is possible that a newer driver might help, or that
> you have some sort of hardward problem, such as a worn out (dead
> laser) drive. My understanding is that a dead laser is the "normal"
> end of life for CD players.
I will try to contact the CD-rom manufacturer. I already downloaded the
latest drivers from their site.
The driver's come with a benchmark program which has no problem
accessing the drive to perform its tests.
I'm also running a DTC 2278 (E)IDE controller card (which requires its
own driver) and the CD-rom is on the master drive on the second port.
I think I have a driver problem, but I hope I can get this worked out.
:-) All I want to do is install Windows95 (I bought the upgrade), but I
need to be able to boot dos and acces my cd-rom first...<argh>
Here's my config.sys and autoexec.bat, if it helps. I've tried numerous
variations of the below, perhaps I am missing something?
Thanks for your help!
#config.sys
SHELL=C:\DOS\COMMAND.COM C:\DOS /P
DOS=HIGH,umb
FILES=40
BUFFERS=30
DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE ram 12000
STACKS=9,256
LASTDRIVE=Z
DEVICEHIGH=C:\DTC\DOSEIDE.SYS /v /2 /16
DEVICEHIGH=C:\MTM\MTMCDAI.SYS /D:MTMIDE01
# autoexec.bat
@ECHO OFF
SET COMSPEC=C:\DOS\COMMAND.COM
PATH C:\;C:\BAT;C:\DOS;C:\UT\
PROMPT $P$G
SET DIRCMD=/o:gn
MODE CON: RATE=32 DELAY=1
rem LOADHIGH C:\DOS\MSCDEX.EXE /D:MTMIDE01 /L:D /M:10 /V /E /K /S
LOADHIGH C:\DOS\MSCDEX.EXE /D:MTMIDE01 /M:10
LOADHIGH C:\DOS\DOSKEY >NUL
Phil Crown
for anyone interested, MSCDEX 2.23 (for DOS 6.2x) fixed my problem. :-)
For some reason I had it stuck in my head that MSCDEX 2.21 would be good
enough for DOS 5.0.
--
Phil Crown pcr...@airmail.net http://web2.airmail.net/pcrown