Installing Win95 off a CD was fine. Initially booting up DOS, then running
setup off the CD worked without a hitch. The problems started when Win95
booted up. Although under DOS, the drive appears to function fine, any
attempt to access it under Win95 causes a system freeze. Total freeze. Dead.
My investigation showed the following: under previous install of DOS, one of
two drivers were being loaded (surprise, surprise, I found the original
installation pamphlet, again, no manufacturer mentioned):
MTMCDD.SYS, 62974 bytes, dated 3/21/91, or MTMCDS.SYS, 64120 bytes, dated
3/21/91. That was followed by good 'ol trusty MSCDEX.EXE.
MTMCDD.SYS appears to be a version of a driver that used DMA. The driver
requires an IO port, an IRQ, and DMA channel to function. MTMCDS.SYS is a
version that does not use DMA, it only needs an IO port address.
When Win95 was installed, it threw away the MTMCD?.SYS driver, and MSCDEX.EXE
(out of config.sys, and autoexec.bat respectively). Control Panel's device
manager told me that I have: CD-ROM controller: 'Mitsumi older single-speed
controller'. CD-ROM drive: 'Mitsumi older single-speed CD ROM drive'. Model
number 'Mitsumi LU002S'. The way that the CD-ROM drive was listed, yielded me
to think it was actually a SCSI drive, with the controller card being a
cheap-o 8-bit single-purpose SCSI adapter (although neither one was really
explicitly identified as SCSI).
Anyway, Win95's mitsumi driver was a farce. The combinations of IO ports,
IRQs, and DMA channels it offered as list of possible choices had absolutely
nothing in common with the corresponding choices I had with the (barely)
working DOS driver. There was an option to use an IO port directly, however,
that didn't work either. Trust me, folks, the Win95 driver does not work,
period.
The only thing that appears to be bone fide is the manufacturer name, since it
somewhat jives with the name of the DOS driver.
Anyway, folks, I can get the CD-ROM drive to work maybe 30% of the time by
throwing out, manually, the abovementioned two entries out of the win95 setup,
then manually loading the DOS driver and DOS MSCDEX.EXE from Win95's autoexec
and config.sys. (Notice, I do lose the autoplay feature this way, but that's
the least of my troubles, read on).
This does avoid the freeze up, but the drive is definitely malfunctioning. A
simple CD-ROM application appears to barely work. However: attempting to
install anything of substance off the CD is a failed effort. MS-Office, for
example, fails to install completely. Even loading the extra set of sound
effects from the Win95 install CD barfs (notice, that installation, under DOS,
off the same CD went off without a hitch).
Every minute or so, install would complain 'Unable to read' such and such
file. Clicking 'Retry' allows things to proceed. Occasionally, 'Unable to
open' such and such file pops up. This one, doesn't go away with a 'retry'
though. Experimentation yielded: after getting one of these errors, if I pop
up a DOS window, then go to the specified directory (on the CD-ROM), DIR would
show an empty directory. CD-ing back to CD-ROM's root directory, DIRing the
root directory, then switching back to the previously empty directly would
miraculously bring back the files contain therein. After which, closing the
DOS window, then clicking on 'Retry' would allow the install to proceed.
It appears that, even with all these tricks handy, there are some undetectable
errors that slip by, which eventually cause the setup to page-fault in
KERNEL32.DLL (or something like that). Shoving the same CD into my own
machine, with my trusty Adaptec 2940 and a Toshiba 4X auto-installed the CD
without a single hiccup.
This, folks, is just my away of convincing you that I really need the right
driver for this beast, period. Any ideas? Kindly respond via E-mail or post,
it's your dime.
Well, I have the same configuration, and it works for me...
One of the things I had to do in order to get it to work was
to delete the DOS drivers in config.sys and autoexec.bat BEFORE
detecting the CDROM with "Add new Hardware" in the control panel.
After that, all worked without a hitch. If after trying this you
are still having problems I would look for hardware conflicts.
Perhaps the IO or IRQ is used twice. Good luck!
Bengt
It sounds like a either hardware problem or you put the real mode drivers in
after Windows set up the drive as a 32 bit device. To make sure, you can
install the drive with the 32 bit drivers by deleting the MTM*.SYS driver from
config.sys and MSCDEX from autoexec.bat if they are there. In device manager,
remove the CD-ROM drive if it is there. Go to add hardware. To save time do
not do autodetect. Select CD-ROM controllers. Choose the Mitsumi. When it
loads the driver it will reboot. After the reboot, go to the device manager
and try to find a combination of resources in the setup that will match the
jumpers on the card. If you can do that and the drive doesn't work you
probably have a faulty drive. If you reinstate the real mode drivers in
CONFIG.SYS and AUTOEXEC.BAT you'll need to make sure that Windows does not
have the drive in the device manager as the 32 bit and real mode drivers will
conflict.
--
Patrick J. Beal
Supervisor/Systems and Support Services
The University of Illinois at Chicago Publications and Mail Services
Voice: 312-996-8571 E-mail: pat...@uic.edu
Thank you in advance.
Give me a mail please.
>I am looking for a Mitsumi double-double-speed CD-ROM driver for Win95.
>In the list of CD-ROM drivers, there is no this driver. Who can help me
>to get it?
I have a mitsumi quad speed (which is what I think you mean by
double/double), and I got it installed the following way:
1) rem out the CD driver lines so no CD drivers load.
2) run install new hardware, and let '95 configure this for you on
its own.
I am a little vague here, but this is something I tried and it worked.
Evidently there is some type of generic quad speed driver that WIN '95
will load. Currently my systems reports back that I do have the
mitsumi, set for quad or better speed, and optimized for best
performance. I can not guarantee that your CD will run in DOS through
this approach (mine won't, but I do not care!) I do not even have an
autoexec.bat or config.sys file on my system.
Hope this helps, let me know if you need more... .
--Jerry
>mo...@htx.chem-eng.kyushu-u.ac.jp (my) wrote:
>--Jerry
I do not have a mitsumi cd-rom, but if your looking for drivers for
it, the best place to look is at http://www.rust.net/~frankc/
You will find a lot of obscure drivers there.
>
Trust me, folks, the Win95 driver does not work,
>period.
>
and it won't either..
>Anyway, folks, I can get the CD-ROM drive to work maybe 30% of the time by
>throwing out, manually, the abovementioned two entries out of the win95
setup,
>then manually loading the DOS driver and DOS MSCDEX.EXE from Win95's
autoexec
>and config.sys. (Notice, I do lose the autoplay feature this way
There are no drivers that will make this drive work..if your friend is going
to keep this drive, the he has to use the real mode driver in the config.sys
file, and you know what that does..
>
>
>
I have a Mitsumi CD-ROM on my system and I use the Mitsumi driver that
comes with Win '95, the setup program recognised it straight away and it
all works fine.
Jon
>Everything deleted-
I have just encountered this same problem. It seems as though when I
was inside the PC the last time and re-ordered my cards, the CD-ROM
controller was not in the slot all the way. As a result the CR-ROM
drive did not operate correctly. I did the Add New Hardware and let it
look for it and it didn't find it. I followed the above procedure and
it works fine.
Thanks Patrick,
Mike Stoops
E-mail:mst...@sun-link.com
***************************
Email: mst...@sun-link.com
***************************