CD-ROM

Reply

  #1  
Old 10-19-01, 06:47 AM
Visiting Guest
Posts: n/a
My CD-ROM does not detect a CD . If i put a CD-ROM Lens Cleaner in my drive Will it still clean the lens even though the drive will not play a CD ?
Thanks "JAKEY"
 
Sponsored Links
  #2  
Old 10-19-01, 02:09 PM
bigmike
Visiting Guest
Posts: n/a
Cool More

What OS is it? 95? 98? ME? Who is the CD maker? Have you reinstalled the drivers for the CD? Go into control panel, system, device manager and see if the CD has any "!" or "X" through the CD. Most likley you need to update your CD drivers. This is a common thing with Windoze. http://www.windrivers.com will be able to find the manufacture for the drivers. You will most likley need the model or at least the speed of the CD.
 
  #3  
Old 10-20-01, 07:05 AM
Visiting Guest
Posts: n/a
Driver in MSDOS

I went to the win Driver & installed a updated driver. It went into MSDOS & i now have a" Drive E " which i didn't have before. When i go to Device Manager & performance Tab it says " Drive E useing MS-DOS compatibility Mode file system", now my system is real slow. Is there a way to take the driver out & get rid of Drive E. I don't care if CD Rom don't work cause it's not working any ways. I will put a new CD-ROM drive in.
Thanks "JAKEY"
 
  #4  
Old 10-20-01, 09:07 AM
bigmike
Visiting Guest
Posts: n/a
Cool remove

Yes, go into device manager and remove the device. Then go into ctrl panel add remove programs and see if the cd shows any program associated with it and remove it. Shut down. Open the case and unplug the IDE cable for the CD. Power too if you want. This will stop Windoze from searching for the device. When you buy the new CD Rom, plug it in and when you boot Windoze should find it as a generic device. After you get the drive running then install the drivers that will come with the new drive.
 
  #5  
Old 10-20-01, 09:54 AM
Visiting Guest
Posts: n/a
Mike, I took it out from Device Manager But can't find anything in CTRL DELETE about CD's. When i get a new Rom & install it with Driver will this one i just installed go away & not load at all in MSDOS ?
I'm going to unplug the rom now.
Thanks "JAKEY"
 
  #6  
Old 10-20-01, 10:13 AM
bigmike
Visiting Guest
Posts: n/a
Cool new

Yes the new software will over write the old. There may not be anything in there as far as programs. When you removed it from device mangler did the MS DOS mode go away?
 
  #7  
Old 10-20-01, 10:57 AM
Visiting Guest
Posts: n/a
Mike. i removed it from device manager but it still loaded in MSDOS until i unpluged the CD-ROM. Thats great as long as the new Rom i'm going to get will over write this one.
Thanks for all your help. "JAKEY"
PS: Got an Opinion on radio Shack CD-ROMS ?
 
  #8  
Old 10-20-01, 11:32 AM
bigmike
Visiting Guest
Posts: n/a
Cool No way

I wouldn't! I would go and buy or get online and buy Creative Labs/3COM. They have been around the most and you can actually get help from them. Always stick to a brand name! Windoze has got a little more lax in what type of equipment you can run on their OS but they were and still are designed to use Creative Labs. Some will disagree with me but what is usualy the first question asked on sound, video etc? Is it Win brand which stinks or Creative? Anyway this is just my opinion but I always use Creative... Radio Sham I mean Shack is good for scanners etc. I actually don't even know who makes RS components...
 
  #9  
Old 10-20-01, 11:37 AM
Visiting Guest
Posts: n/a
Thanks Again for your help Mike. i really appreciate it.
"JAKEY"
 
  #10  
Old 10-22-01, 06:43 AM
Gary Tait
Visiting Guest
Posts: n/a
RS just buys things from various Asian manufacturers.
At one time I think they had their own plants, but not
in the era of Multimedia PCs where this CD-ROM appears
to be from. It is very possibly the drive is a propetary
interface drive requirin you to manually select the drivers
from the Add Hardware control panel (as opposed to
Windows looking for it, it will not know how).
 
  #11  
