(26 replies, posted in DriverPack Mass Storage)

Case sensitive, that is quite wierd, i mean this is windows not unix wink
Is there no alternative driver available? I know Dell has lots of megaraid drivers, actually i slipstreamed one on w2k3 2 days ago for a Dell poweredge 1950.


(36 replies, posted in DriverPack Mass Storage)


i noticed the following 2 sections:

ms_1_deviceName="Silicon Image 3112 SATARaid Controller for Bios 4.x.79"

ms_1_deviceName="Silicon Image 3112 SATARaid for Bios 4.x.83"

Both section have the same sysfile, i thought that textmode setup can only load .sysfiles that do not have the same name as other .sys files do.
If you want a specific version of Si3112r.sys to be loaded during textmode, you probably have to rename one of the Si3112r.sys filenames to something else.  I Could be wrong here though.


well, there are similarities:

1. Both topics are about the ICH7 hardware.
2. The symptoms are the same, after the first reboot, after gui setup it freezes at the windows logo screen where the blue dots appear.
3. When the intel drivers are removed from the driverpack chipset the problem is no longer present, so the problem has to be in the latest dp chipset.

There are also differences:

1. In AHCI mode there is no problem.
2. The system does not lock up when i enter save mode.
3. The problem only occurs when RAID-AHCI mode is used.

Regrettably the system i tested this on is no longer available,
so i cannot test with DP chipset 6.05.

It could very well be that this topic is the same problem:


I had the exact same problem with an HP XW4400.
When i removed driverpack chipset, the system no longer locks up at first gui startup.
I am going to test tomorrow wether this problem is related to the intel chipset driver or other chipset drivers.


could you try this test version aswell?

@jonedeuf ,

i have uploaded the test version with the proposed PCI\VEN_197B&DEV_2360&SUBSYS_03601849 right here:

http://rapidshare.com/files/13784411/DP … ly.7z.html

Can you guys give it another go?


can you expand the si3132.sy_ and then tell us what version that file is?
Can you also expand the following 7z file in the OEM folder of your slipstreamed CD?


Can you then go to the d/m/s/b folder and tell us what version that si3132.sys is?

Can you also describe in what phase during setup you are prompted for the si3132.sys file?

I downloaded both the sata and the raid driver.
I compared them:

- hwids are the same.
- sys and cat files are different.
- looking at the .inf's the sata driver is newer then raid driver

I think we have 2 options:

1. Change the date in both inf files so that the date is the same in both inf files. Then add them both to DP masstorage. The question is, will both drivers be loaded without conflict?

2. We merge both inf files and also modify txtsetup do that both sys files are loaded during textmode.
Is this possible?

Ok, i am going to fix this by adding the following hardware id's in D\G\N\1\nv4_go.inf to prevent BSOD on Dell laptops with Quadro NVS 110/120M GPU:

%NVIDIA_G72.DEV_01DA.1%  = nv4_WSApps_mobile,        PCI\VEN_10DE&DEV_01D7&SUBSYS_01C21028
%NVIDIA_G72.DEV_01DA.1%  = nv4_WSApps_mobile,        PCI\VEN_10DE&DEV_01D7&SUBSYS_01CC1028
%NVIDIA_G72.DEV_01DB.1%  = nv4_WSApps_mobile,        PCI\VEN_10DE&DEV_01D8&SUBSYS_01CC1028

This fix will become effective in the next dp graphics A release.

Ah yes,

i analysed your problem and i think i now know what is causing the BSOD.
The driverpacks graphics A uses a modified .inf file to be able to support all the nvidia mobile GPU's.
We obtain this modified .inf file from www.laptopvideo2go.com.

When i lookup the hardwareid for your Quadro NVS 110M videocard in the modified .inf file (nv4_go.inf), i can clearly see that the first bit of that hardwareid is associated with a "NVIDIA GeForce Go 7300".
It should have been associated with the "NVIDIA Quadro NVS 110M", so that is why you get a BSOD.

I found these 2 posts that completely confirm my conclusion:

http://www.laptopvideo2go.com/forum/ind … l=NVS+110M

http://www.doitrightconsulting.net/foru … 48a6f7d283

The question that remains is, how can we correct this properly without breaking anything?

Ok, the LSI SAS 1068 driver will be implemented in the next version of DP masstorage.
Only for windows 2003 though, i am unable to find a windows xp version of that driver with the same hardware id's.

Can you tell us the exact model of your motherboard and specifiy where we can downloadn the jmicron drivers for your motherboard?
I would like to analyse your drivers, maybe we can add even more hardware id's.


Could you please post your hardware id's?
Also, why do you have to update your nforce drivers? What problems are you experiencing if you do not update your nforce drivers?
Can you tell us where we can download those specific nforce drivers?

Bâshrat the Sneaky wrote:

Well, Promise has been working surprisingly well for a very long time (many, many months), but perhaps it's now time to rethink the whole current implementation.

Do you already have a suggestion on how we can add this driver without causing a conflict?

I have implemented both the windows xp aswell as the w2k3 version of this SAS driver. It already is in the latest driverpack masstorage (7.01.1).

The windows xp version of the Dell 5IR SAS driver is not "lsi_sas.sys" but it is "symmpi.sys".
The driver "symmpi.sys" is already being used in windows xp by "LSI Adapter, FC 4000 series, Dual or Quad port (with 929)".
I could ofcourse give it another ms_1_tag name, but still, during textmode 2 symmpi.sys drivers will then be loaded. Will this not confict?


do you start your unattended installation from dos (with winnt.exe)?


I tested the new dp Base 7.01.4 in combination with DP masstorage 7.01 and the new nightly of DP masstorage. I cannot reproduce this error.
What version of the Driverpack masstorage where you using?

There was a large topic about your WinXP Promise SATA378 (tm) IDE Controller.

If i understand correctly the SATA version of your controller driver was deliberatly left out of the driverpacks because it would conflict with the RAID version of your controller driver (WinXP Promise FastTrak 378 (tm) Controller).

What i can see is they both share the same hardwareid's.

This is the topic if am referring to:
http://www.msfn.org/board/lofiversion/i … 37535.html

Could you please post your hardware id's? Then we can analyse this problem.

We are aware of the problem and we are trying to solve this asap.


That sounds awesome, would love to know the outcome of that.

A solution for this problem is on the way.

XP driver seems not be an option, since it will confict with an existing .sys file from a driver called "LSI Adapter, FC 4000 series, Dual or Quad port (with 929)".
We could create a workaround for that, there is however not much point in doing so since this Controller is meant to be used on servers.
I therefore added the Windows 2003 version of this driver.