#Windows and CD-ROM
6 messages in this thread
Has anyone experienced problems with running a CD-ROM drive and Windows
versions 3.1 or 3.0 with Microsoft Extensions version 2.21?
If so, what was the problem, and how did you fix it.
So far we have two CD-ROM workstations that have problems running Windows
under enhanced mode. About the only thing common between them is the
software: Windows 3.0 or 3.1, MS-DOS 5.0 or 4.0, and Microsoft CD-ROM
Extensions 2.21.
Microsoft has been NO help at all. I'm made 8 calls to the tech help
numbers (multimedia and Windows).
I would GREATLY appreciate some suggestions.
Bill Hayes
Bill,
I've *never* been able to run my CD-ROM drive from Windows 3.0, 3.1 or
MS-DOS 5.0 using the MCSDEX.EXE v2.21 currently available for downloading
from MSL-1 (as CDEXT.EXE) here on CompuServe. It will invariably cause a
system lockup or crash. I get flawless operation in both Windows and DOS
with the v2.20 of MSCDEX.EXE that came with my drive. V2.20 requires the
SETVER.EXE in my CONFIG.SYS for MS-DOS 5.0 but that's always been there
anyway. Since I have no problems with v2.20, this hasn't been an important
issue with me, but it certainly *IS* strange and I'd like to know why.
Tom
So far, I've seen the problem on a Gateway 486 clone, and two IBM PS/2s, a
Model 55 and a Model 57. In all three cases it appears to be some kind of
device timeout error. We think the microchannel problem could be a badly
engineered card, and I'm working with the manufacturer on that problem.
You should check your System.ini file and rid it of the line
"device=lanman01.386." For what it's worth, it doesn't matter in our case
if it's there or not, the systems lock up! But it MAY matter with your
hardware/software combination.
Calls to MS have not been very helpful. Thanks for the suggestion, I'll
fall back to MSCDEXE.EXE version 2.20.
Bill…
Thanks for the response, Bill, and I had already removed the lanman01.386
line from SYSTEM.INI. At present I'm loading MSCDEX 2.20 high with QEMM
6.01 and also am using the /E switch with it. It may be that I can't get
away with that combination with v2.21. As soon as I get some time, I'll
play around with different ways to load it and see if it makes a
difference.
regards,
Tom
I've heard that if you're using MS-DOS 5.0, you may want to change the
SETVER.EXE table for MSCDEX 2.20 from DOS 4.0 to DOS 4.1. That comes from
On-Line Computer Systems support folks. They're the people who make
Opti-Net and other CD-ROM products.
Best wishes,
Bill…
Bill,
Thanks for the info, although I'm having NO problems with 2.20 with
SETVER.EXE set up as it is; it's v2.21 that won't work on this machine for
some reason. Maybe I can't use the same parameters and switches with 2.21
that I use with 2.20, something I intend to investigate when I have some
free time. For now, I don't intend to fiddle with a successful setup [g].
regards,
Tom