Search options (Page 134 of 213)

The OP had an excellent question i felt we should share with our audience.

The simple answer is because we have 7 unique drivers that are all named nvrd32
Because Nvidia has no clue how to create drivers correctly.
None of their versions can coexist in the \I386 folder together since they all have the same name
(Duh, new driver - new file names - get a clue guys)

The "tag" name is what base renames them to so they can coexist for text mode
(since no tag name should ever be duplicated in the INI)

It is WAY more complicated than above... But that is a good enough answer for now.

The finisher is the main difference...

It is quite inspireing to think that our project may actualy make PnP a more effective and stable vehicle.

maybe we will all get jobs at the WHQL   
i suppose the vendors wouldn't like haveing a new sheriff in town

Sheriff Jaak... has a nice ring to it...
but i think constable Smartepants is a bit much

Ok

1 not useing DriverPacks correctly you need to select mass textmode min for each platform.

2 \i386\asms folder contains some machine specific exceptions that havent been used in years. they are unneeded and removed by most of us as useless files. since they are not modified by us this question really has no place here at all (its not even remotely related to DriverPacks)

So the unneeded files that are not modified by us - what heppend to them - who knows, more importantly who cares...

I am going to say the files got corrupted... start with a clean source and try again...

best of luck ... but when you ask questions that are totaly unrealated to DriverPacks don't be surprized if no one answers you...

(if you cant say anything nice )

I would jsut use nlite to remove that folder altogether

well if we don't it might present issues like this one for bartpe...

Well your HWID's are missing from the mass storage pack - so the error is not on your end...

can you post a link to the driver that you know works for your controller
If so then we will make sure it is supported in the future...

thanks for bringing this to our attention. (we hate missing drivers )

Excellint info thank you...

try this for your INI

[N-7]
ms_count=2
ms_1_deviceName="NVIDIA nForce Serial ATA Controller"
ms_1_tag="nvgts7"
ms_1_sysFile="nvgts.sys"
ms_1_hwids="PCI\VEN_10DE&DEV_0054&CC_0101,PCI\VEN_10DE&DEV_0055&CC_0101,PCI\VEN_10DE&DEV_0266&CC_0101,PCI\VEN_10DE&DEV_0267&CC_0101,PCI\VEN_10DE&DEV_037F&CC_0101,PCI\VEN_10DE&DEV_03F6&CC_0101,PCI\VEN_10DE&DEV_044D&CC_0106,PCI\VEN_10DE&DEV_0554&CC_0106,PCI\VEN_10DE&DEV_0555&CC_0106,PCI\VEN_10DE&DEV_07F4&CC_0106,PCI\VEN_10DE&DEV_0AD5&CC_0106,PCI\VEN_10DE&DEV_0AD4&CC_0106,PCI\VEN_10DE&DEV_0054&CC_0104,PCI\VEN_10DE&DEV_0055&CC_0104,PCI\VEN_10DE&DEV_0266&CC_0104,PCI\VEN_10DE&DEV_0267&CC_0104,PCI\VEN_10DE&DEV_037F&CC_0104,PCI\VEN_10DE&DEV_03F6&CC_0104,PCI\VEN_10DE&DEV_044C&CC_0104,PCI\VEN_10DE&DEV_0558&CC_0104,PCI\VEN_10DE&DEV_07F8&CC_0104,PCI\VEN_10DE&DEV_0AD9&CC_0104,PCI\VEN_10DE&DEV_0AD8&CC_0104"
ms_1_isBusExtender=false
ms_1_exc_disableIfOS="w2k"
ms_2_deviceName="NVIDIA nForce RAID Controller"
ms_2_tag="nvrd327"
ms_2_sysFile="nvrd32.sys"
ms_2_hwids="SCSI\NVIDIA__Raid_Disk________,SCSI\__NVIDIA_______Raid_Disk,SCSI\NVIDIA__Raid_Disk_20_____,SCSI\__NVIDIA____Raid_Disk_20,*_NVRAIDBUS,*NVRAID20"
ms_2_isBusExtender=false
ms_2_exc_disableIfOS="w2k"

yes it will work from cmdlines.txt

but why not just use DriverPacks normaly... ?

i agree ...

take a look at chipset - most of the inf's do not include a copy file

IMEID ... now i am going to have to go look that up... rats...

see the home page and the SAD Disk post in the FAQ

We talked about it before in the other thread...

http://forum.driverpacks.net/viewtopic. … 109#p24109

updated by me