OverFlow wrote:

There is no I5 folder in mass 805???

You're right. I copied and pasted from an earlier post that was showing the nightly build. I guess my point was to show the identical hardware IDs for two different drivers. Sorry for the confusion.

Overflow,

I like your way better also, but my specific problem is:
PCI\VEN_8086&DEV_27C0=C:\D\M\I5\ich7id2.inf
  PCI\VEN_8086&DEV_27C0=C:\D\M\I5\ich7ide.inf
  PCI\VEN_8086&DEV_27C4=C:\D\M\I5\ich7id2.inf
  PCI\VEN_8086&DEV_27C4=C:\D\M\I5\ich7ide.inf
  PCI\VEN_8086&DEV_27DF=C:\D\M\I5\ich7id2.inf
  PCI\VEN_8086&DEV_27DF=C:\D\M\I5\ich7ide.inf

id2's will lockup the 620s. An install from the CD will pick the right driver, but after imaging XP will grab the wrong one. Can you think of another way to "prioritize" the ide.inf's to prevent the lock ups? I would prefer to live my life w/ out sysprep. smile

SOLVED! An associate here at work was able to narrow down the problem to the ich7id2.inf file. This file causes the GX620 to crash on boot; the file, ich7ide.inf, is the one that is needed by this chipset. The fix is to not run the makePNF command. For some reason this will cause windows to grab the wrong driver. ...or at least that's in layman's terms.

4

(34 replies, posted in Other)

I'd be happy to, except I don't know how to create torrent files. I would need your help w/ how to get started. I would also feel a little better if a couple other people joined in, so my server doesn't get hammered (too much). Let me know what you think.

5

(34 replies, posted in Other)

I'm sure this has already come up, but have you guys thought about adding torrents? I've got a 4Mb pipe that never gets used that I'd be happy to seed on for a while. I've downloaded graphics B & C, but I can't get A. sad

JakeLD wrote:
[SysprepMassStorage]
  ;Intel IDE Controllers (ICH7 to ICH10)
  PCI\VEN_8086&DEV_2680=C:\D\M\I5\ESB2id2.inf 
  PCI\VEN_8086&DEV_2680=C:\D\M\I5\ESB2ide.inf 
  PCI\VEN_8086&DEV_269E=C:\D\M\I5\ESB2id2.inf 
  PCI\VEN_8086&DEV_269E=C:\D\M\I5\ESB2ide.inf 
  PCI\VEN_8086&DEV_27C0=C:\D\M\I5\ich7id2.inf 
  PCI\VEN_8086&DEV_27C0=C:\D\M\I5\ich7ide.inf 
  PCI\VEN_8086&DEV_27C4=C:\D\M\I5\ich7id2.inf 
  PCI\VEN_8086&DEV_27C4=C:\D\M\I5\ich7ide.inf 
  PCI\VEN_8086&DEV_27DF=C:\D\M\I5\ich7id2.inf 
  PCI\VEN_8086&DEV_27DF=C:\D\M\I5\ich7ide.inf 
  PCI\VEN_8086&DEV_2820=C:\D\M\I5\ich8id2.inf 
  PCI\VEN_8086&DEV_2820=C:\D\M\I5\ich8ide.inf 
  PCI\VEN_8086&DEV_2821=C:\D\M\I5\ich8ahci.inf 
  PCI\VEN_8086&DEV_2824=C:\D\M\I5\ich8ahci.inf 
  PCI\VEN_8086&DEV_2825=C:\D\M\I5\ich8id2.inf 
  PCI\VEN_8086&DEV_2825=C:\D\M\I5\ich8ide.inf 
  PCI\VEN_8086&DEV_2828=C:\D\M\I5\ich8id2.inf 
  PCI\VEN_8086&DEV_2828=C:\D\M\I5\ich8ide.inf 
  PCI\VEN_8086&DEV_2829=C:\D\M\I5\ich8ahci.inf 
  PCI\VEN_8086&DEV_2850=C:\D\M\I5\ich8id2.inf 
  PCI\VEN_8086&DEV_2850=C:\D\M\I5\ich8ide.inf 
  PCI\VEN_8086&DEV_2920=C:\D\M\I5\ich9id2.inf 
  PCI\VEN_8086&DEV_2920=C:\D\M\I5\ich9ide.inf 
  PCI\VEN_8086&DEV_2921=C:\D\M\I5\ich9id2.inf 
  PCI\VEN_8086&DEV_2921=C:\D\M\I5\ich9ide.inf 
  PCI\VEN_8086&DEV_2922=C:\D\M\I5\ich9ahci.inf 
  PCI\VEN_8086&DEV_2923=C:\D\M\I5\ich9ahci.inf 
  PCI\VEN_8086&DEV_2926=C:\D\M\I5\ich9id2.inf 
  PCI\VEN_8086&DEV_2926=C:\D\M\I5\ich9ide.inf 
  PCI\VEN_8086&DEV_2928=C:\D\M\I5\ich9id2.inf 
  PCI\VEN_8086&DEV_2928=C:\D\M\I5\ich9ide.inf 
  PCI\VEN_8086&DEV_292D=C:\D\M\I5\ich9id2.inf 
  PCI\VEN_8086&DEV_292D=C:\D\M\I5\ich9ide.inf 
  PCI\VEN_8086&DEV_3A00=C:\D\M\I5\ichaid2.inf 
  PCI\VEN_8086&DEV_3A00=C:\D\M\I5\ichaide.inf 
  PCI\VEN_8086&DEV_3A06=C:\D\M\I5\ichaid2.inf 
  PCI\VEN_8086&DEV_3A06=C:\D\M\I5\ichaide.inf 
  PCI\VEN_8086&DEV_3A20=C:\D\M\I5\ichaid2.inf 
  PCI\VEN_8086&DEV_3A20=C:\D\M\I5\ichaide.inf 
  PCI\VEN_8086&DEV_3A26=C:\D\M\I5\ichaid2.inf 
  PCI\VEN_8086&DEV_3A26=C:\D\M\I5\ichaide.inf

