Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home
Reply to Message Icon Go to Main Page Icon

Subject: BIOS sees new DVD but Win XP doesn'

Original Message
Name: Mark Denison
Date: February 6, 2008 at 13:03:11 Pacific
Subject: BIOS sees new DVD but Win XP doesn'
OS: WIN XP SP2
CPU/Ram: Athlon 2600+/2x512mb PC27
Model/Manufacturer: Generic PC
Comment:
I replaced my original CD read only player with I/O Magic DVD/CD writer because the CD drive was not recognized by windows. I figured after 5 years or so it was due and wanted to upgrade to write capabilities anyways.

Unfortunately, I ran into the same problem when trying to install the DVD drive. The original drive was connected via IDE2.
So here is what I have tried not necessarily in order (all with no success):
1) I tried a different cable (IDE2)
2) I bought a new cable (IDE2)
3) I attached the DVD drive as the slave to the HD (primary) on IDE1
4) uninstalled in Device Manager and then tried to reinstall
5) reset the CMOS
6) updated and or reinstalled motherboard and chip set drivers as well as the video driver

The DVD drive is correctly identified in the BIOS but not in Win XP. Actually the DVD is in Device Manager but with the yellow exclamation point. On boot, it loads the necessary drivers but then has the error message (in Device Manager "Windows successfully loaded the device driver for this hardware but cannot find the hardware device. (Code 41)"

I have the jumper on the DVD as slave and HD as master. Though the 1st connection (from IDE 1) is to the HD and the 2nd to the DVD (if that matters)

Your help is appreciated.

Mark
__________________
NF2 Ultra A+ nVidia-nForce motherboard
BIOS: Phoenix Technologies, LTD 6.00 PG 11/27/2003
AMD Athlon XP 2600 cpu stock cooling
NVIDIA GeForce4 Ti 4200 with AGP8X
WDC WD1200JB-75CRA0 [Hard drive] (120.00 GB)
TSSTcorp (Samsung) CDDVDW SH-S202N
NVIDIA nForce Networking Controller
NVIDIA(R) nForce(TM) Audio (Realtek alc 650 onboard audio)
2 x 1 512 generic PC2700 ram
Uneec 300 watt power supply
Win XP SP2


Report Offensive Message For Removal

Response Number 1
Name: aegis
Date: February 6, 2008 at 13:38:26 Pacific
Subject: BIOS sees new DVD but Win XP doesn'
Reply: (edit)
You really should have the DVD drive on the second controller. That will speed up transfers between the two drives. It will run almost twice as fast with the drives on different controllers.

"uninstalled in Device Manager and then tried to reinstall"

You shouldn't have to install any drivers. Windows should have the correct drivers.


Report Offensive Follow Up For Removal

Response Number 2
Name: Tubesandwires
Date: February 6, 2008 at 14:32:13 Pacific
Subject: BIOS sees new DVD but Win XP doesn'
Reply: (edit)
Whenever you load Windows from a regular Windows CD (or DVD) from scratch, after Setup is finished you must load the drivers for the mboard, particularly the main chipset drivers, in order for Windows to have the proper drivers for and information about your mboard hardware, including it's AGP or PCI-E, ACPI, and hard drive controller support. If you have the CD that came with the mboard, all the necessary drivers are on it. If you load drivers from the web, brand name system builders and mboard makers often DO NOT have the main chipset drivers listed in the downloads for your model - in that case you must go to the maker of the main chipset's web site, get the drivers, and load them.

If you're absolutely sure the main chipset drivers are loaded, or if you tried loading them and that didn't help, there are other things that can be wrong.

DVD combo drives capable of DVD +R or DVD-R 16X or greater must be connected to 80 wire IDE cables in order to acheive their maximum speeds, because they are capable of UDMA66 (Ultra DMA 4 in Windows). They may still work connected to a 40 wire data cable, but they can't achieve their maximum speeds, and if burning software still allows you to select the max speeds, Windows will detect data errors and force the drive to run in PIO mode.

If you have such a drive and it IS connected to an 80 wire data cable.......

This is the most probable thing wrong when you have yellow ? marks beside any optical drive's model number.

There may be entries in your registry regarding:
upper filters and lower filters
that need to be removed.
I don't know where to refer you to about that, but someone else who answers can probably supply that info.

If you had a 40 wire data cable connected to a drive that requires an 80 wire one, Windows may not set the same model drive's mode to a proper value right away when you connect it to an 80 wire cable - you may need to set that yourself manually.

See this:
http://www.microsoft.com/whdc/devic...

If the connection your optical drive is on is in PIO mode, or in another wrong mode, try setting it to DMA if available, save settings, go back in, see if it has changed to a higher mode. DVD combo burner optical drives should be in Ultra DMA mode 4, if they are capable of 16X or greater DVD + or DVD - .
If the drive won't go out of PIO mode, you need to remove some lines from the Registry, but if you haven't cured what caused the data errors, Windows will immediately or in a short time insert the lines again and it will be in PIO mode again.
...........

"You really should have the DVD drive on the second controller. That will speed up transfers between the two drives. It will run almost twice as fast with the drives on different controllers."

There were some older chipsets that had that problem, but that does NOT apply to ANY mboard chipset's IDE controllers made since about the mid 90's, or earlier!

Other than that, the drives are always accessed one at a time by the cpu. It makes only a very miniscule difference or no difference at all how you connect them!


Report Offensive Follow Up For Removal

Response Number 3
Name: OtheHill
Date: February 6, 2008 at 14:45:04 Pacific
Subject: BIOS sees new DVD but Win XP doesn'
Reply: (edit)
Did you ever install the MBoard chipset drivers? Are you using 80 wire IDE cables? They are the ones with colored MBoard end.

Report Offensive Follow Up For Removal

Response Number 4
Name: beckrl
Date: February 6, 2008 at 15:00:49 Pacific
Subject: BIOS sees new DVD but Win XP doesn'
Reply: (edit)
"I have the jumper on the DVD as slave and HD as master. Though the 1st connection (from IDE 1) is to the HD and the 2nd to the DVD (if that matters)"

If you are connecting an HD and DVD/CD on same ribbion the HD sould be placed on the ribbions end and the DVD/CD on middle.
BUT as aegis has said, DVD/CD on second IDE.
That maybe why it has a (!) for the DVD you have it set as slave but connected to the end(master)


Report Offensive Follow Up For Removal

Response Number 5
Name: OtheHill
Date: February 6, 2008 at 15:13:31 Pacific
Subject: BIOS sees new DVD but Win XP doesn'
Reply: (edit)
beckrl

FYI When using an 80 wire cable on a recent computer it doesn't matter where a drive is connected on the cable when using Master/slave settings. You can connect a drive to the center connector while jumpered as Master. That is the advantage of using Masteer/slave settings.


Report Offensive Follow Up For Removal

Response Number 6
Name: OtheHill
Date: February 6, 2008 at 15:14:39 Pacific
Subject: BIOS sees new DVD but Win XP doesn'
Reply: (edit)
beckrl

FYI When using an 80 wire cable on a recent computer it doesn't matter where a drive is connected on the cable when using Master/slave settings. You can connect a drive to the center connector while jumpered as Master. That is the advantage of using Masteer/slave settings. Conversely, CS settings result in the Master being the drive on the end of the cable.


Report Offensive Follow Up For Removal

Response Number 7
Name: jam
Date: February 6, 2008 at 15:16:40 Pacific
Subject: BIOS sees new DVD but Win XP doesn'
Reply: (edit)
"That maybe why it has a (!) for the DVD you have it set as slave but connected to the end(master)"

The positioning on the cable only matters when Cable Select is being used.


Report Offensive Follow Up For Removal

Response Number 8
Name: OtheHill
Date: February 6, 2008 at 15:20:42 Pacific
Subject: BIOS sees new DVD but Win XP doesn'
Reply: (edit)
jam, great minds think alike.

Report Offensive Follow Up For Removal

Response Number 9
Name: Tubesandwires
Date: February 6, 2008 at 19:43:39 Pacific
Subject: BIOS sees new DVD but Win XP doesn'
Reply: (edit)
"BUT as aegis has said, DVD/CD on second IDE.
That maybe why it has a (!) for the DVD you have it set as slave but connected to the end(master)"

That will not produce any ! or ? in Device Manager for the drive.
Drives jumpered cable select will either work in some situations where they are connected to the wrong connector, or they won't be detected at all.

"FYI When using an 80 wire cable on a recent computer it doesn't matter where a drive is connected on the cable when using Master/slave settings"

....except that the end connector for the mboard - usually blue - the one farthest from the middle connector if there are three connectors on the data cable - must be connected to the mboard.


Report Offensive Follow Up For Removal

Response Number 10
Name: aegis
Date: February 6, 2008 at 20:47:12 Pacific
Subject: BIOS sees new DVD but Win XP doesn'
Reply: (edit)
Putting the hard drive and the CD drive on separate cables 'will' speed up the data transfer between them. That's because data can be read from one drive and written to the other 'at the same time'. DMA makes that possible because the CPU is not involved in the transfer. When they are on the same controller, that cannot be dome because the controller can only do one thing at a time.

Report Offensive Follow Up For Removal

Response Number 11
Name: suatcini
Date: February 6, 2008 at 23:50:30 Pacific
Subject: BIOS sees new DVD but Win XP doesn'
Reply: (edit)
You may have the IDE Channel to which DVD drive is connected set to NONE in Windows.

Or you have some ghost CD drives in Device Manager making Windows hard to identify the new DVD drive. You must uninstall all ghost drives in Device Manager.

Also check that the DVD drive receives enough power when Windows loads due to some power-hungry components.

Hope the above helps.

Regards

SuatCINI


Report Offensive Follow Up For Removal

Response Number 12
Name: Mark%20Denison
Date: February 9, 2008 at 14:30:11 Pacific
Subject: BIOS sees new DVD but Win XP doesn'
Reply: (edit)
First, I want to thank all for their input and helpful efforts. In fact there was so much I want to sift thru it in more detail. I would like to respond and clarify to help my focus and perhaps add useful information to help you help me!

1) I do understand it would be better to put the DVD drive on the separate controller (what I called in my post IDE2). It was originally on that controller but didn't work, so I thought I would try to eliminate that as a interfering factor by putting the DVD drive on the first controller (IDE1) since I knew that was working. Rest assured, once I get this drive working I will explore that option.

