|
|||||||
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
#1 |
|
Member (2 bit)
Join Date: May 2000
Location: Shreveport, LA
Posts: 2
|
I have a Crystal PnP Audio System CODEC as my sound card on my computer system. I am running Windows 98. Every time I restart or turn on my computer a pop up white window says cwdaudio.drv. I click OK and then the driver is never installed making me lose all my sound. I reinstall the drivers for the sound card and the sound works again. But there’s a catch, every time I try to reboot my computer the message appears again and the driver doesn’t work again. I have to reinstall my drivers again in order to get sound. I really don’t want to install sound drivers every time I reboot my computer.
The error message I get when I go to device manager when the sound card isn’t working is as follows: The MMDEVLDR.VXD device loader(s) for this device could not load the device driver. [Code 2] To fix this, click update driver to update the device driver. I have the latest driver and this is the driver that worked previously for the system for over a year now. So where do you think the problem lies? |
|
|
|
|
|
#2 |
|
Member (2 bit)
Join Date: May 2000
Location: Shreveport, LA
Posts: 2
|
What is the best way to check for DMA and IRQ conflicts and how do I knkow what changes to make? I have let Windows find the device and I still got the same results. thanks for your help.
|
|
|
|
|
|
#3 |
|
Member (8 bit)
Join Date: Jun 1999
Location: Riverside, CA
Posts: 160
|
Hi,
Have you checked to see if there any IRQ or DMA conflicts in the device manager? Have you tried removing the card from the device manager and letting windows find it and reinstall it? Other than those two suggestions, I don't see why the system won't retain the driver. RON |
|
|
|
|
|
#4 |
|
Member (8 bit)
Join Date: Jun 1999
Location: Riverside, CA
Posts: 160
|
To check for conflict you go into the My Computer icon, open up Control Panel, Go into the System icon. Then open the Device Manager and look to see if there are any exclamation marks on any devices listed, especially the sound card. If there is, it is conflicting with another device, like a mouse or modem. At that point I would suggest highlighting the sound card and hitting "remove" at the bottom. Say yes to confirm it and then shut down your computer.
After you have it turned off, change the sound card to another slot on the board where it will fit, making sure it is firmly seated. Then, restart the system and let it boot up and let W95 or W98 find it again. Then try to renistall the driver when it asks for it. There is a way to manually change the device IRQ's and addresses in the Device Manager, but it can get tricky if your not sure what you are doing. Try the above first and see if that works. The more knowledgeble techs in this forum can walk you through the manual changes if it is necessary. Ron |
|
|
|
|
|
#5 |
|
Member (9 bit)
Join Date: Oct 1999
Posts: 282
|
Error code below applied for Windows 95 and also Windows 98.
Code 1-3 Go to the Device Manager and remove the device. Then, use the Add New Hardware wizard (in Control Panel) to reinstall driver support for the device. Code 4 Go to the Device Manager and remove the device. Then, use the Add New Hardware wizard (in Control Panel) to reinstall driver support for the device. If, after doing this, you still get the error code, contact the manufacturer of the device and ask for an updated INF file for it. Code 5 Go to the Device Manager and remove the device. Then, use the Add New Hardware wizard (in Control Panel) to reinstall driver support for the device. Code 6 A Code 6 error will occur if there is a resource conflict with another device. To resolve the conflict, use the Device Manager to assign the device an available resource. You may have to set jumpers/switches on the device itself, so that it will try to use the free resource you assign to it. Code 7 A Code 7 error means that a device is not configurable. If the device is working properly despite the error code, then you have nothing to worry about. If it is not working properly, go to the Device Manager and remove it. Next, use the Add New Hardware wizard (in Control Panel) to reinstall driver support for the device. If it still won’t work, get an updated driver from the device manufacturer. Code 8 Go to the Device Manager and remove the device. Then use the Add New Hardware wizard (in Control Panel) to reinstall driver support for the device. If, after doing this, you still get this error code, contact the device manufacturer and ask for an updated INF file for it. Code 9 Go to the Device Manager and remove the device. Then use the Add New Hardware wizard (in Control Panel) to reinstall driver support for the device. If, after doing this, you still get the error code, contact the device manufacturer and ask them to help you check the Windows 95 registry setting for your computer. Code 10 A Code 10 error occurs when a device is not detected or working properly. First, see if all the cable connections are okay, if adapter cards are fully inserted into their slots, and if ribbon cables or power cables are connected properly. If you installed the wrong driver for a device, you may also get a code 10 error. Even though most computers now have Plug and Play capability, sometimes they don’t perform perfectly and neglect to assign a resource to a Plug and Play device (resulting in a code 10 error). In some cases, switching the ailing adapter to another helps. You might also try disabling the adapter’s Plug and Play feature and then reinstalling it as a non-Plug and Play card (this can be done on most well designed Plug and Play cards). Plug and Play is not always at fault. Many of today’s Plug and Play computers feature a motherboard CMOS setup that includes a section for fine-tuning Plug and Play operations. If that section is improperly set, it could lead to a code 10 error. This can usually be resolved. Code 11 Go to the Device Manager and remove the device. Then use the Add New Hardware wizard (in Control Panel) to reinstall driver support for the device. Code 12 A code 12 error (like code 6) means that you have a resource conflict. To resolve the conflict, use the Device Manager to assign the device a resource which is free. You may have to set jumpers/switches on the device itself, so that it will use the free resource you assign to it. Code 13 Go to the Device Manager and remove the device. Then use the Add New Hardware wizard (in Control Panel) to reinstall driver support for the device. Code 14 When you get a code 14 error, just shut down your system, turn your computer power off, and then on again. Code 15 Code 15 errors indicate there is a resource conflict. Use the Device Manager to assign a free resource to the device. You may have to set jumpers/switches on the device itself, so that it will use the resource you assign to it. Code 16 When an error code 16 occurs, you will need to tell Window 95 what resources the device is using. Go to the Device Manager and double-click the device’s icon to bring up its Properties dialog box. Next, click on the Resources tab to flip to the corresponding page and enter the needed resource information into the appropriate boxes. Code 17 Error code 17 applies to multiple-function devices with bad INF files. Go to the Device Manager and remove the device (remove its child devices first). Then, use the Add New Hardware wizard (in the Control Panel) to reinstall driver support for the device. If, after taking these steps, you still get a code 17 error, contact the device manufacturer and ask for an updated INF file. Code 18-20 Go to the Device Manager and remove the device. Then, use the Add New Hardware Wizard (in Control Panel) to reinstall its driver support. Code 21 Shut down your system and turn your computer power off, and then on again. Code 22 Error code 22 occurs when devices have been disabled. To enable the device, go to the Device Manager and double-click on its icon to bring up its Properties dialog box. On the page displayed, look for the Device Usage list box. The Device Usage box lets you configure your computer to run a different set of devices with different configurations. For most users, only one configuration is listed: Original Configuration (Current). To enable the device for this configuration (which is also the current one) just click the checkbox beside it, click OK, and restart your computer. Code 23 Go to the Device Manager and remove the device. Then, use the Add New Hardware wizard (in the Control Panel) to reinstall driver support for the device. Code 24 Code 24 is similar to code 10. Make sure everything is slotted in and connected properly by pulling the card out and reinserting it or seating the card in another slot. Code 25 Code 25 errors supposedly occur only during the first reboot after Windows 95 installation. If you get one, just ignore it. Code 26 Go to the Device Manager and remove the device. Then use the Add New Hardware wizard (in the Control Panel) to reinstall driver support for the device. If, after doing this, you still get error code 26, contact the device’s manufacturer to get updated driver files for it. Code 27 Go to the Device Manager and remove the device. Then use the Add New Hardware wizard (in the Control Panel) to reinstall driver support for the device. Code 28 Code 28 errors mean that the driver support for the device is not set up properly. Go to the Device Manager and double-click the device’s icon to bring up its Properties dialog box. Click the Driver tab to flip to the corresponding page. Click on the Change Driver button to re-specify the driver. Code 29 A code 29 error means that a device is disabled for some reason, and Windows 95 can’t do anything to help. You may be able to resolve the problem by going to the computer’s CMOS setup program (press the delete key during bootup). However, to find out exactly what to change, contact the manufacturer of the device or the computer. Code 30 Code 30 errors indicate the presence of a resource conflict. If a device is using DOS drivers (vs. Windows 95 drivers), Windows 95 may not know what IRQ it is using. If, in addition, a PCI or EISA SCSI controller card happens to use that same IRQ, this error could occur. You may have to remove DOS driver support for the DOS device or reconfigure it to use another IRQ. This would involve editing the Config.sys or Autoexec.bat file where drivers and their settings are recorded in script form. It would also mostly likely involve switching jumpers on the card to get it to use the newly assigned resources. |
|
|
|
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|