#NECCDR.SYS PROBLEM
11 messages in this thread
HELP! I've got a problem with a NEC CDR-80 I just picked up from DAK. When
I got it home, I found that the MSCDEX.EXE wouldn't work with dos 5.0
(Incorrect DOS version message). But that's not the problem. I talked
with NEC, who gave me a BBS number. I called and downloaded a file named
CD_T128.EXE. This gave me a new MSCDEX, NECCDR.SYS file, and MUSICBOX
software. When I installed this, my computer will not load the NECCDR.SYS
file, saying that C:\SCSI\NECCDR.SYS is bad or does not exist. But I KNOW
it is in that directory by that name, and I wouldn't think NEC would have a
bad version on their BBS, would they?
I don't know if this has anything to do with it, but I am running STACKER
on my hard drive, and I have a D: Ramdrive and an E: Stacker drive, so I am
installing the CDROM as G:
PLEASE HELP! I am salivating to check this thing out, but I can't get it
to work. Oh, 1 more thing. I ran SCSITEST, and everything checks out ok.
My id is 72677,44, just leave E-Mail or a message here or on the IBMNEW
forum. Thanks in advance!
Steve Soller
I'm about to follow in your footsteps. Bought the NEC CD80 some time ago
from DAK and will be installing it in a week or so. Have been having an
awful time installing a Sony CDrom at work, but finally successfully (odd
thing: two variants of the sony_cdu.sys file and, of course, only one
worked). Point of this message is to ask you if you'd be kind enough to
send along any tips, NEC helpline numbers, DAK staff names, or … that you
think would be useful. Reward in heaven, and many thanks.
I did call NEC, and got a BBS number. It also contains another BBS number
for NEC. The number I got was 708-860-2602, at 8N1. It has current
graphic Drivers, and current CDROM drivers. I bought the NEC CDR-80 at a
DAK close out sale when the Torrance CA. Store closed on 30 Apr. Got a
great deal, since it was the last in stock and didn't even have a box, but
I guess it will only be worth it if this thing works. It you happen to
come up with any information on my problem, or if you experience a similar
problem, PLEASE let me know. I am going nuts trying to figure this one
out.
Steve
In response to your original question….
You said that MSCDEX reported "incorrect dos version" with DOS 5.0. The
simple solution for THAT problem is to add MSCDEX to the SETVER command of
dos 5.0, which then TELLS MSCDEX you are running dos 3.3. This program was
included just for this version compatibility issue.
I hope these problems are not an omen, I just got a DAK "special customer"
mailing for the NEC CDR-80, with SCSI card and Bookshelf/etc package, and I
can't pass up this price.
I'm not into multimedia or anything (…yet), can someone evaluate what the
500ms vs 380ms(cdr-83) access rate has? Am I gonna feel frustrated just
accessing reference materials, waiting for the drive?
Thanks for any info TSK
Thanks! I got the drive running, first by using the OLD Device driver and
the new MSCDEX.EXE file, and then using the old MSCDEX.EXE file using
SETVER. The drive is accessible as drive F. Unfortunately, I cannot get
CHKCD to work (it just sits there for hours showing a busy light), and when
I tried to access the disk that DAK gave me (MICROSOFT BOOKSHELF 1991) I
get a "CDR103: CDROM not High Sierra or ISO-9660 format reading drive F"
message. What is going on? GuessI'll work this out yet.
Steve
I haven't received my player yet, so these joys are still ahead…..can't
help ya!
Keep in touch, Tom. Maybe we can share info.
Steve
Will definitely keep in contract. I got mine at DAK, too. From a short
article that ran in PC-Week. Also a deal, but, as you say, only if they
work… Have you tried DAK technical support? They never carried this
item in the catalog, but they did mail order it if you knew to ask.
Meanwhile, I've got house guests from California this week. Maybe they'd
like to help install a CD-rom, but maybe they've got other plans for their
jaunt clear across the country <g>. So, a bit of silence on this end just
means a short break from the problem, not defeat.
Keep in touch, Caarlyle! Maybe we can share what we learn about these b
beasts.
Steve
Carlyle, if you have a moment at some point, I'd very much appreciate some
info on the two sony_cdu files you had, e.g. file sizes and dates, along
with which version worked and the sony drive #. I'd like to have the info
for a help file, laser3.txt, on the Sony LL drive that I maintain in the
library here. TIA! Kevin–
Glad to help, Kevin. And nice to know about your work. I'd wondered about
the contents of that file, but not downloaded the description. Do you know
if the same sort of collection of drivers exists for NEC hardware? At any
rate, here's the information you wanted: Drive is CDU6250 with driver card
CDB-231. On a Zenith 386-25, it installed at port address 300h. The two
files that came in the \bin subdirectories on the 3.5 and 5.25 disks were,
respectively: Sony_cdu.sys 6/11/91 @ 8:40a (9216 bytes) and sony_cdu.sys
1/10/91 @ 2:11a (8993 bytes). The second file, the older one, was the only
one that worked. The other would lock up the Zenith while booting. Now,
this machine had been used (Gov't buys things on the cheap), and I wonder
if the .sys file could have been modified on the master disk. Can you
imagine anyone using a master disk except to make a backup! So, seems kinda
like that may be the explanation <g>. Hope this information is useful.