2) winXP was a working and (can I say this?!) stable system. All motherboard, chip set, and video drivers were updated/reinstalled. I can't change the mode for the DVD (at least in Windows) because XP says the hardware can't be found and that there isn't anything attached as the slave to the primary controller.

3) re cable. I initially used the cable from my old CD player 40 pin. I then used a new 40 pin cable. I then bought an 80 pin round cable all with the same result "Windows successfully loaded the device driver for this hardware but cannot find the hardware device. (Code 41)"

4) suatcini wrote "You may have the IDE Channel to which DVD drive is connected set to NONE in Windows." If I understand this correctly this would be something in Device Manager under the controller section. Windows says there isn't anything attached as the Slave on the primary channel(IDE1). I do not believe I have any ghost drivers but truthfully, I am not sure I know exactly what that is. Please elaborate.

5) the make and model is correctly identified in the BIOS. I know it works because I did a repair install yesterday using that drive with no luck. When windows starts up it detects the DVD and gives "found new hardware" message and then the message that the drivers were loaded but there is a problem with the hardware. and there is the yellow exclamation

Again, I appreciate the group's response and I hope this was helpful in further diagnosing and fixing this vexing problem.

Mark


Report Offensive Follow Up For Removal

Response Number 13
Name: OtheHill
Date: February 9, 2008 at 16:00:30 Pacific
Subject: BIOS sees new DVD but Win XP doesn'
Reply: (edit)
First of all you need to determine is the BIOS is picking up the drive. You can look in the BIOS screens to verify the drive is configured there. Then watch the screens at startup. The drive must be identified there by model number or Windows will never find it.

