CD ROM Drive not recognised 1

[ssidetv]

Having reloaded Windows 98 SE via my CD ROM drive I then set about finding the video drivers to match my display adapter. I opened the cae, had a look round, could not find the make of the motherboard or adapter - disconnecting the daisy-chained data cable that runs from the CD to the HD then the board in the process. I reattached it, put the cae back on and fired it up.
The CD ROM disappeared from My Computer and the Device Manager. I dealt with the video driver issue using other means but cannot resolve the CD ROM.
Data:
*CD ROM is a TTOD CDD1480
*On boot up the TTOD is recognised as the Primary Slave
*In CMOS there is no mention of the TTOD. Primary Slave is NONE.
*When I boot in Safe Mode, Device Manager sees the TTOD. My Computer does not, even though a drive letter has been assigned.
*When I boot in Normal mode, the TTOD disappears again.

Does anyone have any ideas?

Thanks in advance,
Nick

 

[Guest_imported]

last week i have same problem it waas resolve by edit registary entery follow these steps
1. open regedit program.
2. find CD ROM drive in devices trace drive letter key if it blank edit this key assighn any drive letter which is not already assigned to HD or other drives. be sure about it and assign drive letter like that "F:".
3. restart computer your problem resolve if fully drivers loaded already and BIOS setup detect it.

 

[Grenage]

Ok, since you were in the machine the first thing I would do is look back inside, and check all your connections with power and data. Generally speaking the red line on the Data cable points towards the Power socket of the CDROM/Hard Drive.

 

[mudskipper]

I agree...check your cabling. Be sure that if you pulled TWO cables out of the system, that you are chaining your CDROM drive and HDD seperately. Remember, your CDROM drive does not have to detect in BIOS, and setting it to None usually works fine.

If that doesn't work, then boot into safe mode, remove the device from device manager. Restart into normal mode.

If the CDROM drive still does not detect, go to your device manager. At the top of that window, you will have a tab that says &quot;performance&quot;. Click on it. You are looking for the spot that normally says &quot;Your system is configured for optimal performance&quot;. If this is the case, then I am on the wrong track.... If it says &quot;drive <X>: is using MSDOS compatibility mode, then post back and we will suggest things to try for that!!

Good luck ----------------------------------------
Groucho Marx said it best...
&quot;A child of five could understand this. Fetch me a child of five.&quot;

 

[Vicko7]

