Problems with Nero

... of the CD-ROM drive

Initially please check if Nero already recognizes the CD-ROM drive. You can find this out by checking if the menu entry CD recoder->Autodetect CD-ROM... is selectable. If this menu item is selectable, then please have the CD-ROM drive detected. to do this you either need the Nero-CD or you download the compressed image of the test CD from the ahead WebSite.
Please check if Nero after the installation of the Nero ASPI drivers, recognizes the drive.
Please check if Windows itself recognizes the device. In Windows 95 you can do this in Control Panel->System->Device Manager->CD-ROM . The drive must be there, there must be no exclamation mark and apart from that, the drive should not be deactivated. Some of the causes mentioned in the following may in part concern the problem of Windows itself not recognizing the drive.
If the device which is not recognized is a SCSI device, then please continue with 4.

Please check if the Nero Driver is installed.
Please check if DMA is deactivated. On this, see DMA Option
Is a busmaster driver active? If yes, then please check if there are new drivers (in particular in the case of mainboards with an Intel, VIA or ALI chip set) and download these. If this doesn't help, then please deactivate the busmaster driver. See Deinstalling the busmaster driver or deactivating the secondary port .

Information on the busmaster driver: http://24.7.149.52/ (used to be called: bmdrivers.com)

If the CD-ROM drive is connected to the secondary port, then please check if the port is also active. There are BIOS versions which only activate the port if one or several harddisks are connected to the secondary port. If you have a BIOS which behaves like this, then you must connect the drive to a port which has a harddisk connected to it.
In some cases Nero (and sometimes Windows as well) can not recognize the device if in the BIOS the PIO access mode on the drive is set to AUTO , in particular if a harddisk is also connected via the same cable as well. Please check if the drive is recognized if the value is set at 0. If this is case, then increase the PIO mode step by step.
In some cases Nero (and Windows) do not recognize the drive if it is jumped as a slave and it is the only device connected to the IDE port. Please jump it as a master for test purposes.
If you use a mainboard with an 82371SB (PIIX3) or an 82371AB (PIIX4) chip set and you see the following line in the Device Manager under harddisk controller

Primary IDE Controller (single FIFO)

Standard Dual PCI IDE Controller

Standard IDE/ESDI Hard Disk Controller

then you Windows 95 version does not recognize the 82371SB PIIX3 or the 82371AB PIIX4 controller. This means that BIOS will deactivate the secondary IDE port when next rebooted.

In this case the file mshdc.inf must be replaced by a corrected one: ftp://download.intel.com/design/pcisets/setupex.exe

One problem which mainboards have with the 82371SB PIIX3 or the 82371AB PIIX4 controller and the original Windows 95 version (and 95a) affects

Numerous drives do not stick to the ATAPI interface definitions and are not recognized by Windows or do not function correctly if it is the only device connected to the secondary port. Windows sometimes even finds a device which is not connected (ghost device). As a result, the secondary port is deactivated by the system.

Whether there is such a problem can be determined as follows:

Check in the Device Manager under harddisk controller if the secondary port is in conflict with another device or if it is not working correctly. Sometimes the CD-ROM drive is recognized in the Device Manager but it doesn't work correctly (in particular not in Nero).

The best solution in this case is to connect the drive to the primary port (with a connected hardisk), get hold of the newest versionsof the Flash-BIOS and use the newest Windows 95 driver for the CD-ROM drive.

If you are using Windows 95 and a mainboard with one of the following Intel chip sets

440GX, 440BX, 440LX, 440EX, 430TX

and you have not yet downloaded the INF update file, then you should do so now: http://developer.intel.com/design/chipsets/drivers/95license.htm

If you are using Windows 98 and a mainboard with one of the following Intel chip sets:

440GX

and you have not yet downloaded the INF update file, then you should do so now: http://developer.intel.com/design/chipsets/drivers/98license.htm

If you are using a mainboard with an SIS chip set (e.g.: ASUS SP97-V with chip set SIS5598) and you are using Ultra-DMA drivers, then it is possible that an UltraDMA driver is causing the problem. Please deinstall the Ultra-DMA driver.
If you are using a mainboard with an ETEQ chip set and you are using its busmaster driver, then you had better not ignore their advice:

In some cases it's better to use the default driver, especially with some ATAPI CD-ROM models, which may not operate after installation of these ETEQ drivers.(from: ftp://ftp.soyo.nl/Drivers/Chipsets/ETEQ/IDE/eteq2133_readme.txt)

A drive is not always found by Nero if it is connected to the soundcard, particularly if its IDE port is defective or if the IDE port does not support the ATAPI protocol sufficiently.
A CD-ROM drive is sometimes not detected after installing another harddisk or is contacted in compatibility mode. More on this in the registration under:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\IOS

remove the entry NOIDE if present. Then restart the system.

Please check that the jumpers concerning the slave and master are set correctly. As some drives do not work together if they connected to the same port, they should be connected to another port for test purposes.
If you are using the original Windows 95 version or the 95a version, then it is possible that the drive may in part not be recognized if it is connected to the slave of the primary port or to the secondary port. This problem was not solved until Windows 95b.
If you are working in Windows NT and are not using an Adaptec SCSI hostadapter: Please check if you can solve the problem by installing the drivers listed in the following:

ftp://ftp.symbios.com/pub/symchips/scsi/drivers/Windows_Drivers/WindowsNT/I386/Tools/ntaspi.exe

This entry only applies to SCSI-devices

Please look initially under Recommended hardware settings check if your device is connected correctly.
Please use SCSI cabling error to check if you cabling/termination is correct.
At the moment devices are not recognized if SCSI connected to ID 7 or higher. Please allocate the device an SCSI ID of less than 7.
Numerous SCSI devices need a RESET signal at the start, e.g. the TEAC drives. For this reason for the SCSI hostadapter the following option must be set in the BIOS:

Advanced Configuration Option -> Reset SCSI-Bus at IC Initialization

There are SCSI hostadapters for which in the case of a warmstart the RESET signal is created too briefly, e.g. Tekram and Symbios SCSI hostadapters so that some CD-ROM drives are not recognized. e.g.: TEAC 51SK. Here the only solution is to exchange the drive or the SCSI hostadapter.

The option parity always has to be enabled (on all devices and on the SCSI card)
One case is known in which the drive was not recognized because a SCSI scanner was installed and the SCSI harddisk was not set as ID 0 or ID 1.

Please SCSI Set the ID of the harddisk to ID 0 or ID 1.

If you are using a mainboard which has an OnboardSCSI has a controller, then for some cards (PCI/AGP) it should be ensured that they are not connected to the same IRQ and the onboard-SCSI controller is allocated, as many cards are not capable of sharing IRQs, e.g. graphics cards with the Riva TNT chip set.
Please check that the termination is correct, i.e. all ends and no other device inbetween, that there is no T-cabling and that each device has its own ID allocated to it.
If a SCSI I/II device is connected to a Wide Controller, than this has to be explicitly explained to the BIOS:

example: For the AHA2940/UW-BIOS you can set the option of not-wide-devices being recongnized as well. This is done using SCSISelect in item Additional Options by setting the option Initiate Wide Negotiation of the affected SCSI-device to no.

IF you are working in Windows NT and the non-recognition of a drive only occurred after installing a service pack, then presumably the drivers of the SCSI-hostadapter have been overwritten. Please reinstall the drivers of the SCSI hostadapter.
If you are using an daptec AHA2940AU hostadapter, then you should at least update to the BIOS version 1.32
If you are using an external SCSI device, then you should make sure that the cabling is high quality. On this see SCSI cabling error.

The CD-ROM drive or the burner is not recognized until the warm start.

Presumably a quantum harddisk is connected in the system. On starting these harddisks need a relatively large amount of power. No remedy is known.

There has been one case in which the CD-ROM was no longer recognized after the memory was increased from 32MB to 160 MB. This could be seen by the fact that in the Device Manager in system expansion for PnP BIOS e there was an exclamation mark.

Please remove the entry system expansion for PnP BIOS e and start Windows again as this causes the resources an be distributed newly and (usually) correctly

Please check under Start->Settings->Control Panel->Device Manager, if there is an exclamation mark under Harddisk Controller for the primary or secondary port.

If this is the case, then then is a problem. Please read the following article:

http://support.microsoft.com/support/kb/articles/q151/9/11.asp (MS-DOS Compatibility Mode Problems with PCI-IDE Controllers)

Please check under Start->Settings->Control Panel->System->Performance, whether the 32Bit file system driver and the 32Bit virtual driver are active.

If this is not the case, then there is a problem. Please read the following article:

http://support.microsoft.com/support/kb/articles/q151/9/11.asp (MS-DOS Compatibility Mode Problems with PCI-IDE Controllers)

It is possible that a virus is active. Bootsector viruses in particular can cause a drive not to be recognized.

Please check your system for viruses with up-to-date antivirus software and remove these.

There have been cases in which the drive was not recognized because the SCSI software for a scanner (e.g.:EZ-Lite for the Agfa Snapscan) prevented this.

Deinstall the software. Unfortunately the changed drivers are often not replaced again by the original drivers. The changed drivers are usually the WinASPI drivers and the SCSI1HLP.VXD file. Replace these with original Windows 95 drivers.

Please check if the WinASPI driver layer is installed correctly. To do so, download the following program: ftp://ftp.adaptec.com/pub/BBS/win95/aspichk.exe
Sometimes the drivers of scanner software overwrite the WinASPI drivers. An update to the WinASPI drivers by Adaptec would help if there is an Adaptec SCSI-Controller in the system.

If you use an Adaptec SCSI hostadapter, then you can download the drivers from the following address: ftp://ftp.adaptec.com/pub/BBS/win95/aspi32.exe
Otherwise please install the original Windows 95 ASPI driver.

Sometimes scanner programs cause problems in particular if there is more than one host adapter in the system. Please download and install the newest drivers for your scanner. For example old driver versions of some HP scanners (e.g.: 5100C at the parallel port) prevent drives being recognized.
If you are using a ZIP drive or a JAZ drive in the parallel port, then you probably have the software GUEST.EXE installed (is loaded by the AUTOEXEC.BAT). This software doesn't always cause problems directly after being installed but often only after other programs have been installed, e.g. the Internet Explorer 5.0. The reason is that the drivers of this software simulate a SCSI connection. The only solution known to us is to newly install Windows 95/98 (it doesn't help to install it on top) and to do without the software GUEST.EXE as it is not known which drivers have been overwritten and which changes have been carried out in the registration.
Some programs overwrite DLL files so that Nero can not find a drive. e.g.: Whereisit.
If you use a mainboard with the Aladin5 chip set, then you should upgrade to the newest busmaster driver version.
If CD-ROM drive which is not found is connected to an NT computer contacted via the network, then presumably access to the CD-ROM drive has been blocked for all users apart from the user currently logged onto the NT computer.

On this, read the following article: http://support.microsoft.com/support/kb/articles/q172/5/20.asp (Access Denied Error When Trying to Access a Shared CD-ROM).

For some devices, special drivers have to be installed:

e.g. for the Matsuhita CR-581-M. To be able to use this drive, the driver MKEATAPI.MPD (Mini Device Port by Panasonic) has to be loaded. However, this driver prevents burning on IDE CD burner.

Please check if REAL Mode drivers are loaded for the CD-ROM drive. Drivers of this kind are loaded by the CONFIG.SYS or AUTOEXEC.BAT file.

For further information, refer to: Real Mode driver

Please check if any DOS-ASPI drivers are being loaded (CONFIG.SYS/AUTOEXEC.BAT). These DOS-ASPI drivers can cause problems and should therefore not be loaded.
If you use an IDE CD changer and are working under Windows 95 OSR2, OSR2.1 or OSR2.5, then you should read the following article:

http://support.microsoft.com/support/kb/articles/q194/9/36.asp (ATAPI CD-ROM Changer Miniport Driver Is Not Properly Supported)

Sometimes Windows 95 or Nero does not recognize an old CD-ROM drive if the sollowing settings are not adjusted.

Please click on Windows under Start and then on execute.. There please type in "sysedit" (without inverted commas) and now click on OK.
In the menu window click on SYSTEM.INI.
Now look in the current window for the section [386enh] .
In this section, add both the following lines providing they are not already there:

virtualhdirq=false

32bitdiskaccess=off