If the same conditions you describe in your original post satill exist some possible causes would be: Bad IDE cable, cable turned end for end, connector up side down, bad optical drive. I suggest you verify both of your IDE controllers are enabled in the BIOS and then connect the DVD drive to the secondary channel. I suggest using Master/ slave settings for ALL drives. Then you can connect the Master drive to either connector on the drive end of the cable. This makes it easier to configure the drives.

How are you determining the DVD drive is configured in the BIOS?


Report Offensive Follow Up For Removal

Response Number 14
Name: suatcini
Date: February 9, 2008 at 21:47:06 Pacific
Subject: BIOS sees new DVD but Win XP doesn'
Reply: (edit)
Please open a Command Prompt window and type the following:

set devmgr_show_nonpresent_devices=1

Then you must open Device Manager and first select show hidden devices on the Device Manager View menu before you can see devices that are no longer present in the system.

Now expand DVD/CD-ROM drives. If you have any ghost drive, it must be listed there.

If you see one, uninstall it.

Other than this, I also asked if DVD drive gets enough power when Windows loads. Can you determine that ?

Follow the link below and compare the results with your PSU.

http://www.extreme.outervision.com/...

Regards

suatcini


Report Offensive Follow Up For Removal

Response Number 15
Name: Mark Denison
Date: February 20, 2008 at 09:27:39 Pacific
Subject: BIOS sees new DVD but Win XP doesn'
Reply: (edit)
OtheHill wrote:
"First of all you need to determine is the BIOS is picking up the drive."