Please continue with the suggestions, I am having a problem with HP CD-Writer 9100 that has disappreared, and I have that message: &quot;drive <Xdrive C: on PC)is using MSDOS compatibility mode, since then the CD-Writer (Drive D has disappeared as well as the Zip Drive (Drive E. I do have the yellow exclamation point on the Primary and Secondary IDE controller in Device Manager, but don't know what to do next. It seems that the drivers are the correct ones in comparing them to another PC, but apparently the hard drive (C is operating from MS-Dos compatibility mode, while the other drives have disappeared. The user did receive an error message, something about a problem with 32-bit compatibility mode, and it had been chaged, the only option to close the error messsage was &quot;ok&quot;. This happened during a screwed up download of Acrobat Reader 6.0.1. Any ideas?
Much thanks, Vicko

 

[TekTippy4U]

First Uninstall all instances of D/l screwup . empty directories 'TEMP', Temp Inet Files, and Sift thru Downloaded Program Files for unnecessary.....
In device managler remove the all devices with an Exclamation or ?
Unhook the Zip drive, unless you have to boot from it.
Restart and Let windows detect the devices and controllers..have the OS CD handy
What OS?

Once going well.....Then shutdown and Add the Zip back and let windows detect it on boot

TT4U

Notification:
These are just &quot;my&quot; thoughts....and should be carefully measured against other opinions.
Backup All Important Data/Docs..All involved shall be spared the grief.

 

[Vicko7]

Thanks, I'm using Windows 98SE. Device Manager won't let me remove only the Primary IDE and Secondary IDE controllers with the yellow exclamation on them - they are part of the multi-function &quot;parent&quot; device , I'd have to remove the &quot;parent&quot; device which is the &quot;Intel 82371AB/EB PCI Bus Master IDE Controller&quot;.
When I do this, is Window really suppose to detect the devices and controllers and reload properly? (Can you tell I don't trust &quot;Windows&quot;.) Like I don't have another options right now, do I? :-(
Thanks, -V

 

[TekTippy4U]

Just as an aside.the original author's prob was probably arranging the Master/Slave wrong when he re-hooked up the cable, which doesn't seem yo be your problem(just trying to narrow the focus down and zoom in on your particular prob)

Yes, that's correct, it will only let you remove the Parent.
That's the correct controller too &quot;Intel 82371AB/EB PCI Bus Master IDE Controller&quot;....for most Win setups.

Let's go slow here first...What's listed under Driver File details in each of the Children.
Also in Device Manager, click &quot;view by type&quot;....and Right click &quot;Computer&quot; and choose properties....What are the IRQ's listed as for the Controller...you should have 2 instances each for IRQ 14 and IRQ 15....Controller+Primary for 14 and Controller+Secondary for 15.

This is important
Navigate to C:\Windows\System\IOSUBSYS and look for ESDI_506.pdr is it there?



TT4U

Notification:
These are just &quot;my&quot; thoughts....and should be carefully measured against other opinions.
Backup All Important Data/Docs..All involved shall be spared the grief.

 

[Vicko7]

Thanks, Primary IDE Controller (child) Driver File Details lists: C:\WINDOWS\SYSTEM\IOSUBSYS\ESDI_506.pdr, below that also lists: C:\WINDOWS\SYSTEM\VMM32\IOS.vxd
The Secondary IDE Controller Driver File Details lists: the same as above.
Yes, I have 2 instances each for IRQ 14 and IRQ 15....Controller+Primary is 14 and Controller+Secondary is 15. That is correct.
What should be listed for the &quot;Dual IDE Channel Settings&quot; drop down list under the &quot;Settings&quot; tab for the &quot;Intel 82371AB/EB PCI Bus Master IDE Controller&quot;. It may have been set to &quot;Default&quot;, but I'm not sure; I have it on &quot;Both IDE Channels enabled&quot; right now, but it hasn't made a difference in the yellow &quot;!&quot;.
This is important:
Navigate to C:\Windows\System\IOSUBSYS and look for ESDI_506.pdr is it there?
YES, This folder (IOSUBSYS) is there and the file ESDI_506.pdr is there too.
Thank you, What's next?
-Vicko

 

[TekTippy4U]

Both Channels usually are are enabled . One for Primary Master/Slave and one for Secondary Master/Slave...

Above info looks good and correct, however it doesn;t mean no corruption...

I'd like to try a new tack for safety....
We're going Backwards in time and see if we can fix that way.
Restart and As you see the Hard Disk being recognized Press and HOLD the CTRL Key...you're going to activate the Win98 Startup menu....Choose -Command Prompt Only-

At C:\ type
SCANREG /RESTORE (leave a space between G and Restore)
(capitalization doesn't matter either)
hit Enter
Choose a Restore Time and Date (it goes back 5 Days by default)that you're comfortable with, as any changes made, going Backwards in time wise, such as Documents Saved WILL be Undone.
Next to the date it'll say &quot;Started&quot; which means it's a known good copy of the REG.

Most times this works for your situation (It should)..sometimes not...You need to weigh out whether How important any changes (to Data and Doc's especially)you've made over the Last couple of Days are...

Make sure you go FAR BACK ENOUGH in Time (before that Adobe d/l crash)

It's just easier this way for now rather than guessing and replacing drivers and messin with the config...and it'll probably do the trick.

TT4U

Notification:
These are just &quot;my&quot; thoughts....and should be carefully measured against other opinions.
Backup All Important Data/Docs..All involved shall be spared the grief.

 

[Vicko7]

Thank you so much for all the information that has helped to solve the problem. This has got to be the best site to get tech help ever!
After checked everything you suggested and re-checking again (just something I do), I proceeded on with some of the other options. Although I was unable to edit the registry on the first try because the PC locked up again, I opted to try some other things based on some more info that I remembered after writing you. You definitely got me going in the right direction! I am forever thankful, and the user of the hosed PC knows that you helped too, and is forever thankful as well!
Besides all the info you gave me, I also did a search for IDE problems and found info about MS-DOS Compatibility Mode Problems with PCI IDE Controllers (about stuff I remembered after writing to you) and that from the Microsoft Knowledge Base article #151911, the MS-Dos compatibilty mode file system only allows those &quot;real-mode&quot; drivers to load, and the correct drivers for my CD-Writer wouldn't load, that's why my CD-Writer didn't show up in &quot;My Computer&quot; or in the &quot;Device Manager&quot;, or anywhere else for that matter.
The article is great, please refer to it, but here's some info from there:

CAUSE - This behavior can occur if the protected-mode driver for the hard disk controller is not properly initialized when you start Windows. When this occurs, a NOIDE value is placed in the registry which prevents Windows from making future attempts to initialize the protected-mode driver. All Versions - To cause Windows to attempt to reinitialize the protected-mode IDE driver:
Click Start, click Run, type regedit in the Open box, and then press ENTER.
Locate and click the following registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\IOS In the right pane, right-click the NOIDE value, and then click Delete.
Quit Registry Editor.
After you update the registry, restart Windows. Windows attempts to initialize the protected-mode driver for the controller. If Windows can initialize the protected-mode driver for the controller, the file system and virtual memory operate in 32-bit mode and Device Manager does not display an exclamation point in a yellow circle for the IDE channels.
If the protected-mode driver is not initialized properly, you receive an error message and the NOIDE value is re-created. Windows uses the MS-DOS Compatibility mode file system the next time that you start the computer.
Thanks again!
-Vicko

 

[TekTippy4U]

Rock On Vicko7


TT4U

Notification:
These are just &quot;my&quot; thoughts....and should be carefully measured against other opinions.
Backup All Important Data/Docs..All involved shall be spared the grief.

 

[Vicko7]

It's happened again. The MS-Dos compatibilty mode file system only allows those "real-mode" drivers to load, and the drivers for my CD Rom Drive and Zip Drive are not loaded, so it looks like they don't exist. I went back into the Registry and deleted the NO IDE value (NOIDE), then rebooted the PC and the correct drivers loaded again at this point.
My question now is, "why does this keep happening?" It is happening every 2 to 3 months or so. Anyone have any ideas?
Thanks, Vicko7

 

[Dianne316297]

I had a simular problem with a friend's computer and I am still vexed... I was suspecting a virus because of the DOS compatability mode. The Secondary IDE controller was disabled- and I had set it up recently with a fresh install of 98SE. When it happened- it would not even recognize in the BIOS. When I booted into Safe mode- I removed the devices and forced it to re-recognize. All was well- until 2 weeks (Not months) later. I am still having to rip it out from the devices in safe mode and reinstalling the drivers. I'm also looking... Di

 

[TekTippy4U]

Some Possible Answers;

http://www.infinisource.com/techfiles/msdos-compatibility.html

http://www.winguides.com/registry/display.php/288/

http://support.microsoft.com/default.aspx?scid=kb;en-us;151911

http://www.infinisource.com/windows95/tune-40.shtml

http://home.earthlink.net/~billselk/al440lx/bmide.html

http://www.infinisource.com/windows98/tune-35.shtml

TT4U

Notification:
These are just my thoughts....and should be carefully measured against other opinions.
Backup All Important Data/Docs

 

[Vicko7]

Thanks for the reference links TekTippy4U! I'll check them out and will post again if I find a fix for it and I'm able to repair the annoying problem, once and for all! You've always been most helpful!
Thanks again, Vicko7

 

[ceh4702]

Reinstall win98 on top of itself to get rid of the msdos compatability mode. Most likely some file is corrupted.

If you do not like my post feel free to point out your opinion or my errors.