26

(8 replies, posted in DriverPack Chipset)

Got them.

http://ftp.us.dell.com/chipset/R218459.exe

27

(8 replies, posted in DriverPack Chipset)

Ok I have found the HECI 10/20/2008,5.0.1.1127, I just need the SOL 11/21/2008,5.5.0.1136

28

(8 replies, posted in DriverPack Chipset)

Chud could you please provide the download links ? Intel is too retarded to put them on their website.

Well the link to download the RAID version of the driver is not working.

http://www.support-highpoint-tech.com/M … 090423.zip

I downloaded the non-raid driver, I will add them asap.

PCI\VEN_8086&DEV_2652&CC_0106 and PCI\VEN_8086&DEV_2652&CC_010601 are already supported by the driver located in the I2 folder.

This a tricky one.

The working driver is the one located in the L8 folder. Unfortunately this driver is not signed. Only Dell made one signed but they dropped LSI Hwids (including the esx one). I will update the pack with the latest signed driver from Dell and I will create a second INF that supports the missing HWIDs. Hopefully it will work.

You don't need to call MS for patches anymore just look at the top of the page you can get all patches for free by email.

Try this pack too http://driverpacks.sytes.net/driverpack … 2_903r1.7z

Without real data to work it, No one can help you pal. Please be specific.

Sure, 1st learn how to read then google it.

There is no signed LSI driver on LSI website to replace the existing one in the L8 folder. It's important to have a signed driver when there is conflicting hwids, for XP there is not so it should be fine.

Have you tried the latest base http://driverpacks.sytes.net/driverpack … _90201.exe ?

Setup files can be extracted. Use universal extractor or 7-zip.

Nope KickArse, I have no skill in coding. Just some scripting big_smile

39

(14 replies, posted in DriverPack Mass Storage)

JakeLD agrees with ChiefZeke.

You could also try to integrate that plugin into your PE

Driver.inf

[Version]
Signature="$Windows NT$"

[PEBuilder]
Name="Driver: IBM 6M"
Enable=1

[SetupReg.AddReg]
0x4, "CurrentControlSet\Services\nfrd960\Parameters", "PnpInterface", 0x5
0x4, "CurrentControlSet\Services\FastSx\Parameters", "PnpInterface", 0x5
ef wrote:

JakeLD,
this is the link for the Promise FastTrak S150 SX4 Windows drivers:

http://www.promise.com/support/download … &go=GO

If possible, please include them and the previously posted Ibm ServerRaid 6m Windows drivers into a new MassStorage DriverPack.
Thank you.

Edoardo

This driver is already included, a simple search would have gave you the answer.

Also please make sure that your BIOS and firmware controller are updated.

IBM 6M use  Firmware level 7.10 for the ServeRAID-7k, ServeRAID-6M,
ServeRAID-6i/6i+, and ServeRAID-5i Ultra320 SCSI Controllers


PCI\VEN_1000&DEV_0030 for XP use the driver in L8 folder which is not signed. That might be the problem. I will replace this one with a signed one asap.

Also try with XP Sp3 or 2003 SP2 as source. I don't understand why you are using an old service pack anyway. Don't you have enough problems already ?

I also noticed PCI\VEN_1106&DEV_0571 which is a via controller, that specific controller is supported by XP SP3 and not by SP2. That's why we are using the switch replace in the INI file. So using XP SP3 as source sounds like a good idea.

42

(14 replies, posted in DriverPack Mass Storage)

I might be wrong but I don't think PCI\VEN_8086&DEV_2820  and PCI\VEN_8086&DEV_2825 support AHCI at all.

http://www.intel.com/Assets/PDF/specupdate/313057.pdf

Look at page 12, Non-AHCI and Non-RAID.

The HWID changes when you switch sata modes, so we need the hwid listing when you are in sata mode. You can achieve this in BartPE or with UBCD4WIN.

I would recommend a bios update. Also when we get the proper HWID for AHCI mode, we could lookup at intel documentation and see if your HWID is supported.

BTW your welcome. big_smile

http://www.jhouseconsulting.com/index.p … -hotfixes/

The Windows StorPort mini driver (storport.sys) is an interesting case, and makes for a good example of this theory. Functions within it are used by most disk subsystem drivers, such as the LSI SAS and QLogic HBA drivers, just to name two. When referring to Windows 2003 SP2, this has been updated in the following hotfixes:

    * KB932755 contains driver version 5.2.3790.4021
    * KB939315 contains driver version 5.2.3790.4121
    * KB940467 contains driver version 5.2.3790.4133
    * KB941276 contains driver version 5.2.3790.4156
    * KB943295 contains driver version 5.2.3790.4163
    * KB943545 contains driver version 5.2.3790.4173

Nope the mass storage pack is intended to be universal; support for IDE, SATA, SCSI and SAS.

You were right about me looking in the wrong section...I need some vacation I guess big_smile

So I was right big_smile Thanks for the detailled infos cdob. I already with Overflow and I'm sure he will take care of it as soon as he has the chance.

KB943545     Error returned by the IOCTL_SCSI_GET_INQUIRY_DATA operation on a Windows Server 2003-based computer: “STATUS_INVALID_DEVICE_REQUEST� . This is an updated Windows StorPort mini driver that addresses issues such as:

    * Disk subsystem performance issues
    * Random blue screens
    * Server stops responding
    * Server doesn’t shutdown properly
    * Network freezes

Diskdump.sys
Storport.sys


Since this a post SP2 patch, it's the most recent version of storport.sys (5.2.3790.4173)

http://support.microsoft.com/kb/943545

Hi,

I have a noticed a bug with version 3.2f with nvidia nforce lan drivers. They don't get all listed. For instance if you run the tool with NV4 folder you only get 1 hwid and there is 29 in reality. Nvidia network hwids are particular since they use a different format: {1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV054D.

Thank you.

From e1k5132.inf included in their last pack version 14.0:


%E10DENC.DeviceDesc%            = E10DE.5.0,       PCI\VEN_8086&DEV_10DE
%E10DFNC.DeviceDesc%            = E10DF.5.0,       PCI\VEN_8086&DEV_10DF

49

(2 replies, posted in DriverPack LAN)

No its part of e100b325.inf.

Perhaps, you could read the whole post again.