The make and model is correctly identified in the BIOS and when the computer boots up.

"I suggest you verify both of your IDE controllers are enabled in the BIOS"

They are.

"and then connect the DVD drive to the secondary channel."

It was originally on that controller but didn't work, so I thought I would try to eliminate that as a interfering factor by putting the DVD drive on the first controller (IDE1) since I knew that was working.

Also checked for ghost drives per suatcini and found none. Power supply seems adequate (per same post) 239 watts needed vs 300 actual.

The DVD drive did work correctly when I booted from the WXP disc and did a repair install.

Thanks again for the help and sorry I took so long to respond.
Mark


Report Offensive Follow Up For Removal

Response Number 16
Name: Mark Denison
Date: February 20, 2008 at 11:52:53 Pacific
Subject: BIOS sees new DVD but Win XP doesn'
Reply: (edit)
I just got the "cure" from another forum. The fix is listed below. Thanks for everyone's help in getting this old clunker up and running!

Mark

"If it's what I think it is, this fix should work:

Go to Start Menu > Run and type regedit

Navigate to the following key:
Code:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318}]

Right click it and choose Export - select a destination for the backup where you can find it again. You probably won't need it.

Highlight the following entries and delete them:
Upperfilters
Lowerfilters

Delete the device from Device Manager.

Restart your PC."


Report Offensive Follow Up For Removal

Response Number 17
Name: OtheHill
Date: February 20, 2008 at 14:01:45 Pacific
Subject: BIOS sees new DVD but Win XP doesn'
Reply: (edit)
Deleting all upper ande lower filter can create complications. There are multiple filters in each catagory. Look at the links below.

http://www.mcse.ms/message1428182.html

http://www.cdr-zone.com/forum/post-...

Google Deleting Upper & Lower Filters for more hits on this topic. The filters are there for a reason.


Report Offensive Follow Up For Removal

Response Number 18
Name: Mark Denison
Date: February 20, 2008 at 23:01:21 Pacific
Subject: BIOS sees new DVD but Win XP doesn'
Reply: (edit)
OtheHill,

Thanks for the followup info. I read the links you suggested and further perused a Microsoft support response on a similar problem and recognising a DVD drive. I agree that editing the registry is a bit risky. So far so good! I will let you know if things unravel.

Mark


Report Offensive Follow Up For Removal



Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: BIOS sees new DVD but Win XP doesn'

Comments:

 
  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 


Data Recovery Software



Version Tracker Pro
Keep your software current and secure, effortlessly

Click Here for a Free Scan

Driver Agent
Automatically find the latest drivers for your computer.
Click Here for a Free Scan



The information on Computing.Net is the opinions of its users. Such opinions may not be accurate and they are to be used at your own risk. Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE

All content ©1996-2007 Computing.Net, LLC