| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2943.1 | | CPCOD::CODY | | Thu May 29 1997 17:09 | 7 |
| I would assume that if you got a Win95 pc and it came with real mode
drivers then protected mode drivers don't exist. You can check out the
CD vendors support page on their web site to see if there are any newer
drivers available and if not to ask there support group if there is
anything you can do.
PJ
|
| 2943.2 | | UTRTSC::jgoras-197-2-3.jgo.dec.com::JurVanDerBurg | Change mode to Panic! | Fri May 30 1997 05:47 | 11 |
| An ide cdrom (i presume that's the case here) normally does not need a
separate driver to function. Remove the device from config.sys, remove
mscdex from autoexec.bat, reboot and let windows auto-detection do it's job.
Normally it would be no problem then, unless the device has some funnies
in it's ide implementation.
How is this device connected? On the primary controller together with
a hard disk? Or separately on a second ide controller? Of not you may try
the separate controller to avoid a conflict with the hard disk.
Jur.
|
| 2943.3 | | DECXPS::HENDERSON | Give the world a smile each day | Fri May 30 1997 14:53 | 16 |
|
> I would assume that if you got a Win95 pc and it came with real mode
> drivers then protected mode drivers don't exist. You can check out the
> CD vendors support page on their web site to see if there are any newer
> drivers available and if not to ask there support group if there is
> anything you can do.
I'm told (per the Mitsumi [supplier of the controller]) Web page, that
the protected mode drivers are in Win95.
According to Microsoft the problem I have encountered occurs, and their
document on the Knowledge base that deals with protected mode drivers say
that drivers for Mitsumi are in Win95.
Jim
|
| 2943.4 | | DECXPS::HENDERSON | Give the world a smile each day | Fri May 30 1997 14:57 | 19 |
|
>An ide cdrom (i presume that's the case here) normally does not need a
>separate driver to function. Remove the device from config.sys, remove
>mscdex from autoexec.bat, reboot and let windows auto-detection do it's job.
Do I remove the entire line that refers to MSCDEX from autoexec.bat, or
just the MSCDEX.EXE statement?
>How is this device connected? On the primary controller together with
>a hard disk? Or separately on a second ide controller? Of not you may try
>the separate controller to avoid a conflict with the hard disk.
From what I can tell, the CDROM is connected to the controller which is
mounted on the sound card.
|
| 2943.5 | fairly easy to do | SUBSYS::MSOUCY | MentalmETALMike | Fri May 30 1997 15:30 | 12 |
|
Do I remove the entire line that refers to MSCDEX from autoexec.bat,
or just the MSCDEX.EXE statement?
Just rem the line out, ie put rem or REM at the beginning of the line
and put a space after it and it won't load mscdex for you. I also rem
stuff out of config.sys and haven't had any bad side effects other than
to learn what I can leave out for W95. It should detect new hardware
during boot and install the drivers for you (have W95 cdrom handy).
|
| 2943.6 | | DECXPS::HENDERSON | Give the world a smile each day | Sat May 31 1997 13:24 | 13 |
|
I wound up re-installing Win95 and it put all the right drivers in there.
Somehow or other I must have deleted them or something..but I tried
the suggestions posted here first to no avail.
Now it works fine, except I can't hear .wav files in Win95
Jim
|
| 2943.7 | | BBQ::WOODWARDC | ...but words can break my heart | Mon Jun 02 1997 03:46 | 13 |
| Jim-Bro,
> Now it works fine, except I can't hear .wav files in Win95
no great loss ;')
A quick check might be to look at the volume control panel and see if
.wav files are either turned right down, or it may even have the 'mute'
check-box checked ;')
hth,
H
|
| 2943.8 | | DASXPS::HENDERSON | Give the world a smile each day | Mon Jun 02 1997 11:51 | 14 |
|
Thanks, Harry..what I wound up doing is a restore of all factory
installed software. All is well now, thank you.
(I'd checked all those boxes, etc ;-)
Jim
|