If you could then nobody would have ever shown up here,
they simply would toss all their drivers in a zip file themselves.

It's a lot of hard work and testing and modifying and retesting.
most of the posts on this board are in the forums for release and testing of beta packs and they are hidden from public view. it has taken hundreds if not thousands of hours to get them to work they way they do. I am impressed that you gave it a go, so don't sweat it if your attempt was not what you expected. Mr_Smartepants has been doing the packs for years and still has a glitch here and there .

Cheers m8

I've no idea, if a Windows 7 dism works at Vista files or at Windows 2008 (not R2) files.
May work or fail, it's not supported.

Yes it does.  Each newer version of DISM is backwards compatible and IS supported by M$.

My question is whether fix_7hdc can also handle Windows 2008 (not R2)?

Dosn't Windows 2008 (not R2) relate to Vista?
I've no idea, if a Windows 7 dism works at Vista files or at Windows 2008 (not R2) files.
May work or fail, it's not supported.

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.

Hey guys! I've been trying to sort out my motherboard swap from intel to amd with windows 7 and I can confirm that Fix_HDC.cmd does work!! with one modification

simply edit the fix_hdc.cmd file and right down the bottom delete the two lines:

Thank's for report. Yes, it may work by chance at special cases.
However this is not supported. And will fail at other cases.

Instead use Fix_7hdc.vbs to fix a windows 7.

simply edit the fix_hdc.cmd file and right down the bottom delete the two lines:
if not exist %system_root% etc txtsetup.... and the line after it

I used the windows 7 recovery console rather than a PE cd, make sure you have all necessary files, reg.exe, regedit.exe, devcon.exe, expand.exe, findstr.exe
make sure they are all in the same folder, I put them in the system32 folder, then run fix_hdc

worked like a charm

Are options 1 and 2 even possible from an x64 PE 3.

I've no idea. Never tried this.
vbs should work (1), however dism.exe behaviour is unclear (2).

Yes, do this. Write log files too.

1) Boot my current cd
2) Fix HDC drivers for x64 win7  OR x86 Win7 using a batch menu with preset switches for your vbs.

Example Menu:

1) Activate HDC drivers for x86 Win 7 (standard win7 drivers)
2) Inject and activate HDC drivers for x86 Win 7 (Driverpacks.net folder)
3) Activate HDC drivers for x64 Win 7 (standard win7 drivers)
4) Inject and activate HDC drivers for x64 Win 7 (Driverpacks.net folder)

Question:  Are options 1 and 2 even possible from an x64 PE 3.  I assume the vbs polls from the PE3 x64 environment.  Hmmm...  I guess I should do some trial and error.

Main features:
enable existing, but disabled drivers
install new drivers.

Runtime environment:
a PE3, this incluedes a Windows 7 installation DVD.
Default integrated tools like dism.exe are used.
No need to include a addional tool.

This require testing at real hardware.
Dism may install driver from a *.inf file or not.
Compare above [VMware.Mfg] [VMware.Mfg.NTx86] example.

You may use DriverPacks driver.
DP_MassStorage_wnt6-*.7z contain Vista and Windows 7 drivers.
Expand files yourself first.
Use default folders, or select folder at runtime.
default folder:
32 bit running PE use .\x86
64 bit running PE use .\amd64
Be aware, this refer to current running OS, not to offline windows.
If you boot a 32 bit PE and like to fix a 64 bit offline windows, set driver folder at command line.

The last read inf file is used at double HardwareID.
File system is alphabetically sorted at a NTFS partition. Use a NTFS partition.
This should prefer Windows 7 drivers.

@real1elmo
Do you boot a 32 bit PE 3 or a 64 bit PE?
Should I change default driver folder behaviour?

Good luck

General rule: broken input result broken output.

Thanks cdob.  Yes, you gotta love GIGO.
DISM will only add drivers to an OFFLINE image.  You can't use DISM to add drivers to an ONLINE or running system.  DPInst or PNPutil is used for online images.

Scenerio 3 HPxw8400 to HPz800

I booted a Z800:
native supported by Windows 7 64 bit
device: LSI SAS 3000 8 port
HardwareID PCI\VEN_1000&DEV_0058&CC_0100
driver: LSI_SAS.SYS

Do you boot from SAS hard disk?
Driver lsi_sas.sys is installed but disabled.
Open registry, and set service lsi_sas to boot start=0.

However machine is in usage already: hence no testing, reading only.
I'll get deep trouble if I break the machine.

To explore strange new worlds (TM):
Given a 32 bit Windows 7.
Existing disk swapped to a vmscsi hard disk.
Booting result to a BSOD 0x7B.

Add XP driver vmscsi:

dism /image:e:\ /add-driver /driver:F:\x86\scsi\vmscsi.inf /ForceUnsigned

However no driver added to Windows 7. And no registry setting is added.

vmscsi.inf adjusted and integrated

Dism does install driver vmscsi now.
Files are copied to inf, system32\drivers and system32\DriverStore.
Registry is adjusted.

Windows 7 does boot with a XP vmscsi.sys now.

Conclusion:
Dism message "The operation completed successfully." refers to dism rules.
Message is missleading: a driver may be installed, or not installed.
A driver if installed, if a driver exist matching image.
If a driver is missing according to dism rules, no driver is added.

No, I won't support adding XP drivers to windows 7. That's at own risk.
General rule: broken input result broken output.