If you have updated from Windows 95 to Windows 98 and the CD-ROM drive or the CD burner is not recognized or there are other problems with your harddisk or the CD-ROM drive or CD burner , then please read the following article:

http://support.microsoft.com/support/kb/articles/q189/0/92.asp (Problems with Hard Disk and CD-ROM Drive After Upgrading)

and

http://support.microsoft.com/support/kb/articles/q189/5/18.asp (Problems with Hard Disk Controller After Upgrading to Windows 98)

If you have a: Intel 82371SB PIIX3 IDE Controller you are using Windows 95 (not OSR2 or newer) and drives are not recognized, then you should read the following article: http://support.microsoft.com/support/kb/articles/q156/9/40.asp
If the drive is only contacted in the compatability mode, then please read the following article:

http://support.microsoft.com/support/kb/articles/q151/9/11.asp (MS-DOS Compatibility Mode Problems with PCI-IDE Controllers)

and

http://support.microsoft.com/support/kb/articles/q151/6/34.asp (Protected-Mode CD-ROM Drive Support in Windows)

There are CD-ROM drives which only function currently if real-mode drivers are loaded. Such drives may not work in Nero or may not be recognized.

On this, refer to the article: http://support.microsoft.com/support/kb/articles/Q131/4/99.asp (CD-ROM Drives Requiring Real-Mode Drivers)

The following drives currently require real-mode drivers (list is not complete):

Backpack CD-ROM (External/Parallel Port) von Micro Solutions
CD-ROM devices conneted to Mozart soundcards
Chinon CDS-435 oder CDS-535
Creative Labs Sound Blaster Value CD4x MK4062
Matsushita or Panasonic CD-ROM devices to Ensoniq Soundscape cards
Media Vision Reno
NEC CDR-38, NEC CDR-250, CDR-260, CDR-260R, CDR-260GW
NEC 55-JD
Philips CD-ROM connected to Media Vision Fusion 16 soundcard
Philips CM205 and CM206 CD-ROM drives (possibly also CM207)
Pinnacle Micro PCD-100
Sanyo (TORISAN) CDR-C3G Multidisk ATAPI CD-ROM
Sony CDU-6201-20
Teac CD55A CD-ROM
Wearnes CDD-110
Mitsumi FX001D & FX001 CD-ROM drives

If you are working in Windows NT, you should read the following article:

http://support.microsoft.com/support/kb/articles/Q126/3/80.asp (Troubleshooting CD-ROM Problems in Windows NT).

If you are using more than two IDE controllers, then you should also read the following article:

http://support.microsoft.com/support/kb/articles/Q103/9/34.asp (How to Add More Than Two IDE or ESDI Drives in Windows NT)

If you are using a CD changer, read the following:

http://support.microsoft.com/support/kb/articles/q189/0/13.asp (Atapi.sys Does Not Support Multiple Logical Devices)

If you are working in NT and a connected drive is not contactable, then you should check if the drive has possibly been omitted from those detected. On this, read the following article:

http://support.microsoft.com/support/kb/articles/Q158/4/57.asp (Defining Local and Remote Drive Visibility Under WinNT 4.0)

If you own a Philips DR-UA124X CD-ROM drive, then you should read the following article:

http://support.microsoft.com/support/kb/articles/q188/2/94.asp (Pioneer DR-UA124X CD-ROM Drive Disables IDE Port)

If you are working in Windows NT and are using a Sony Spressa CDU920S SCSI CD burner and the drive is not recognized in NT, then you should read the following article:

http://support.microsoft.com/support/kb/articles/q164/4/34.asp (Sony Spressa SCSI CD-ROM Drive May Not Be Detected

If you are working in Windows NT and are using a Panasonic KXL-D740 4X CD-ROM drive, then you should read the following article:

http://support.microsoft.com/support/kb/articles/q155/8/24.asp (Installing a Panasonic KXL-D740 4X CDROM using KXLC002)

If Windows itself doesn't recognize the device correctly, then please disconnect the drive and all other CD-ROM drives from the system. Then run up Windows 95/98 in a secure mode and remove all CD-ROM drives in Start->Settings->Control Panel->System->Device Manager->CD-ROM . Then restart Windows, run it down and then connect all the drives again. Now restart Windows.