Old 11-05-01, 08:23 AM
Member
Join Date: Nov 2001
Location: Taylors, SC
Posts: 9,483


Troubleshooting MS-DOS Compatibility Mode on Hard Disks

--------------------------------------------------------------------------------
The information in this article applies to:

Microsoft Windows 95
Microsoft Windows 98
Microsoft Windows 98 Second Edition
Microsoft Windows Millennium Edition

--------------------------------------------------------------------------------


SYMPTOMS
The Performance tab in System properties shows that one or more of the hard disks in your computer is using MS-DOS Compatibility mode. MS-DOS compatibility mode may be in use either for the file system or for virtual memory. You may receive the following message:


Compatibility Mode Paging reduces overall system performance



CAUSE
MS-DOS Compatibility mode may be in use for any of the following reasons:


An "unsafe" device driver, memory-resident program, or virus hooked the INT21h or INT13h chain before Windows is loaded.


The hard disk controller in your computer was not detected by Windows.


The hard disk controller was removed from the current configuration in Device Manager.


There is a resource conflict between the hard disk controller and another hardware device.


The Windows protected-mode driver is missing or damaged.


The Windows 32-bit protected-mode disk drivers detected an unsupportable configuration or incompatible hardware.


You are running Windows Millennium Edition (Me) and have used Drive Copy 2.0 by Powerquest to copy the contents of one hard disk to another hard disk.





RESOLUTION
To correct the behavior, follow these steps:

If you used Drive Image 2.0 by Powerquest, contact Powerquest for a version of the software that is compatible with Windows Me.


Use the Performance tab in System properties to identify which drive is using MS-DOS Compatibility mode and why.

NOTE: Floppy disk drives and CD-ROM drives operating in MS-DOS Compatibility mode cause the Performance tab to display the message "Some drives are using MS-DOS compatibility" for the file system, but this article applies only to troubleshooting hard disks operating in MS-DOS Compatibility mode.

For additional information about troubleshooting floppy disk drives, click the article number below to view the article in the Microsoft Knowledge Base:
Q131690 Troubleshooting Floppy Disk Drive Problems in Windows
If the driver name listed as causing MS-DOS Compatibility mode is Mbrint13.sys, your computer may be infected with a boot-sector virus, or you are running real-mode geometry translation software (for an IDE hard disk with more than 1024 cylinders) that is not compatible with Windows protected-mode disk drivers.

For additional information about real-mode geometry translation software that is compatible with Windows protected-mode disk drivers, click the article number below to view the article in the Microsoft Knowledge Base:
Q126855 Windows Support for Large IDE Hard Disks
Disk Manager 6.03 is supported in protected mode on hard disks on the primary IDE channel and when DriveSpace disk compression is not installed. For drives on the secondary IDE channel, Disk Manager 7.0 or later is required. When using the DriveSpace compression software that is included with Microsoft Windows and Microsoft Plus!, Disk Manager 7.04 or later must be used.

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
Q126855 Windows Support for Large IDE Hard Disks
For additional information about detecting and removing boot-sector viruses, click the article number below to view the article in the Microsoft Knowledge Base:
Q82923 Methods to Detect a Boot-Sector Virus
Q129972 Description of Computer Viruses
Q49500 List of Antivirus Software Vendors



b. If a driver that is listed in the Config.sys file is named, contact the driver's manufacturer to determine whether there is a version of the driver that enables protected-mode access in Windows.


If no driver is listed on the Performance tab, continue with Step 2.


Check to make sure that the hard disk controller is listed in Device Manager. If it is not listed, install it with the Add New Hardware Wizard. If the Wizard does not detect the controller, run the Wizard again but do not let the Wizard detect the hardware in your computer. Instead, select the controller from the hardware list. If the controller is not listed, contact the manufacturer of the hard disk controller to determine whether there is a Windows protected-mode disk driver or a Windows 3.1 32-bit disk access (FastDisk) driver available.

