I have a Dell XPS 600 which according to Windows XP has an nForce4 Serial ATA RAID controller (single hard drive) and according to the Unknown Devices app in UBCD4Win has an nForce4 Serial ATA controller (PNPID VEN_10DE&DEV_0055&SUBSYS_01C31028&REV_F4.) I'm using the latest UBCD4Win and all the mass storage Driver Packs, but I can't see the hard drives attached to this controller. What am I doing wrong?
T
Full Version: Dell XPS 600 nForce4 serial ATA controller won't work
I'd probably first suggest that you download the latest MassStorage DriverPack from http://driverpacks.net ...
Place the 7z file in the [UBCD4Win]\plugin\DriverPacks.net\BASE\DriverPacks folder.. remove the older pack.. then rebuild the driver packs from the Plugins area
If you still have issues.. go into the Bios settings and see if they have a option similar to a "Legacy" setting or not and try changing it to that.
FYI on an unrelated issue... on the Dell XPS 600 ... if you are using a 32b OS.. don't even try to have more than 2Gb of memory installed, you won't be able to use it even if the BIOS can see it.. the BIOS won't let the OS use any more than that... 64b OS's are limited to 8Gb.
Place the 7z file in the [UBCD4Win]\plugin\DriverPacks.net\BASE\DriverPacks folder.. remove the older pack.. then rebuild the driver packs from the Plugins area
If you still have issues.. go into the Bios settings and see if they have a option similar to a "Legacy" setting or not and try changing it to that.
FYI on an unrelated issue... on the Dell XPS 600 ... if you are using a 32b OS.. don't even try to have more than 2Gb of memory installed, you won't be able to use it even if the BIOS can see it.. the BIOS won't let the OS use any more than that... 64b OS's are limited to 8Gb.
QUOTE (rdsok @ Jan 19 2008, 02:35 PM) 
I'd probably first suggest that you download the latest MassStorage DriverPack from http://driverpacks.net ...
Place the 7z file in the [UBCD4Win]\plugin\DriverPacks.net\BASE\DriverPacks folder.. remove the older pack.. then rebuild the driver packs from the Plugins area
If you still have issues.. go into the Bios settings and see if they have a option similar to a "Legacy" setting or not and try changing it to that.
Place the 7z file in the [UBCD4Win]\plugin\DriverPacks.net\BASE\DriverPacks folder.. remove the older pack.. then rebuild the driver packs from the Plugins area
If you still have issues.. go into the Bios settings and see if they have a option similar to a "Legacy" setting or not and try changing it to that.
I installed the latest MassStorage Driver Pack, but there was no change, and there is no option to set the SATA drive to legacy (there is just Off, On, and RAID On - it is currently set to On.)
How can I tell if the MassStorage Driver Pack installed successfully?
Is there a driver specific to NForce4 SATA that is non-driverpack?
T
Do you use Norton Go Back or similar applications?
This prohibit PE hard disk mounting.
Does you hardware use compatible ID
PCI\VEN_10DE&DEV_0055&CC_0101,
PCI\VEN_10DE&DEV_0055&CC_0104 or
PCI\VEN_10DE&DEV_0055&CC_0106 ?
Dell and Nvidia offers NForce4 SATA drivers.
Read the help file drivers.htm to integrate massstorage drivers.
This prohibit PE hard disk mounting.
Does you hardware use compatible ID
PCI\VEN_10DE&DEV_0055&CC_0101,
PCI\VEN_10DE&DEV_0055&CC_0104 or
PCI\VEN_10DE&DEV_0055&CC_0106 ?
Dell and Nvidia offers NForce4 SATA drivers.
Read the help file drivers.htm to integrate massstorage drivers.
QUOTE (tsherr @ Jan 21 2008, 06:52 AM)
How can I tell if the MassStorage Driver Pack installed successfully?
Is there a driver specific to NForce4 SATA that is non-driverpack?
T
Is there a driver specific to NForce4 SATA that is non-driverpack?
T
After you download and replace the driver pack then you go into the Builder-> Plugins ... highlight the one that is obviously labed... "# DriverPacks.net - BASE - Press <CONFIG> to enable or reset DriverPacks plugins" and as it states, press the Config button which then will cause it to rebuild the drivers which you can watch the progress of.
There are generic nForce4 specific drivers... but that doesn't mean that Dell didn't customize the ones they require and you would then need to use their customized versions... cdob's question about the HWID's would help answer that to some extent.
QUOTE (cdob @ Jan 21 2008, 04:25 PM)
Do you use Norton Go Back or similar applications?
This prohibit PE hard disk mounting.
Does you hardware use compatible ID
PCI\VEN_10DE&DEV_0055&CC_0101,
PCI\VEN_10DE&DEV_0055&CC_0104 or
PCI\VEN_10DE&DEV_0055&CC_0106 ?
Dell and Nvidia offers NForce4 SATA drivers.
Read the help file drivers.htm to integrate massstorage drivers.
This prohibit PE hard disk mounting.
Does you hardware use compatible ID
PCI\VEN_10DE&DEV_0055&CC_0101,
PCI\VEN_10DE&DEV_0055&CC_0104 or
PCI\VEN_10DE&DEV_0055&CC_0106 ?
Dell and Nvidia offers NForce4 SATA drivers.
Read the help file drivers.htm to integrate massstorage drivers.
Go Back isn't installed, and I don't see anything else that would block access. I looked through the drivers.htm - can I use both the driverpacks and put a driver in drivers\SCSIAdapter or does one preclude the other?
Here are my HWIDs:
===========
PCI devices
===========
PCI\VEN_104C&DEV_8023&SUBSYS_01C31028&REV_00\4&26EC2DE1&0&5090: IEEE 1394 Controller
PCI\VEN_10DE&DEV_0050&SUBSYS_00000000&REV_A4\3&172E68DD&0&50: PCI to ISA Bridge
PCI\VEN_10DE&DEV_0052&SUBSYS_01C31028&REV_A2\3&172E68DD&0&51: SM Bus Controller
PCI\VEN_10DE&DEV_0053&SUBSYS_CB8410DE&REV_F3\3&172E68DD&0&78: IDE Controller
PCI\VEN_10DE&DEV_0054&SUBSYS_01C31028&REV_F3\3&172E68DD&0&80: RAID Controller
PCI\VEN_10DE&DEV_0055&SUBSYS_01C31028&REV_F4\3&172E68DD&0&88: RAID Controller
PCI\VEN_10DE&DEV_0057&SUBSYS_01C31028&REV_A3\3&172E68DD&0&98: NVIDIA nForce Networking Controller
PCI\VEN_10DE&DEV_005A&SUBSYS_01C31028&REV_A2\3&172E68DD&0&58: Universal Serial Bus (USB) Controller
PCI\VEN_10DE&DEV_005B&SUBSYS_01C31028&REV_A4\3&172E68DD&0&59: Universal Serial Bus (USB) Controller
PCI\VEN_10DE&DEV_005C&SUBSYS_00000000&REV_A2\3&172E68DD&0&90: PCI to PCI Bridge
PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&172E68DD&0&B8: PCI to PCI Bridge
PCI\VEN_10DE&DEV_005E&SUBSYS_00001028&REV_A4\3&172E68DD&0&48: PCI Memory Controller
PCI\VEN_10DE&DEV_006F&SUBSYS_00000000&REV_A1\3&172E68DD&0&03: PCI Memory
PCI\VEN_10DE&DEV_0071&SUBSYS_00000000&REV_A3\3&172E68DD&0&00: PCI HOST Bridge
PCI\VEN_10DE&DEV_0075&SUBSYS_00000000&REV_A1\3&172E68DD&0&02: PCI Memory
PCI\VEN_10DE&DEV_0076&SUBSYS_00000000&REV_A1\3&172E68DD&0&08: PCI Memory
PCI\VEN_10DE&DEV_0078&SUBSYS_00000000&REV_A1\3&172E68DD&0&09: PCI Memory
PCI\VEN_10DE&DEV_0079&SUBSYS_00000000&REV_A1\3&172E68DD&0&0A: PCI Memory
PCI\VEN_10DE&DEV_007A&SUBSYS_00000000&REV_A1\3&172E68DD&0&0B: PCI Memory
PCI\VEN_10DE&DEV_007B&SUBSYS_00000000&REV_A1\3&172E68DD&0&0C: PCI Memory
PCI\VEN_10DE&DEV_007C&SUBSYS_00000000&REV_A1\3&172E68DD&0&0D: PCI Memory
PCI\VEN_10DE&DEV_007D&SUBSYS_00000000&REV_A1\3&172E68DD&0&0E: PCI Memory
PCI\VEN_10DE&DEV_007E&SUBSYS_00000000&REV_A2\3&172E68DD&0&10: PCI to PCI Bridge
PCI\VEN_10DE&DEV_007E&SUBSYS_00000000&REV_A2\3&172E68DD&0&20: PCI to PCI Bridge
PCI\VEN_10DE&DEV_007F&SUBSYS_00000000&REV_A1\3&172E68DD&0&01: PCI Memory
PCI\VEN_10DE&DEV_00B4&SUBSYS_00000000&REV_A1\3&172E68DD&0&04: PCI Memory
PCI\VEN_10DE&DEV_00C1&SUBSYS_024510DE&REV_A2\4&1D0C1215&0&0010: Video Controller (VGA Compatible)
PCI\VEN_1102&DEV_0005&SUBSYS_10031102&REV_00\4&26EC2DE1&0&2090: Multimedia Audio Controller
PCI\VEN_14F1&DEV_2F20&SUBSYS_200F14F1&REV_00\4&26EC2DE1&0&1890: PCI Simple Communications Controller
29 matching device(s) found.
===========
USB devices
===========
USB\ROOT_HUB\4&20614AED&0
USB\ROOT_HUB20\4&25764ABC&0
2 matching device(s) found.
I also tried using a driver floppy and hitting F6 during the UBCD4Win boot process (not sure if that is supposed to work) it said it loaded the drivers, but the drive still isn't accessable.
T
Here's an odd thing. I thought I try the Hardware Plugin Builder, but it says there are no drivers loaded for any of the NForce SATA controllers. However, it is clear from the Device Manager that the hard drive is connected to the NForce 4 SATA controller. Grrr.
T
T
QUOTE (tsherr @ Jan 23 2008, 02:51 PM)
However, it is clear from the Device Manager that the hard drive is connected to the NForce 4 SATA controller. Grrr.
T
T
Is that the Device Manager while booted in UBCD4Win? If so...
While in UBCD4win... right click on the "My Computer" icon and select Disk Management... is the drive ( s )also listed there?
QUOTE (rdsok @ Jan 23 2008, 05:04 PM)
QUOTE (tsherr @ Jan 23 2008, 02:51 PM)
However, it is clear from the Device Manager that the hard drive is connected to the NForce 4 SATA controller. Grrr.
T
T
Is that the Device Manager while booted in UBCD4Win? If so...
While in UBCD4win... right click on the "My Computer" icon and select Disk Management... is the drive ( s )also listed there?
No, sorry, in Device Manager in the Windows install on the drive. In UBCD4WIn, diskpart doesn't detect any drives.
T
QUOTE (cdob @ Jan 21 2008, 04:25 PM)
Dell and Nvidia offers NForce4 SATA drivers.
Read the help file drivers.htm to integrate massstorage drivers.
Read the help file drivers.htm to integrate massstorage drivers.
Ok, I tried this but no soap. Is this because I need to remove the driverpacks mass storage drivers?
T
QUOTE (tsherr @ Jan 23 2008, 03:40 PM)
QUOTE (cdob @ Jan 21 2008, 04:25 PM)
Dell and Nvidia offers NForce4 SATA drivers.
Read the help file drivers.htm to integrate massstorage drivers.
Read the help file drivers.htm to integrate massstorage drivers.
Ok, I tried this but no soap. Is this because I need to remove the driverpacks mass storage drivers?
T
Very possibly... there are likely the same filenames in the MS driverpack and then they would have overwritten the drivers you supplied
QUOTE (rdsok @ Jan 23 2008, 05:50 PM)
Very possibly... there are likely the same filenames in the MS driverpack and then they would have overwritten the drivers you supplied
So do I just disable the Mass Storage plugin and rebuild?
T
There are already nForce4 drivers in driverpacks.
Don't add own driver nForce4 to driverpacks. Yes disable driverpacks.
Again which compatible HarwarId do you use?
CC_0101, CC_0104 or CC_0106 indicates a class.
Run regular windows, launch device manager.
Which compatible HardwareId and driver is assigned to SATA controller?
Don't add own driver nForce4 to driverpacks. Yes disable driverpacks.
Again which compatible HarwarId do you use?
CC_0101, CC_0104 or CC_0106 indicates a class.
Run regular windows, launch device manager.
Which compatible HardwareId and driver is assigned to SATA controller?
QUOTE (cdob @ Jan 23 2008, 06:11 PM)
There are already nForce4 drivers in driverpacks.
Don't add own driver nForce4 to driverpacks. Yes disable driverpacks.
Again which compatible HarwarId do you use?
CC_0101, CC_0104 or CC_0106 indicates a class.
Run regular windows, launch device manager.
Which compatible HardwareId and driver is assigned to SATA controller?
Don't add own driver nForce4 to driverpacks. Yes disable driverpacks.
Again which compatible HarwarId do you use?
CC_0101, CC_0104 or CC_0106 indicates a class.
Run regular windows, launch device manager.
Which compatible HardwareId and driver is assigned to SATA controller?
It uses VEN_DE&DEV_0054&CC_0104.
The drivers are nvatabus.sys, idecoi.dll, idecoins.dll, and nvcoi.dll.
T
Rather strange, Nvidia file nvrd325.inf concat PCI\VEN_10DE&DEV_0054&CC_0104 to nvgts5.sys.
So does Massstorage drivers.
Reenable driverpacks. Don't include own dirves.
But include one \plugin\drivers\fix_xps600.inf
So does Massstorage drivers.
Reenable driverpacks. Don't include own dirves.
But include one \plugin\drivers\fix_xps600.inf
CODE
; PE Builder v3 plug-in INF file
[Version]
Signature= "$Windows NT$"
[PEBuilder]
Name="driver: Dell XPS 600 NF4 addon"
Enable=1
[SetValue]
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_10DE&DEV_0054&SUBSYS_01C31028", """nvatabus"""
[Version]
Signature= "$Windows NT$"
[PEBuilder]
Name="driver: Dell XPS 600 NF4 addon"
Enable=1
[SetValue]
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_10DE&DEV_0054&SUBSYS_01C31028", """nvatabus"""
QUOTE (cdob @ Jan 23 2008, 06:47 PM)
Rather strange, Nvidia file nvrd325.inf concat PCI\VEN_10DE&DEV_0054&CC_0104 to nvgts5.sys.
So does Massstorage drivers.
Reenable driverpacks. Don't include own dirves.
But include one \plugin\drivers\fix_xps600.inf[code]; PE Builder v3 plug-in INF file
So does Massstorage drivers.
Reenable driverpacks. Don't include own dirves.
But include one \plugin\drivers\fix_xps600.inf[code]; PE Builder v3 plug-in INF file
Ok, thanks. Before I got your message, I tried with my own drivers and no driverpacks and the drive is recognized. I'll try this solution tomorrow.
T
QUOTE (tsherr @ Jan 23 2008, 08:23 PM)
QUOTE (cdob @ Jan 23 2008, 06:47 PM)
Rather strange, Nvidia file nvrd325.inf concat PCI\VEN_10DE&DEV_0054&CC_0104 to nvgts5.sys.
So does Massstorage drivers.
Reenable driverpacks. Don't include own dirves.
But include one \plugin\drivers\fix_xps600.inf[code]; PE Builder v3 plug-in INF file
So does Massstorage drivers.
Reenable driverpacks. Don't include own dirves.
But include one \plugin\drivers\fix_xps600.inf[code]; PE Builder v3 plug-in INF file
Ok, thanks. Before I got your message, I tried with my own drivers and no driverpacks and the drive is recognized. I'll try this solution tomorrow.
T
Your solution worked perfectly! Thanks for all your help.
T
Thanks for your patience and report. Information will be useful in future.
Unfortunately I've no idea for a general solution.
Some manufacturer release confusing driver versions.
A full working nForce series driver pack is difficult or not possible at all.
Additional information:
PNP use ranking.
PCI\VEN_*&DEV_*&SUBSYS_* get a higher priority than PCI\VEN_*&DEV_*&CC_*
Keep this PCI\VEN_*&DEV_*&SUBSYS_* solution.
You may need this in future or not.
Unfortunately I've no idea for a general solution.
Some manufacturer release confusing driver versions.
A full working nForce series driver pack is difficult or not possible at all.
Additional information:
PNP use ranking.
PCI\VEN_*&DEV_*&SUBSYS_* get a higher priority than PCI\VEN_*&DEV_*&CC_*
Keep this PCI\VEN_*&DEV_*&SUBSYS_* solution.
You may need this in future or not.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.