I have a 4 speed Nec external cd-rom on a 386 with 8 megs of ram and Win 3.1.  It always worked until my zip drive got a problem.  Zip is Drive F, CD-rom is drive E.  The zip was getting assigned to E to conflict with the cd.  When I got the zip back to its F: drive the cd-rom would no longer work. Upon boot up, right after the mscdex.exe line, I get the message" No valid cd-rom device driver selected.  Device driver Aspicdo not found.  Its address is actually BOB8:0000. I am using Adaptec EZ-Scsi for Dos/Windows.
In my autoexec.bat it says  C:\scsi\mscdex.exe /D:As[icido /M:12 /L:E
Config.sys says Device=C:\qemm\loadhi.sys R:2 Size=24032 C:\scsi \aspi2dos.sys /d /z  and Device=C:qemm\loadhi.sys /r:1 Size=28976 C=scsi\aspicd.sys D:aspicdo  How can I get my computer to realize that Aspicdo is located at BOB8:0000?
Are those zeroes the letter o or number zero?  If the answer is going to do me any good, the directions will have to be very EXACT and simple or I won't understand.  (The cd-rom worked before with these lines in the autoexec.bat and config.sys at boot up.  Please help since my cd-rom won't work at all now.
###### Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Commented:
I am hoping that you have made a type-o above with the line
device=c:\qemm\loadhi.sys R:2 Size=24032 c:\scs\aspicd.sys D:aspicdo.  If so, edit the config.sys and place a '/' infront of the D:.  It sould be

As for your other question about the '0's.  It is hexidecimal - ie, 0-F (0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E ,F).  Therefore, they are Zeros.  So, it would be B<zero>B8:<zero><zero><zero><zero>.

What is the model of the SCSI card you are using (eg, AHA-1520, 1510, 2940).  Most of the Adaptec cards will display what drives are connected to what ID (0-7).  If your card shows attached devices, and you dont see any, then there is a hardware problem which needs to be looked at by a technician.

Hope this helps,

Stuart

PS.  You could run Optimize from the DOS prompt again (from the QEMM directory).  You may have memory being used for EMS which are conflicting with the SCSI adaptors memory regions.  Try running optimize with a stealth checking.
0
Commented:
You have to edit the config.sys and the autoexec.bat

the lines with 'aspicd.sys' in the config.sys has to look like:

Then the autoexec.bat has to contain the following:
C:\scsi\mscdex.exe /D:aspicdo /M:12 /L:E

The two names after /D: (mscdex and aspicd) must! be the same. The driver (aspicd.sys) is setting this name. MSCDEX is accessing ASPICD.SYS via this name.

After correcting these lines your CD-Rom should be again accessable.

Best regards
0

Experts Exchange Solution brought to you by

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Author Commented:
The config.sys and autoexec.bat files are correct, but I still get the same message.  I THINK I have scsi card aha-1510/1520/1522.  I got this because one of my manuals said that was the only card one of the periferals worked with.  I don't know how to tell if it is supposed to have attached devices.  After I updated my Iomega guest.exe file, this problem developed.  I think it is in some way related to the "break-down"
in the zip drive, and the subsequent steps toward repair.
0
Commented:
Have you tried out, if this still comes up with the same error, when you're using 'loadhigh' or 'devicehigh' in addition to use emm386.exe and highmem.sys. It could probably be affected by this calling.

Exspecialy I'm interested in your whole config.sys and autoexec.bat. And place at the very beginning of the autoexec.bat the line:
pause

Afterwards you should be able to read, what the sys-files tell you about the cd-rom. Exspecialy measage of the adaptec-drivers are interesting for me.

Best regards

0
Author Commented:
I am going to make a hand typed copy for you of my files.  Because they are so extensive Iwill carelessly omit some of the punctuation.  I think you can assume it is correct since the cd-rom used to  work with these configurations.
Config Sys
device-C:\qemm\dosdata.sys
Devicehigh=D:\sb16\drv\csp.sys /unit=0 /blaster=a:220
devicehigh=d:\sb16\drv\ctsb16.sys /unit=0 /blaster=a:220 I:5 D:1 H:5
devicehigh=d:sb16\drv\ctmmsys.sys
device=C:qemm\qemm386.sys ram r:1 fr=none
device-c:qemm\dos-up.sys @c:\qemm\dos-up.dat
device=c:qemm\qdpmi.sys swapfile=dpmi.swap swapsize=1024
buffers=40
files=50
dos=umb
lastdrive=k
fcbs=16,0
/z
laster=a:220
dos=high
shell=c:\dos\command.com c:\dos\ /p /e:512
stacks=9256
country=001,437 c:\dos\country.sys
shell=C:\ndos.com@g:\nu\ndos.ini /p
autoexec.bat

g:\iomega\guest.exe letter=f
set mouse=g:\glide
c:\scsi\mscdex.exe /d:aspicdo /m:12 /l:e
set blaster=a220 i5 d1 h5 p330 t6
set sound=d:\sb16
set midi=synth:1 map:e
set midi=synth:1 map:e
d:\sb16\diagnose /s
d;\sb16\sb16set /p /q
@echo off
set path=C:\qtw;c:\windows;c:\qemm;c:dos;g:\nu;f:\wpc60dos;f:wp60;C:wp60
set symantec=g:\symantec
set nu=g:\nu
set temp=c:\temp
date
time
c:\windows\mouse.com /y
g:\nu\image c: d: g: H: F:
prompt $d$t$h$h$h$h: $p$g
set appt=f:\comm\dates
f:\comm\dates\appt.com /l
G:\nu\initrakd /b
c:\qemm\loadhi /r:2 /lo g:\nu\ncache2 /install /ini=g:\nu\ncache.ini
In neither win.ini nor sys.ini do I find anything called cd-rom in bracket like [fonts] if that's what you are looking for.  I do have a category called [mci] if that's what you want.
I hope this will be helpful to you.  I appreciate all the effort
you are making in my behalf.  Thank you. Kathy
0
Author Commented:
I don't seem to have emm386.exe and highmem.sys in either autoexec.bat orconfig.sys.  No, I haven't used loadhigh or device high in addition because I don't know what you mean, where you want it, and exactly what I am to write.
Also, I am satisfied with my "expert".  I just want to increase the points to this question another 100. That choice doesn't seem to be there.  Mr. Z.
please stick with me, and continue to help me.  I am trying, but as you can see, I am no expert.  I am having trouble even trying to maneuver through your site.
0
Commented:
No hurry or panik - I'm still working on qour problem. I was locking for the software of qemm, to build the whole system qou have on my computer to see how it works. Now I think I have found the problem. Exange the lines with:

g:\iomega\quest.exe letter=f

with the line

c:\scsi\mscdex.exe /d:aspicd0 /m:12 /l:e

After changing these two lines the cd-rom was accessable on my system again. Try it and tell me how it works.

In addition I have found in your config.sys and autoexec.bat some double definitions and useless items. If you want a full corrected autoexec.bat and config.sys send them either here to this board or send them as an attachment via mail to expert@zenker.m.eunet.de. I will make some corretions and will afterwards send them back to you.

Best regards
0
###### It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Hardware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.