NOTE: If the hard disk controller is listed in Device Manager but has a red X over it, it has been removed from the current hardware profile. Click Properties for the controller in Device Manager, and then click the check box that corresponds to the current hardware profile under Device Usage.


If the hard disk controller is listed in Device Manager but has a yellow exclamation point over it, there is an IRQ, I/O, DMA, or RAM address conflict with another device, the protected-mode driver is absent or damaged, or the "Disable all 32-bit protected-mode disk drivers" check box is selected in File System properties.


Check to make sure that the "Disable all 32-bit protected-mode disk drivers" check box has not been selected on the Troubleshooting tab in File System properties. To access this tab, double-click System in Control Panel, click the Performance tab, and then click File System.


Resolve any resource (IRQ, I/O, DMA, or RAM address) conflicts with other devices. Consult the controller's documentation for information about resource usage and changing resource usage.


Check to make sure that the protected-mode driver is in the Windows\SYSTEM\IOSUBSYS directory and is loading properly. To determine which driver is providing 32-bit disk access, click Properties for the controller in Device Manager and click the Driver tab to see which driver files are associated with the controller.

NOTE: If you are using an IDE, EIDE, or ESDI hard disk controller, the Driver tab may not be present when you click Properties for the controller in Device Manager. Unless you are using a third-party driver, Esdi_506.pdr is the protected-mode driver that is used to provide 32-bit disk access for these controllers.

Restart Windows and press F8 at the "Starting Windows xx" message, and then choose Logged (/Bootlog.txt) start from the Windows Startup Menu. Examine the just-created Bootlog.txt file to determine if the driver listed above is loading properly.

In Windows 98, press and hold the CTRL key until you see the Windows 98 Startup menu, and then choose Logged (/Bootlog.txt).

If the Bootlog.txt file shows an "Init Failure" or "Load Failure" message for the driver listed above, proceed with step D. If the Bootlog.txt file shows an "INITCOMPLETESUCCESS" message for the drive listed above, examine the IOS.LOG file.

Windows creates an Ios.log file in the Windows directory if any drives are using MS-DOS Compatibility mode. The first few lines of the Ios.log file may contain information describing why the protected-mode disk driver failed to load. Please have this information available if you contact Microsoft Product Support Services about this behavior.


Check for the NOIDE value in the registry under:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\IOS
The NOIDE value is placed in the registry when the protected-mode driver for the IDE Controller is not properly initialized.

For additional information about how to troubleshoot NOIDE, click the article number below to view the article in the Microsoft Knowledge Base:
Q151911 MS-DOS Compatibility Mode Problems with PCI IDE Controllers
Make sure the protected-mode driver is not damaged.

For all ESDI and IDE drives, Windows uses ESDI_506.PDR in the IOSUBSYS directory to provide 32-bit disk access. For SCSI controllers, Windows uses SCSIPORT.PDR and a "mini-port" (.MPD) driver to provide 32-bit disk access.

Manually extract the appropriate .pdr or .mpd files from the Windows disks or CD-ROM, or run Setup and choose the Verify option.





Check to see if the Mh32bit.386 driver is being loaded in the System.ini file. Check for a line that reads "device=mh32bit.386." This driver is installed by MicroHouse EZ-Drive software, and is not compatible with the Windows protected-mode disk drivers. This driver is not removed by Windows Setup.


Contact the hard disk controller's manufacturer for information about Windows compatibility. You may be able to get protected-mode, 32-bit disk access in Windows by using one of the following methods:


Disable any enhanced features (such as caching, fast or turbo mode, reduced data transfer rates, and so on) on the controller (SCSI, IDE, or ESDI) or system BIOS (IDE only).


Obtain a protected-mode Windows disk driver, or Windows 3.1 FastDisk driver for the controller.








MORE INFORMATION
A real-mode driver is "safe" if its functionality does not exceed the functionality of the corresponding Windows protected-mode driver. If a real-mode driver is safe, the protected-mode driver can take over all I/O operations for the corresponding device. Otherwise, Windows routes all I/O operations through the real-mode driver.

