#MSCDEX.EXE v2.21
16 messages in this thread
For those of you who've been trying to locate Version 2.21 of MSCDEX.EXE, I
have good news and [maybe] bad news.
The good news is that v2.21 is available in the Microsoft Software Library
here on CompuServe. Just GO MSL-1 and search on the keyword MSCDEX. This
will pop up MMEXT.EXE which is the self-extracting archive containing
MSCDEX.EXE 2.21.
The possible bad news is that this version may not work on your system.
It sure doesn't work with my MITSUMI internal CD-ROM drive, whereas the
MSCDEX v2.20 that came with the drive works faultlessly, from MS-DOS 5.0
(with SETVER.EXE) and from both Windows 3.0 and 3.1. V2.20 works in
conventional RAM or loaded high with and without the /E switch. V2.21
doesn't work on my system no matter what I do. Any attempt to access the
CD-ROM drive results in an immediate system lock-up requiring a re-boot. It
is quite possible that other CD-ROM drives with different drivers may be
OK. I'd be interested in hearing any success stories.
Tom
Tom,
It doesn't suprise me that you have had problems with 2.21. I downloaded
it from the Microsoft BBS when it was there just to see what it did. It
specifically said that it was a beta version for internal use only. I
prefer to stick with production versions — besides, using setver is not so
bad.
Frank
I'm using the 2.21 in the MS CDROM developer's kit and have not had any
problems whatsoever. I'm not using any MITSUMI drives though.
<<< Peter Schulz >>> 09:45am pst
Thanks, Peter. It could well be that the drivers that came with the Mitsumi
drive just don't like or recognize 2.21, even though everything performs
faultlessly with the supplied 2.20. If it's not broken, I have no interest
in trying to fix it! [g].
Tom
If it works… It is weird thought since there are no "documented"
interface changes between 2.20 and 2.21.
<<< Peter Schulz >>> 08:49am pst
Thanks for the info, Tom. Per a general message I posted a little while
ago, the version of 2.21, let's call it the "new" 2.21, that MS posted is
different from the now-older version of 2.21 that's in fairly widespread
distribution. I hope someone with more technical skill than I can tell us
what makes the newest one different. Between this and incompatibilities
popping up with the basis drivers and W3.1, we may see some messages
flying!
I downloaded the newer one from MSL-1 and quickly reverted to the earlier
2.21. I start MsCdEx and load buffers into expanded memory. Under Win
3.1, the new version instantly gets an EMM386 crash and automatic reboot.
— Ron
Uhggg! Sounds like that turkey ought to fly back to Redmond, WA!
Ron,
Can you be so kind to send me a bynary Email of the **right** version of
mscdex 2.21? Since I'm stuck here in Italy, I have no practical access to any
of the sources documented in laser3.txt…
Thanks and Regards!!
Paolo from Italy
yes, indeed, it is different. The new version won't work with my Sony
7205.
It's interesting to note that the "read.me" file in the 3.1 upgrade kit
specifically mentions 2.21. The version I'm running, from Creative Labs
BBS, is working fine on my config. (Win 3.1, SB PRO, Sony Laser Lib 7205).
I just downloaded the MSCDEX driver and Win 3.1 SBP driver set last week,
so I assumed it was the version mentioned in the readme file.
I too am interested in how this all shakes out. So far, it's the only bad
news about 3.1.
Kevin, I know we have similar CD & Sound hardware. What PC are you running?
The reason I ask is that my system does not appear to be fast enough to run
King's Quest V under windows. The CD sound track is choppy to say the least
and the cartoon at the beginning does not run (the slide show runs
instead). Acording to the doc's, the slide show is substituted for the
cartoon on "slow" systems. Until now, I didn't consider a 20Mhz 386SX a
slow system. The program runs a little better under DOS, the cartoon plays
and the sound, while still a little choppy is much better.
If a larger buffer would solve this problem, I think we've found the first
MM title that won't run on the SBPRO/CDU 7205 platform.
Hasn't anyone noticed that MSCDEX 2.21 SHIPS with Win 3.1? In fact, the
SETUP program will automatically upgrade the driver! Works fine on all of
our machines, loaded high (with QEMM 6.02)
Well, it doesn't show on any of the 6 3.5" diskettes that I got with my
Win 3.1 upgrade. What name was it under and roughly where in the file
sequence on the various disks can I expect to find it? Maybe you could
upload it here if it's not on the normal upgrade version of Win 3.1.
Thanks,
Tom
That IS interesting – both my system at home and at work started having
problems accessing the CD-ROM right after upgrading to Win31!! Previous to
the Win upgrade, I was successfully using MSCDEX v2.21 without a hitch. I
had suspected SmartDrive or the newer HIMEM.SYS, but I now have a new
suspect!
Thanks
Chris
Tom – I'm having similar problems with the 2.21 version downloaded from
MSL… on DOS 4.01, with QEMM 6.02 and a Sound Blaster Pro. Complete
lockup upon any attempt to access the drive.
Duff,
Yes, I'm convinced that the 2.21 in MSL is broken in some way. I've gone
back to good old 2.20 which performs flawlessly and was the one that came
with my Mitsumi CD-ROM drive. "If it ain't broke, don't fix it!"
The other mystery is the statement that 2.21 was shipped with Windows 3.1
It doesn't appear to be the case with my 3.1 package unless it's very well
hidden somehow.
Tom