Search options (Page 52 of 159)

I'm finalizing the code and tweaking some of the display screens.  Works great!  Added changelog to the code for reference.
I'll upload once completed.

Well, how you described your problem (txtmode works, BSOD after GUI first reboot) indicates that the problem is NOT with the .ini.  The .ini only tells Windows setup how to find the drives during the initial setup (blue screen, white text, where you select the drive to format/install).  Once setup continues into the GUI, the drivers are selected from the %systemdrive%\D\ folder.

Did you also edit the D\M\I8\*.inf file to delete the HWID?

Marking as "solved" due to lack of participation from original poster.

This should be fixed in v11.04 final

post your DPs_BASE.log please

DP_MassStorage_wnt5_x86-32_1104r3
link removed

No like newsposter said, you need both.
Chipset is THE most important of the DriverPacks.  dpms allows for the drives to be "seen" during txtmode.  The pair work together.

v11.04r3
Fixed
- I3\ Moved PCI\VEN_8086&DEV_27C3&CC_0104 .ini entry from I8 to I3.  Reported here: http://forum.driverpacks.net/viewtopic. … 609#p43609

Delete PCI\VEN_8086&DEV_27C3&CC_0104 from the [I8] section in the .ini and replace your .ini section [I3] with the below

[I3]
; 7.8.0.1012
ms_count=1
ms_1_deviceName="Intel ICH8/ICH9/EP 80579 SATA AHCI/RAID"
ms_1_tag="iastor3"
ms_1_sysFile="iastor3.sys"
ms_1_hwids="PCI\VEN_8086&DEV_27C3&CC_0104,PCI\VEN_8086&DEV_2824&CC_0106,PCI\VEN_8086&DEV_2829&CC_0106,PCI\VEN_8086&DEV_2923&CC_0106,PCI\VEN_8086&DEV_5029&CC_0106"
ms_1_isBusExtender=false
ms_1_exc_disableIfOS="w2k"

So you waited for two YEARS to report this bug?  OK, I'll look into it.  Thanks for posting your HWIDs.

Already reported and fixed in another RC build.
DP_MassStorage_wnt5_x86-32_1104r2
link removed

I'll bet you built your .iso with strict 8.3 filenames.  I use relaxed filenames in my own .iso build.
nvatabus2.sys is 9.3
Rename the .ini [n2] section to this:

[N2]
; From nForce 6.39 DriverVer=01/20/2005,5.10.2600.0507
ms_count=2
ms_1_deviceName="NVIDIA nForce 2/3/4"
ms_1_tag="nvatabus"
ms_1_sysFile="nvatabus.sys"
ms_1_hwids="PCI\VEN_10DE&DEV_008E,PCI\VEN_10DE&DEV_0085,PCI\VEN_10DE&DEV_00D5,PCI\VEN_10DE&DEV_00EE,PCI\VEN_10DE&DEV_00E3,PCI\VEN_10DE&DEV_00E5,PCI\VEN_10DE&DEV_0035,PCI\VEN_10DE&DEV_0036,PCI\VEN_10DE&DEV_003E,PCI\VEN_10DE&DEV_0053,PCI\VEN_10DE&DEV_0054,PCI\VEN_10DE&DEV_0055"
ms_1_isBusExtender=false
ms_2_deviceName="NVIDIA nForce RAID Class Controller"
ms_2_tag="nvraid"
ms_2_sysFile="nvraid.sys"
ms_2_hwids="GenNvRaidDisk,*_NVRAIDBUS"
ms_2_isBusExtender=true

Unusual since they're not available here: ftp://driver.jmicron.com.tw/CardReader/Windows/

Moved to "other".
If you look at the Intel chipset "drivers" you'll notice that there are no .sys files (other than USB), so really there are no "drivers".  The signed .inf files only add registry entries so that the system knows what to call all those "unknown device" items in the device manager for the devices in your motherboard.  Just because the chipset package can identify your Mass Storage device, doesn't mean it's operating at peak efficiency.  That's what the RST drivers do.

Having an imbalance of version numbers isn't a problem in itself.