UDMA and Drive Type

[kodiak]

Hello again. When originally built, Device Manager listed both my WD 40's as "western diital + model no./SN + UDMA 100. After one of the originals went bad and I rma'd it, the new replacement was recognized as "generic type 80" in Dev.Man. Last nite, i uninstalled the new drive a couple times and it always came back the same after reboot. So, I removed the SIS 5513 dual pci ide controller from DevMon and rebooted. Now 1 drive is generic type 47 (c drive), the other is generic type 80 (d:, e:, and f: drives). At boot, bios recognizes both as WD+model no./SN and shows them as udma 100 - enabled. More info: 2 antec round udma 100 cables. Drive c: is master on primary channel w creative dvd as secondary (both jumpered accordingly); Secondary channel has ACER CDRW jumpered as master, and second hard drive with 3 partitions jumpered as slave. I have checked the boxes for both to enable them DMA, and the drivers are and always were, all windows plain vanilla, even for SIS 5513 controller, and both drives seem to be fully functional. How do I get Device Man. to list them as WDD 40's.?

[GaryRouth]

Try things jumpered and cabled to Cable Select.

But seems like that shouldn't matter. You could also try booting into Safe Mode and removing the controller and both drives there: then try a run of RegClean 4.1 (on the chance that the Device Manager settings are stored in there somewhere) [http://download.com.com/3000-2094-88...ml?tag=lst-0-1] - then enter Bios Setup on your next reboot, and find the menu with "Enable ESCD" or "Force Update ESCD" (Extended System Configuration Data) - and see if the hardware detect in Windows end goes better.

That's my guess at the moment.
. . . Gary

[kodiak]

Thanks, Gary. Will give it a try and post back.

[kodiak]

Hi Gary. Tried your suggestions to no avail. My BIOS doesn't have any ESCD options, but I went to safe mode and deleted the controller and drives. Also made 2 runs of regclean. Ist reboot got me a Wcmdmgr caused invalid page fault in Kernel 32.dll. Did CTRL-ALT-DEL, and ended "download software from the task manager, then to msconfig and unchecked a couple of no longer installed items, then regclean again (It found nothing to fix). Rebooted clean after that, but Drive c still showing as generic type 47, the other as Generic type 80. C drive is DMA enabled, the other one is not SisoftSandra confirms that. The second drive won't force enable DMA in the drive manager checkbox, either (perhaps because its the IDE secondary channel slave? Perhaps because it's partitioned into 3 drives?) I still have a lot to learn, so if you see this do you have any other ideas? Thanks again!

[GaryRouth]

I'll have to do some homework on this one . . . I should have some time tomorrow to look around. If we're lucky, glc will see this post = he knows most things off the top of his head that I have to check my books for
. . . Gary

[GaryRouth]

OK - I've looked around a bit, which has been interesting, since I've been wondering why some devices list differently in Device Manager, though they list fine in the Bios and in Hardware test programs such as SiSoft Sandra. Here's Western Digital's answer:
_________________________
"Q. How are EIDE drives recognized in Device Manager in Windows 95/98?

A. The Windows 95/98 Device Manager shows the drives installed in the system. In many cases, when you view the drives within Device Manager, they are identified as Type xx. Sometimes the actual model number of the drive is displayed.

The drive model number within the Windows 95/98 Device Manager is usually not shown unless you have some type of third-party driver installed. Keep in mind that the driver referred to here is the driver for the EIDE controller on the motherboard, not the drive itself. The drive does not require drivers. The lack of a model number does not affect the performance of the drive, although a third-party driver can offer improved performance. If you would like to use a third-party driver, check with your motherboard manufacturer for availability. In addition, you may be able to obtain a suitable driver from the motherboard chipset manufacturer (i.e. Intel, Via, etc.). Make sure you understand the driver requirements and verify that your system meets these requirements before installing the driver.
____________________
I'm also not sure if your SiS chipset supports UDMA-100. Some of their chipsets from a few years ago maxed out at UDMA-66. Your motherboard specs should say for sure. If you can't go any higher than UDMA-66, use the Western Digital utility Data LifeGuard's menu selection of Ultra ATA management and change the UDMA/Ultra-ATA setting for both drives to 66. If your board can do 100, but the new drive won't enable DMA, you can try moving both optical drives to the Secondary IDE Controller (SiS recommends this on their website anyway), and have both hard drives on the Primary. Then see if DMA will remain enabled on the new drive. (it should).
_____________
Not sure if this helps much, but it's a start.
. . . Gary

[kodiak]

Thanks a million Gary. I was intuitively thinking along that same line, but was not sure how to move forward or even what steps to take to research it like you did. Wierd! Since Device Manager originally showed the drives as ata 100 (and that setting is supported by the sis735chipset on the mobo, btw), it seems apparent that the after relocating the drives from the primary IDE, to one each on each IDE channel, thats how the first drive became a "generic" in DevMAn. Then, when i removed the SIScontroller and it reinstalled, I must have not directed windows to the mobo/sis-specific driver, which left windows to fend for itself and use its own driver, resulting in the second WD becoming a "generic" too. So, I'll go back to original jumpers and cabling setup, download the sis ide driver, boot to safe mode and remove the controller and the drives, reboot to safe mode and install the sis ide driver, and reboot. Does that course make sense to you?

Oh - you may not recall, but you and crickette saved my bacon when I first came to the board. I ultimately reinstalled everything and started from scratch, but thanks to you all, I was able to save all my data first, and learned a bunch more in the process. Thanks!!

[GaryRouth]

There are whole decades I don't recall

But glad we've been helpful at least some of the time
_________
I'm pretty sure that you'll be OK with the SiS drivers - but if you notice any drop off in performance, it won't hurt anything (other than perhaps losing the drive names in Device Manager) to go back to drivers you can get at Windows Update. They are usually certified, and oddly enough sometimes outperform the SiS drivers [or so I've read]

I'm glad you asked these questions, because I got to finally find out a bit more about Device Manager's way of doing things.

This old dog learned a few new tricks!
. . . Gary