An example of an unsafe driver is a real-mode IDE/ESDI driver that uses dynamic encryption for security reasons. Since Windows does not provide encryption, Windows does not enable the protected-mode IDE/ESDI driver to take over the real-mode driver. Any real-mode driver with functionality on the following list is considered unsafe:



Data compression that is not compatible with DoubleSpace


Data encryption


Disk mirroring


Bad sector mapping


Fault tolerance (for example, maintenance of ECC correction on a separate disk)


Vendor-specific IOCTLs


Microsoft-defined IOCTLs with vendor-extended features


The safe driver list (the Ios.ini file) is a Windows-maintained list of safe drivers. Each entry in the list identifies a driver or TSR that Windows can take over with the corresponding protected-mode driver. The safe driver list includes the name of the driver or TSR. This name should be the same as the name in the Config.sys or Autoexec.bat file.

Windows does not store the version number of the driver or TSR in the list, so it is the responsibility of the vendor to change the name of the driver if a future version of the driver is enhanced in a manner that makes the driver unsafe.

By default, the following drivers are considered safe:

MS-DOS 5.0-compatible real-mode block device drivers


INT 13 monitors (hooks INT 13 for monitoring INT 13 I/O but does not access the hardware directly or modify the I/O buffer)


INT 13 hooker (hooks INT 13 for altering INT 13 I/O but does not access the hardware directly)


INT 13 driver (provides INT 13 functionality and directly accesses the hardware)


ASPI Manager (implements ASPI for MS-DOS specification)


CAM Manager (implements MS-DOS CAM specification)


NOTE: If the real-mode driver you are using has better performance or provides some functions that are not be present in the Windows protected-mode driver, the driver's vendor should remove the driver from the safe driver list. The system may use real mode to access the drive. If the real-mode driver you are using can be safely taken over by protected-mode drivers, the driver's vendor can add that driver to the safe driver list.

Disk Manager is manufactured by OnTrack Computer Systems, a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.

EZ-Drive is manufactured by Micro House, a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.

Additional query words: ez.exe dm.exe dmdrvr.bin xbios.ovl tshoot noide w95hwfaq win95 win98 win98se winMe winMil Drvdata bin Drvidx bootlog txt config sys or autoexec bat

Keywords : kbenv kbhw kbtshoot kbHardware kbWinME
Issue type : kbprb
Technology : kbWinMEsearch kbWin95search kbWin98search kbWin98SEsearch kbZNotKeyword3 kbWin98 kbWinME kbWin98SE



Last Reviewed: July 24, 2001
2001 Microsoft Corporation. All rights reserved. Terms of Use. Disability/accessibility Privacy Policy







Article ID: Q130179

Last Reviewed:
July 24, 2001

Send to a friend



Provided by
Microsoft Product Support Services



--------------------------------------------------------------------------------

Did the information in this article help answer your question?
Yes
No
Did not apply

Please provide additional comments about this information.
(255 character max)







 
  #12  
Old 11-05-01, 08:39 AM
bigmike
Visiting Guest
Posts: n/a
Cool drivers & ms dos mode

I have tried this last post from chfite and it has never worked, has anyone else had success with it? I have ran across this msdos problem several times and found it to be a driver that was old or not correct.
 
  #13  
Old 11-12-01, 02:30 PM
Visiting Guest
Posts: n/a
MS Dos Compatibility Mode

If you're using Win98 then your system should automatically install all drivers related to your Cdrom drive. Probably the reason you're getting the compatibility message is you have the DOS based drivers loading for the CDrom in your Config.sys and your Autoexec.bat. In your config.sys look for the line that says Device=xxxxx.sys /d:msc0001 or something along those lines.. but you should have a line with at least the /d: put a REM at the beginning of that line, save and close that file. Then open your Autoexec.bat and look for a line with MSCDEX.EXE in it. put a REM at the beging of that line as well. Save that file and then reboot your computer. The next time your computer boots up, it should automatically install the Cdrom drive properly into the system and you should be set to go.
 
Reply

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off


Thread Tools
Search this Thread
Display Modes