Search options

Ran into an issue with HP Z820 machine. 
I had to manually update the DP_MassStorage_driverpack x64 to include the latest matching iastor drivers from intel. 
Then I tried to use fix_7hdc on my "Windows 2008 SP1" imaged machine.  It looked good, but the bsod occured.
PE3 sees the drives (side note: i also had to remove the SilRem* drivers from the driverpack due to a conflict in PE3.)
So I manually added the driver IASTORF using these steps: http://social.technet.microsoft.com/For … af77484ae7
The machine booted after I did that.  My question is whether fix_7hdc can also handle Windows 2008 (not R2)?
My manual add proves the driver was correct once I updated the driverpack, so what could it be.  I have spent 2 weeks trying to isolate the issue.

Otherwise is there an alternate way to update w2k8 standard using the manual style instead of dism.  The manual method didn't use dism.  It added the driver correctly by dropping the sys, inf, and reg keys.

Yes my pe build did make use of the pnputil.exe   I double checked inside the wim and found it in \BOOT.WIM\1\Windows\System32\ which when booted from cd was in x:\Windows\System32\
On win7 I am strictly doing x64.  I used to be an xp 32bit only guy.  That is all I use.

Scenerio 2: (untested in 7)
Dell 670 (RAID) that was converted to Dell Laptop M90 using FIX_HDC had to be converted back when returned to RAID. (if memory serves)

Scenerio 3 HPxw8400 to HPz800(win pe 3 without driverpacks added or no boot cd needed in this case)
It turns out my make_pe3 build didn't have the x64 driverpacks added.  Yet still had compatible drivers for FIX_HDC since 7 comes with a ton.  At least my wim built on HP OEM x64 image did.  Not sure if my pe would have had so many otherswise.  I will check tomorrow.  Long story shorboth boxes contain a common sata controlller (lsi_sas i think, might have been iastor.. again i will have to check)  Ran 2 seperate tests. 
Test A)
Booted the cd. Ran fix_hdc (it added 2 drivers and reg key)and no more bsod on z800.the tool worked in pe3
Test B)
Put HPxw8400 drive in Z800 and booted to BSOD
Plugged sata cable into common denominator sata controller matching 8400
Booted z800 and let windows slowly add the second sata controller (which it had the driver for already)
Rebooted and plug the sata back into the newly added primary sata controller
new drive could now boot on either HPxw8400 or HPz800. (the othertech figured out both boxes shared a common controller..no cool points for me)

Scenerio 4:
HPz800 Windows 7 image pushed to Dell m6300 Laptop or Dell M90
BSOD occured.
Booted my  make_pe3 cd and ran fix hdc (it said no driver needed and imported fix_hdc.reg)
no more bsod.

I use lsi_sas, iastor, and ide.  In my case those cover a lot of ground.  I would attach my txtsetup, but not sure how to attach.

Quick question how do I get dism to only load the driver that matches pe devcon results.  That way it doesnt just load them all using recurse?

Scenerio 1:
I backup a win7 machine with ghost. The original machine was an HPxw8400 using IASTOR.sys already installed.  I restore the image to an old Dell 670 and try to boot it. BSOD!  I run your tool and FIX_HDC says no driver needed, but still imports the fix_hdc.reg info.  Reboot, and bam no more BSOD.  The reason it needed no driver was because the drive in the 670 was IDE.

Can DISM do that?  I know it adds drivers, but in my scenerio windows had the driver for IDE, but refused to pick it out and use it when the original was built RAID.

If DISM is the way to go can you make a script that adds all the driverpack subfolders for mass storage, and existing ones in winpe just in case.

Hey ricktendo64
The disk is already visible in PE3. Which wasn't an issue.  I am working on a plugin support file used by FIX_HDC when booted into PE3.  FIX_HDC looks at the PE3 driver that is running (visible disks) and injects that registry info and driver to the HDD to make it not BSOD.  The boot cd does not BSOD.