I haven't had a need for my XP PE disc in many years but came across a system where it might help and was happy to see you guys have still been updating the driver packs. I haven't updated mine since 2015 so I figured before I move forward with a repair, I'd inject your latest packs.

However I have an issue and also a question:

1) My DriverPacks BASE 10.06 is showing "where did you go" beside Chipset, even though I have it in the 'BASE\DriverPacks' folder while the rest of the items are showing what I believe is an older version 12.09. I have placed "DP_MassStorage_wnt5_x86-32_180421.7z" in 'BASE\3rd party DriverPacks' along with "DP_LAN_wnt5_x86-32_180421.7z" which is showing 12.05.

Can anyone advise as to how I can get it to pick up the newer versions? Sorry guys, it's been three years!

2) Is the VMware SCSI driver in there? I was able to add it to a base XP PE disc back in the day but since converting to your driver packs I'm not sure if it's in there. https://kb.vmware.com/s/article/1005208

Thanks in advance!

Just wanted to say your efforts are appreciated, you can count on at least one person who's actively utilizing your updates for PE discs I use to scan friends / relatives PC's for malicious files. There's very few systems your driver pack updates won't support!

TechDud wrote:

Has anybody tested DP-integrated AHCI installation on intel 8-series, Asmedia, or Highpoint?
  Looking for any commentary upon intel eSATA devices too, please.
    Any comments are appreciated.

Whatever the latest nightly was as of February 22, 2014, it blue screens native AHCI with Intel Q87 chipset.
I can test this for you if you like.

I did not blue screen if I chose IDE native mode... but it also didn't see the drive.

TechDud wrote:

@urbanriot - Please post your DPs_BASE log.
Does a simple install of NT5 work?
What is the bluescreen error specifically?

A simple install of NT5 works fine with the two IDE modes but gives the standard non-supported controller blue screen (7B?), the same blue screen you get when using the newer DriverPacks. If I flip the system to AHCI mode and boot up an older PE disc with the older DP from February of 2013 then use the "fix_hdc" script it will insert the AHCI drivers into that Windows installation and work just fine.

Unfortunately I don't have access to this system to provide further insight into the particulars of this issue and I don't know which DP I used in February 2013 disc but it was probably whatever stable was around at that time. I didn't start using the DP nightlies until recently.

TechDud wrote:

Here are a couple of test packs for you.  ICH8 & ICH10D/DO should be fixed now.

TechDud, I appreciate your efforts. I have not yet had an ICH10 based system to test since you posted and I look forward to evaluating it.

However the aforementioned DG35EC still blue screened with the latest iterations of Driverpacks with the standard controller blue screen.

The BIOS has three settings:
Legacy - IDE
Native - IDE
Native - AHCI

The blue screen occurs regardless of which of those options you choose.

If we use a Driverpacks from February of 2013 it will work fine in any of those modes.

Unfortunately I no longer have the system here to test further but I figured I'd report back in the event this information helps anyone else.

Sorry for the late response, it's been extremely busy with work. This system may actually be more of an anomaly as none of our OPK deployment sets are supporting the AHCI mode and furthermore, I can't find any DEVID references to it in any of the Storage Matrix txtmode.oem files.

A Windows PE disc using a driverpacks from some time around February of 2012 supports AHCI mode of this board while the newer driverpacks will blue screen.

Using an app on my Windows PE disc titled Unknown Devices I have the following information:

Intel Corporation  82801HR/HO/HH (ICH8R/DO/DH) SATA AHCI Controller

I just wanted to throw out there that DP_MassStorage_wnt5_x86-32_1308271.7z leads to blue screening on most Intel onboard storage controllers. I thought this was just an issue with the newer controllers but I recently encountered difficulty booting an ICH8 based board (DG35EC) in both AHCI and IDE emulated mode. I reverting from a DP_MassStorage from some time at the beginning of 2013 allowed me to boot.

Considering the compatibility issues that were introduced at some point, perhaps it might be more beneficial to everyone if DP reverted to an older Intel driver?

Cdob, if no one has told you lately, you're awesome. System is now working, life is good, woohoooo!!

Sorry I've taken so long to reply to everyone's post, but it's been a busy week. I realize a number of you tried to help me, but I'm having a slight bit of difficulty understanding what some people have suggested.

cdob wrote:
urbanriot wrote:

The RAID array was built on a completely different board with a different onboard 'controller'

Which different onboard 'controller' did you use?

Unsure of the exact model, sorry, I'm not the one who originally did this. It was obviously nvidia, otherwise I wouldn't be able to read the RAID array from a Windows 7 disc.

