cd rom drive wont work in win 95

i have a p2 400 machine with win95 osr2 on it. I have a mistumi
24 speed cd rom drive that has stopped working. I insatlled a brand new teac 50 speed and that drive too does not work in win95 YET it will work in dos???

I have spoken to teac and they are of no help. I even went so far as to place this cd rom drive in another machine and it works there but not in my machine . I even have formatted the drive and reinstalled win95 ( i had to connect the hard drive to my other machine to do so and installl it then reinatslled the hard drive back inot my other mahcine ( they have the same hardware setup  and motherboards..ausus p2b


can anyone help on this?

oh... the cd rom was working fine and then i got a GPF in windows  while running outlook.  when i rebooted the machine thats when this all started
bztrybxwAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jhanceCommented:
Any indication of problems in the System Control Panel?  It sure sounds like a CDROM or IDE controller driver problem.  Especially since you say the drive is known to be good and it works on the computer in question from DOS.

I'd suggest trying first to go to the System Control Panel and clicking on the Device Manager tab.  Open the CDROM item and them select the CDROM drive.  Click on the remove button.

Then, when you reboot your system, Windows should detect your CDROM drive as a new device and reinstall it's driver.
0
rayt333Commented:
Check this:
1.Select Start > Settings > Control Panel, and double-click System
2.select the Device Manager tab
3.Double-click the Hard Disk Controllers branch to expand it, select your IDE controller, and then select Properties
4.Select the Settings tab
5.In the Dual IDE Channel Settings box, select Both IDE Channels enabled, and then click OK (2 times), and restart your computer
0
rayt333Commented:
This problem can occur with an IDE controller that requires serialization between the primary and secondary IDE channels. The protected-mode drivers for these IDE controllers can fail to be initialized if one of the following situations occurs:
One IDE channel has a supported hard disk, and the second channel has a CD-ROM or other type of drive that requires real-mode drivers to be loaded. Because of the serialization between the two IDE channels, it is impossible to access the hard disk in protected mode and use the other device in real mode. This causes the protected-mode driver to fail initialization, and the NOIDE switch is placed in the registry to prevent future errors. Both disk devices then operate in real mode.
The driver for the IDE controller is manually removed from Device Manager and then reinstalled, or the protected-mode driver is disabled and then re-enabled. Some PCI controller drivers are not  designed for dynamic enabling and disabling, and can cause the protected-mode driver to fail initialization.

remove the NOIDE entry from the following registry key:


  HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\SERVICES\VXD\IOS

 

  After you update the registry, restart Windows. Windows will then attempt to initialize the protected-mode driver for the controller. If no problems are encountered, the file system and virtual memory will operate in 32-bit mode, and Device Manager will not display an exclamation point in a yellow circle for the IDE channels.
If the protected-mode driver is not initialized properly, an error message will be displayed and the NOIDE registry entry will be re-created. Windows will use the MS-DOS compatibility mode file system the next time you start the computer.
0
Do You Have a Trusted Wireless Environment?

A Trusted Wireless Environment is a framework for building a complete Wi-Fi network that is fast, easy to manage, and secure.

CyberNerdCommented:
You may have a out of date BIOS for your current motherboad. Find out with your vendor for your motherboard's website and download the latest version of BIOS and flash your motherboard.  I certainly fixed in several occasions by updating the BIOS and reinstalling Windows 95/98.  So what kind of motherboard do you have?
0
wombat29Commented:
try just re installing the driver for the cd drive!!!
0
billkoCommented:
rayt333:
Too bad the user said that the CD-ROM was working, and now it's not.  I think your theory is more likely in a brand new install, not in a situation where the CD-ROM suddenly stopped working.

CyberNerd:
Same thing.  A BIOS revision problem is not likely to be the cause of a CD-ROM suddenly failing.

jhance is on the right track.  It definitely looks like the motherboard IDE port(s) gave up the ghost.  It may also be that your BIOS was corrupted somehow.  Not likely, but I've seen it every do often at the company that I do hardware tech support for.

Bill
0
netmageCommented:
If you installed the DOS drivers for this cdrom it would have most likely installed the MSCDEX driver in the autoexec.bat.

As this is a 16 bit driver and windows is 32 bit OS then the best you can look forward to is compatibility mode for the drive.

However, with win95 and any busmaster drivers you may have installed the system may become unstable and refuse to recognise the cdrom.

The fix is to edit autoexec.bat and look for the line that has MSCDEX.exe.
Place the letters REM at the begining of the line.
This tells msdos to ignore the line.

I realise that this comment is similar to rayt333's but i'm trying to establish the direct cause from a different angle.

Netmage

0
billkoCommented:
netmage:
Unfortunately, I have to mostly disagree with you.  Although it is possible for a problem like this to occur, the fact is that if this were the actual problem, the user would have had problems right from the beginning.  It would not suddenly become unstable after a track record of working fine.  Rather, the user would have experienced problems on and off over the whole system's lifespan.

Bill
0
1cellCommented:
restart in DOS and at the c: type:

fdisk /mbr
hit enter
repeat a few times

0
rayt333Commented:
I am confused here, bztrybxw asked the question but billko is the one stating the solutions didn't work??? Is this the same person or is billko just pretending to know more then everybody that is trying to help? But is offering no solutions ??

billko
If you are not the same person who asked the question then why are saying negative things about everybody's comment? Please let the questioner try the offered solutions and stop making negative remarks since it shows how little you actually know as compared to what you do know.

bztrybxw stated <the cd rom was working fine and then i got a GPF in windows  while running outlook.  when i rebooted the machine thats when this all started>
If the protected-mode driver is not initialized properly, an error message will be displayed and the NOIDE registry entry will be re-created..
This is the reason for this suggestion, if the entry is not in the registry then we can look elsewhere.
This can occur if the protected-mode driver for the hard disk controller was not properly initialized when you started Windows 98 previously. When this occurs, a noide entry is placed in the registry, preventing Windows 98 from making future attempts to initialize the protected-mode driver.
Removing and reinstalling the hard disk controller does not resolve the problem.  
0
billkoCommented:
rayt333:

Then you can explain to me why it's not the hardware if the cd-rom/hard drive combo works right on an identical machine, but not on the suspect one?  Hmmm...?

Bill
0
billkoCommented:
rayt333:

I forgot to tell you that in my first post, I already offered a solution:

....jhance is on the right track.  It definitely looks like the motherboard IDE port(s) gave up the ghost...

Bill
0
netmageCommented:
Bilko,this is waste of space being critical of comments but i'll play the pointless game.

original question: "rom drive in another machine"

Bilko, wed 24th Nov: "works right on an identical machine"

There could be countless things different between these machines.
ie: A486 Cyrix compared to a PII 400.

My point here is that i believe it isn't in the interest of the questioner for experts to be critical on possible alternate untested ideas that have been posted as comments.

The comments at times may be way off track to other experts interpretations but if the machine isn't in front of an expert doing the testing, what may seem apparent in text in a web browser may not exactly represent the real problem.

On the other hand, i myself will flame answers that are so obviously wrong as to be silly or blatantly posted without consideration for comments already available, but in my flamming i will offer the correct solution if i know it.
I might lose the chance at the getting the points but do we contribute here for the points or to gain knowledge from other experts and get a sense of acheivement by helping others from a hobby called Experts-Exchange?

Netmage


Sorry bztrybxw for wasting your space.
I should have offered more info on your problem but at this stage i think we need feedback from you.
 
 
0
billkoCommented:
I only consider my last two posts to really be  flaming.  I will attempt to defend my opinions here.  The point was NOT to make these people look foolish, but to try to sort the theories in some relative way.


I DON'T believe rayt333 ranks high as a possiblity because he refutes his own arguement by saying:

"If the protected-mode driver is not initialized properly, an error message will be displayed and the NOIDE registry entry will be re-created. Windows will use the MS-DOS compatibility mode file system the next time you start the computer."

Right.  That means that his setup should STILL work, even if it's working in a crippled state.  Besides, the user's complaint wasn't "One day Iwas using my computer and I got a GPF,  and the next time I booted up I got this message saying that windows was using DOS-Compatible drivers," the user said he couldn't use the setup, period.  I've been there plenty of time, myself.  I have a SCSI card that doesn't load the right drivers when I first install Windows95, and I have to suffer through the DOS-Compatible mode until I can load the drivers.


I not only think CyberNerd's theory is incorrect, I think it's a tad dangerous.  Flashing the BIOS when not necessary is always a gamble that could leave you with a broken motherboard.  Granted, the fact that the other motherboard worked and the suspect one doesn't, DOESN'T refute his theory, because the motherboards may have diferen't BIOS'. but a BIOS problem always rears it's ugly head right away.  It's not going to lay low for a long time time only to bite you in the ass suddenly one day.  I could go along with the theory that BIOS settings may have become corrupt, as I have offered in one of my first posts, but this usually only means looking through the BIOS settings and making sure they're right.  While this theory ranks higher than the last in probability, I would try almost anything else before flashing the BIOS.


I DO support jhance's answer though, because a sudden failure, especially where the failure was not immediately following a change inthe machine's setup (hardware or software) nearly ALWAYS points to a hardware failure for the simple fact that harware is physical.  Things break, things get worn, things overheat.  Software will stay good until you do something to make it bad, or hardware fails and corrupts the hard drive.  That's the main reason I refute rayt333's theory.  If the drivers were the real problem, it would have failed the first time he ever booted the machine up after the initial install.  The machine wouldn't wait around for a long time, then suddeny say, "I've been thinking about those drivers for quite a while, and I've decided I don't like them.  I', not going to work any more."  It would have decided that the first time it booted up with that configuration.

Now here's the MAIN reason why I endorse jhance's answer.  It works on an identical setup.  All things being equal, he swapped out the hard drive/cd-rom combo between a known good machine and the suspect one, and it FAILED in the suspect machine.  If the setups were TRULY identical, the combo WILL WORK, but it DOESN'T, suggesting the setups are NOT identical.  Since the user said everything between the two machines are the same, the likely reason that they are not identical is that one of them failed in some way.  Swapping components is the fastest, most efficient (though brutal) way of determining hardware or software problems.


Part of my job at work is to determine whether the software team or the hardware team should work on a call.  I'm rarely wrong.


You are welcome to rip my logic to shreds.  Despite the tone of my last few posts, if someone can come up with a better explanation than jhance's,I'll change my viewpoint right around.  I'm betting that you won't find much to argue about, though.

Sincerely,

Bill
0
rayt333Commented:
billko
You stated < I'm rarely wrong.>

We bow to your greater knowledge but in this case maybe you should reread what  jhance said (whom you agreed with) and my comment which was on the same line (which you said was wrong) DUH???  the real difference was I explained how to force the machine to use the right driver. Maybe you should let the questioner decide what resolves the problem, your negative comments does not help solve anything and maybe you need to take a chill pill and let the troubleshooting solve the problem.


bztrybxw
Are you still there?
Please don't let the flaming comments drive you away, sometimes you get people here who offers no help but flames those who do. If only they could grow up a little they would see how foolish they make themself look
0
billkoCommented:
Well, rayt333, you know what?  You're absolutely right.  I guess that was one of those rare times.  ;)

No wonder you guys got all confused.  It was me, in the first place, who read his reply incorrectly.  Now I understand why you guys thought (still think) I'm nuts.

Okay, you're right.  I actually bow to your literary skills, which seemed to have escaped me at the most critical time.

I'll just go on record saying I believe it to be a hardware issue, the motherboard in particular, and leave it at that.

My apologies for confusing the issue and muddying the water.  You're right.  Let's just get constructive around here.

Bill
0
cmarks55Commented:
interresting thread....

anyway, the question states that the CDROM still works in DOS, therefore a hardware issue is out of the question (in my opinion).  The problem either lies in the corruption of the current drivers or a registry change.  I believe this because the last line of the question states there was a GPF in Outlook, and that could have easily corrupted some files or screwed up the registry.

bztrybxw, if you're still with us, try reinstalling the drivers (if there's an install disk) but first delete any reference to the cdrom in config.sys and autoexec.bad
-of course you're going to make backups of these files before changing them-
start->run, type "sysedit"
put REM in front of the line in config.sys relating to teh CD (should contain "CD0001 /D:" or simmilar in the line, and the autoexec should reference the CD0001 (or whatever it is in config)).
Reboot, see if it works.
If not, use the install disk, reboot, see if it works in Windows and also try DOS.

Please let us know if you have tried any of the suggestions listed in this thread (there are many).

Thanks,

Colby.
0
billkoCommented:
cmarks55:

I will stand down on this issue because I've already made too many mistakes and defer the solution to someone else.  One other thing I've learned from experience is once you start thinking down the wrong track, it's best to let another set of eyes look at the problem.

Despite all my postings here to the contrary, I think *I'm* the one who got it wrong, and there's a lot of other good suggestions here.

Bill
0
tortcatCommented:
Run a virus scan and i will imagine you find that u have a virus in your machine. The fact that the cd rom wont work in 95 but WILL work in dos mode, and that it works in other machines is a classic symptom of a virus under windows95.  The GPF u got while in outlook is a clue also. There are several macro virus that will cause a GPF and then when u reboot your machine u will probably see that u have at the very least a boot sectpr virus and i wouldnt be surprised to see u have more then one virus on your machine.  We here at Origin have seen this before... hence the reason i am just jumping in with an answer.

get a emergency boot disk ( anit-virsus) that came with your antiviralsoftware and boot to it OR get the disk from a friendds computer LIke macafee or norton...


Ill bet u find this will fix your problem
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
bztrybxwAuthor Commented:
Holy Cr$$  .... that was it!!  I had a disk that came with my macafe software ( which i didnt have installed DOH!!)... it said i had a stealth c, a new york and something called  a gpmacro.somehting...( sorry didnt write down the whole name)

The cd is now there and it shows up just fine and works!!

Wonder why Teac couldnt tell me that?   I have increased the poijt to 400 tort thats all i ahve ... this is great thanks alot!!!!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Hardware

From novice to tech pro — start learning today.