#CDR101 Error msg
8 messages in this thread
HI! I've just added a NEC CDR35 (the very first NEC protable CD-ROM), with
a NEC SCSI inteface to my 386/25 ISA bus clone. When I try to access DRIVE
E:, for example 'DIR E:', I get the error CDR101:Not Ready Reading Drive E.
Does anyone have any idea what this means? I'm using the latest drivers
from NEC, the driver and MSCDEX both appear to intialize without error.
And yes, I do have a CD-ROM in the drive! Also, if I put in a standard
audio CD, and use the MusicBox program demo that came with the drivers, the
audio CD plays fine, so the drivers must be communcating with the card and
drive.
Any help anyone can give would sure be appreciated. BTW, I've tried 2
CD-ROMs one of which I know to be readable on another machine.
It sounds like your drive is had conflicts at a lower level. Maybe
duplicating irqs or some memory addresses. Do you have Window v3.1
.. there is a nice utility (called MSD) which gives quite a bit of detailed
information on your computer setup.
>NEC SCSI inteface to my 386/25 ISA bus clone. When I try to access DRIVE
E:, >for example 'DIR E:', I get the error CDR101:Not Ready Reading Drive
E. Does >anyone have any idea what this means?
If you are loading EMM386.EXE try:
DEVICE=EMM386.EXE X=CC00-CDFF NOEMS
This excudes the SCSI boards address range assuming the SCSI board is set
to this address, which I think is the default setting.
-Mitch
Thanks for the suggestion, but at the moment I'm not running any memory
manager. What's got me stumped is that the driver and MSCDEX initialize
fine, The cdrom spins, and the PC indicator on the drive lights up. Also,
if I turn thedrive off after loading the driver and MSCDEX, and THEN try a
DIR E:, the drive spins up, the PC access indicator lights up, but I still
get the error message. Also, as I said, the PC software will control an
audio CD in the drive without problem, which seems to indicate (to me at
least), that the card, drivers, and drive are talking to each other. I've
tried all four available addresses for the NEC card, with no success. One
other thing: I've got another SCSI card, an Adaptec 1540, controlling a
SCSI drive, but the two cards are set at differen base addresses. (in fact,
if I set them to the same base address, the hard drive won't load).
If anyone has any other ideas, I'd sure appreciate hearing them. (BTW, I'm
running for the test at least, under plain vanilla DOS 5.0, and I've tried
eliminating ALL TSRs and drivers except those absolutely necessary (like
the CDROM drivers). thanks again.
Bob —
I've been having the exact same problem you're describing with a completely
different setup: a Magnavox CDD 461 on a C&T 286 Motherboard, even with a
"plain vanilla" boot floppy (MS-DOS 3.21; no other device drivers; no
TSR's).
I've tried all eight possible jumper settings on my interface card
(Magnavox proprietary) & just about everything else imaginable, including
pulling cards off my motherboard to try to isolate conflicts. The one thing
I haven't been able to try yet is pulling my video card (how could I see
what happens with no video?), but I plan to borrow a card & monitor this
weekend.
I'll try to let you know what I find out.
Paul -I am having the same trouble with the CDD 461 running on a 386SX/16
from Intelec. The drive initiates correctly, but when I try to access the
disk, I get a message like "unable to access disk directory" and then the
system puts me back to DOS. I too have tried all jumper
settings,"bare-bones" DOS 5.0 Config.sys & Autoexec.bat, to no avail. I
phoned Phillips's Tech support finally and got a new interface card -again
no good. Is there anything else I can do? I would appreciate any help.
David — I gather you saw my earlier msg to Bob Meyer. If so, I'll just
tell you (& him) that I did test my unit on another machine — and it
worked fine!
Next I tried swapping the video setup from the second machine into mine,
and it failed again. So I'm pretty sure now that there's an incompatibilty
problem with my motherboard (the video was the only card I hadn't pulled to
test before).
So *if* you're experiencing the exact same thing as I've been, then
replacing the drive or card won't help.
Other than that, I'm out of ideas, other than replacing my motherboard,
or at least finding someone technically oriented enough to know of some
undocumented jumpers there I could try.