cdob wrote:

Did you used nvraid.sys or nvgts.sys at different onboard 'controller'?
Does nvgts.sys read a RAID created by nvraid.sys?

I'm not entirely sure if I can answer that?

cdob wrote:
urbanriot wrote:

I need to change the controller information.

Nice a volunteer. I prepared a fix_hdc update years ago, supporting nvgts.
Never tested because of missing hardware.
You have to boot a PE first.

I would be very interested in trying your update! (But as you said, other problem to solve first).  How do obtain it?  I was going to attempt the one in UBCD.

cdob wrote:
urbanriot wrote:

I'd F6 with USB floppy drive

You may use F6 with USB floppy at UBCD4Win.
Create a new UBCD4Win: don't add mass storage drivers. Boot and load F6 drivers.

Well, after all these years of using PE discs, I'd completely forgotten that you could F6! So, excited, I loaded up my floppy with the appropriate drivers and... "The file nvrd32.sys could not be found". I tried both drivers on Asus site and drivers on their disc (different versions), even the 'make floppy' tool they include. Argh!

cdob wrote:

You may have to adjust old plugin to current used file name.

I'll try to reinterpret your suggestions tomorrow, after I've had more sleep and report back afterwards. I'm working on a week with little sleep, and I'm not entirely sure I understand, but I'm hopeful I'll figure it out.  Thank you!

Debugger wrote:

urbanriot, can you try to run setPnpInterfaceNvgts.cmd from that post: http://forum.driverpacks.net/viewtopic. … 325#p30325 in i386 directory after slipstreaming?

I'm kind of mucking about with PE discs more than I'm needing to do any kind of slipstreaming... in fact, I don't need to slipstream at all, I'd F6 with USB floppy drive. I'd just like to get this going on a disc so I can convert the Windows controller driver on the array... I'm close to giving up, as I can simply access with a Windows Vista / 7 PE disc and copy the data that way, but I'd like to get my trusty old XP PE discs working here and make Windows boot... but I need PE accessing it first.

Is there any way to 'integrate' that command into my PE disc?  Or is there another storage controller driver pack I should try outside of the two suggested above?

mr_smartepants wrote:

Maybe the clue is in how the RAID was created.  How did you build the array?  What software?  Was the RAID built on THAT board, or a different controller (yes, I read the original post)?

The array was created within the nvidia 'controller' RAID configuration pre-boot, not with Windows software.  The RAID array was built on a completely different board with a different onboard 'controller', which is why the system will not boot into Windows. I need to change the controller information.

mr_smartepants wrote:

Typically RAID arrays only work properly on the exact controller they were created on.

This array is healthy and fine, as it's perfectly accessible from a Windows 7 boot disc with no additional drivers. I deleted a pile of temp, temporary internet files and messed around a bit, then chkdsk'd and file system reports healthy.

mr_smartepants wrote:

Could you also try test pack #16 (from newer 15.45)?

I tried test pack #16, from the above link (if that's what you were referring to), and it does not detect the drive.

Pack #13 from above seems to detect drives that are NOT in a RAID array.

a) Your suggestion to create the folder manually allowed me to create the disc.

b) Unfortunately, #13 does not work. It now detects that there's a volume, different behaviour from before; unfortunately the volume is reporting as being unreadable and corrupted and no imaging software will read it. This volume is perfectly healthy so the driver's not functioning quite right...

Any other ideas? (I appreciate your help, it feels like I'm moving towards some kind of solution)

I was excited to see your suggestion; unfortunately when processing MassStorage.inf, it's producing a "Error: Cannot find folder: wxp" message. I found a stickied thread regarding this issue so I wiped out my PE, just in case I missed a file or folder, started with a fresh one, as well as a fresh dpbase folder and it's a no go.  I fought with this for about an hour before I posted... but I'm probably missing something simple.

Asus M2N68 PLUS motherboard with nForce 430 / MCP61 controller. Two drives configured in a RAID0 array from another nForce based board but the Windows won't boot until I change the controller drivers, and I'd like to access it without having to temporarily plug in a hard drive to install Windows on, just to access this data.

I'd manually tried using Asus Nvidia RAID drivers from their web page, and a newer version on the CD they provided (yea, weird, newer version on the disc), no luck. I then figured I'd give this driverpacks.net a try, and that's also not working. If I "Disable RAID Mode" the drive can be read in WinPE (I assume that puts it in IDE mode, not AHCI, hard to say as Asus BIOS option not very explanatory).


If anyone has any suggestions, they would be much appreciated.