I also suggest you use the latest chipset pack:
http://driverpacks.sytes.net/driverpack … 32_810D.7z

Well, the latest build of the mass storage DP /w these drivers added to sysprep.inf is yielding the exact same problem. where the PC freezes after sysprep runs. Am I looking in the right place?
Thanks,

kickarse and JakeLD,

Thanks for the all your help I'm still working on a couple of your suggestions. My problem now is I've setup everything Kickarse has suggested (minus the sysprep driver scanner ....I'll get to it though) and sysprep has been running for over 3 hours and it looks like there's no end in sight. Also, are there any good fixes to accept the driver warning messages while sysprep is running? I have the driver policy set to ignore, but it's not really ignoring everything.

btw. Do you guys do contract work?
Thanks,

I also tried swapping out the new mass storage archive, but the issue persists.

Thanks for your patiencs w/ my noob questions.

JakeLD wrote:

Before you take your image file with ghost/acronis it's important to change your ide controller to "Standard Dual Channel PCI IDE Controller". Usually you should see Standard Dual, Primary and Secondary IDE Channel. You can do that in Device Manager by updating the driver. Also make sure to change you change your ACPI driver under My Computer in Device Manager with the "Advanced Configuration and Power Interface (ACPIP) PC". Also, never install any driver or the vmware tools in your image, it could cause major issues.

This is exactly my procedure, and it's worked 100% on my 8 other platforms. ..even w/o -bmsd, it just works. If the drivers need to be listed in sysprep.inf I don't see why my 755s would work w/o them. I think I'm not understanding something very fundamental to how this whole thing works. smile 


JakeLD wrote:

Well that's normal, mini-setup will redetect your hardware and find the best match. You must specify every ide/sata controller to their appropriate INF in your sysprep.inf. Your HWID is either in mshdc.inf (this one is populated by the bmsd switch) or in the I5 folder of massstorage. To find the hwid of your device, download the save_hwids.ex file located in my sig.

Also take notes that in the new mass storage pack we added support for Intel IDE controllers not supported natively. You can download our latest test pack at this address, a changelog is included:
http://driverpacks.sytes.net/driverpack … 32_810F.7z

It appears to be detecting the wrong driver (probably from the 755, or similar, as mentioned in previous posts). If I capture & deploy using ghost w/ out running sysprep, the 620 will boot install all drivers. It looks good until it reboots and fails to load the OS w/ out the safe mode fix. Sysprep appears to be doing the exact same thing, which I assume is applying the wrong driver. Is there over lap in the INFs?

Here is the relevant sections from the HWIDs script:
PCI\VEN_1002&DEV_5B62&SUBSYS_0B021002&REV_00\4&1603E009&0&0008: 256MB ATI RADEON X600
PCI\VEN_1002&DEV_5B72&SUBSYS_0B031002&REV_00\4&1603E009&0&0108: 256MB ATI RADEON X600 Secondary
PCI\VEN_14E4&DEV_1677&SUBSYS_01AD1028&REV_01\4&117729E2&0&00E0: Broadcom NetXtreme Gigabit Ethernet
PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_E1\3&172E68DD&0&F0: Intel(R) 82801 PCI Bridge - 244E
PCI\VEN_8086&DEV_2770&SUBSYS_00000000&REV_02\3&172E68DD&0&00: Intel(R) 945G/P Processor to I/O Controller - 2770
PCI\VEN_8086&DEV_2771&SUBSYS_00000000&REV_02\3&172E68DD&0&08: Intel(R) 945G/P PCI Express Root Port - 2771
PCI\VEN_8086&DEV_27B8&SUBSYS_00000000&REV_01\3&172E68DD&0&F8: Intel(R) 82801GB LPC Interface Controller - 27B8
PCI\VEN_8086&DEV_27C0&SUBSYS_01AD1028&REV_01\3&172E68DD&0&FA: Standard Dual Channel PCI IDE Controller
PCI\VEN_8086&DEV_27C8&SUBSYS_01AD1028&REV_01\3&172E68DD&0&E8: Standard Universal PCI to USB Host Controller
PCI\VEN_8086&DEV_27C9&SUBSYS_01AD1028&REV_01\3&172E68DD&0&E9: Standard Universal PCI to USB Host Controller
PCI\VEN_8086&DEV_27CA&SUBSYS_01AD1028&REV_01\3&172E68DD&0&EA: Standard Universal PCI to USB Host Controller
PCI\VEN_8086&DEV_27CB&SUBSYS_01AD1028&REV_01\3&172E68DD&0&EB: Standard Universal PCI to USB Host Controller
PCI\VEN_8086&DEV_27CC&SUBSYS_01AD1028&REV_01\3&172E68DD&0&EF: Standard Enhanced PCI to USB Host Controller
PCI\VEN_8086&DEV_27D0&SUBSYS_00000000&REV_01\3&172E68DD&0&E0: Intel(R) 82801GB PCI Express Root Port - 27D0
PCI\VEN_8086&DEV_27D2&SUBSYS_00000000&REV_01\3&172E68DD&0&E1: PCI standard PCI-to-PCI bridge
PCI\VEN_8086&DEV_27DA&SUBSYS_01AD1028&REV_01\3&172E68DD&0&FB: Intel(R) 82801GB SMBus Controller - 27DA
PCI\VEN_8086&DEV_27DE&SUBSYS_01AD1028&REV_01\3&172E68DD&0&F2: SoundMAX Integrated Digital Audio
PCI\VEN_8086&DEV_27DF&SUBSYS_01AD1028&REV_01\3&172E68DD&0&F9: Standard Dual Channel PCI IDE Controller
18 matching device(s) found.

I'm too green to know how to call these (or the needed ones) in my sysprep.inf. Any idea why I'm not having the same issue w/ my other platforms? btw. my install CD works on everything so far.


JakeLD wrote:

Good Luck!

Thanks, I need it! What a great project & community. I am using this for my company. Once I smooth out some rough edges and make a slick presentation, we'll be making donations.

Thanks guys,

That is what I'm currently doing, but after mini setup runs it changes it back to intel blah blah blah.

Should I try it w/ out -mini?

Hey guys,

I haven't been able to get any of these solutions to work. We've got a ton of 620, 745, 755s and I'm soooo close to rolling this out. I've become a huge fan of this project. After sysprep runs my 620s will not boot (the XP screen freezes), I can boot to safe mode and load the standard IDE controller, reboot, and everything is fine. As a dirty fix is there a way to force the standard IDE driver? Any and all help is appreciated.
Thanks,