#MSCDEX
19 messages in this thread
Where can I get updated MSCDEX files? Anyone know? My fingers are tired
ofbrowsing around.
GO MICROSOFT and select the Microsoft Software Library. Search for
keyword=MSCDEX. The latest version is downloadable from there.
Hope this helps!
Rich Bowers OPA
GO MSL-1 (Microsoft Software Library) and download CDEXT.EXE. That's MSCDEX
2.21, the very latest version.
Tom
I've got an interesting problem. I need an OLDER version of MSCDEX! I've
got 2.21 and am having problems under Norton Desktop for Windows. I get
uncerimoniously dumped from windows without even a GPF if I try to access
my CD-ROM after changing discs, without first doing a directory check.
Norton says the problem is because of a bug in the newer versions of MSCDEX
and I need to find an older version. I tried version 2.20 which I had
lying around and it didn't help. Anyone know an easy place to find and
even older version?
Sandy
Sandy,
There are actually TWO 'newer' versions of MSCDEX floating around, both
with the same timestamp and byte count. One is buggy and the other isn't.
You can test the one you have using the following technique:
[1] Using PKZIP 1.10, compress MSCDEX.EXE to MSCDEX.ZIP
[2] Test the result using PKUNZIP MSCDEX -V. You should get the following
CRC32 count: EB7846D3, if it's the good MSCDEX. The bad version has a
CRC32 count of EB5C0EF4.
If you suspect you have the bad version, you can download the right one
from the Microsoft Software Library (GO MSL-1) under the name CDEXT.EXE.
Tom
Tom, I did that with mine (release from the MSL).
I got the 32bit-CRC of 7b1cf0d1, neither of which match yours.
Any ideas?
Clarke,
Interesting. The 'good' value that I gave is from the MSCDEX.EXE that I
downloaded from MSL-1 as CDEXT.EXE a couple of months ago. This also is the
same CRC given in the docs for SpeedCache+ that I use for CD caching. Right
after Windows 3.1 was released, there was an apparently identical
MSCDEX.EXE on MSL-1 with the same byte count and time stamp:
MSCDEX.EXE 25431 2-04-92 2:21am
This earlier version wouldn't work at all on my system, caused all kinds of
problems and lock-ups. The current one with the CRC of EB7846D3 has worked
perfectly in all respects. The SpeedCache+ README file says that there are
other versions floating around as well that give problems with various CD
titles and Norton's NDOS. Unfortunately I no longer have the earlier one
that I got from the MSL, so I can't tell if it's the same one that you
have. When did you get your version from the MSL and was it the MSL here on
CIS?
Tom
Tom, I downloaded it about 2 months ago. I have not had any problems with the
driver as of yet. Strange.
Clarke, well I'm a firm believer that if it isn't broke don't fix it! [g].
If you downloaded CDEXT.EXE from MSL-1 here on CIS only a couple of months
ago, you have the right one despite what the CRC32 apparently is showing. I
suppose there's a possibility of a corrupt byte or two wherever MSCDEX.EXE
is stowed on your HD and it's a byte that doesn't affect performance. As
you say, "strange".
Tom
Do you have the newest version of Norton Desktop for windows? The version
is 2.0 I believe. You might also want to try the Norton forums too and see
if others have had similar problems.
Albert:
I am running NDW 2.0 and it was the SYSOP on the Norton forum that told me
to go to an older version (older than 2.21). I have to go check my CRC's
now
Sandy
When you are accessing the CD-ROM can you disable NDW completely while
using the CD-ROM?
Well, you can load windows without NDW if you change the desktop entry in
System.ini and you can load program manager or file manager while in NDW.
When Norton answered my question about the MSCDEX problem they also refered
to the fact that getting an older version of MSCDEX will solve the problem
of File Manager not being able to access the CD-ROM. Since I don't use
File Manager, I don't know what he was referring to.
BTW, my ZIPping of MSCDEX shows that I have a 'good' version.
Sandy
Have you removed all your TSRs and everything else that isn't necessary
just to get the CD-ROM too boot? Is this just a problem with Norton
Desktop for Windows v2.0?
The problem is only in Norton Desktop. And it's not a terrible problem if
I do things "right". The most reproducable way of getting the problem is
as follows:
I run CorelDRAW! and it accesses the CORELDRW directory of drive M:
(my CD-ROM drive).
I exit CorelDRAW!, place the Word for Windows CD in drive M:
I load Word for Windows.
I get the message TOOLS.DLL not found or something like that.
I exit Word for Windows.
I open the drive window of drive M:
I get a dialog saying that M:\CORELDRW can't be found, do I want to
rescan the drive.
I say yes.
The drive rescans over and over, then suddenly, I'm at the DOS
prompt!
Doing things right is:
I run CorelDRAW! and it accesses the CORELDRW directory of drive M:
(my CD-ROM drive).
I exit CorelDRAW!, place the Word for Windows CD in drive M:
I open the drive window for drive M: and see the directory
structure of the Word for Windows disc.
I run Word for Windows and everything works fine!
Sandy
Have you left a message in the Corel forum about it? What type of CD-ROM
drive are you using? If it is a SCSI drive and you have an adaptec
controller Corelscsi might be able to solve the problem.
I'm using the SONY 7205 with its proprietary SCSI-like interface.
Sandy
Do you have the newest Sony CD-ROM driver? Did the Norton rep state that
it is a problem with all CD-ROM drives with Norton desktop for windows v2.0
or just particular brands? I'm wondering if it is a problem with NON-SCSI
based CD-ROM drives rather than SCSI based.