My bro has the exact same bug, testing right now.

At least we know AD is causing an issue. I will look into it, for now I suggest you get rid of it if you don't need it of course. I will download the latest driver of both manufacturer and keep the one that fits both. (If possible)

This driver seems more recent http://driverdownloads.qlogic.com/QLogi … ocid=20052

The driver is indeed missing, I added to our next test pack. I will put it online asap and give you the link so you can test. Thanks for reporting.

I verified with Oveflow, for Jmicron we use drivers from their official ftp so no change has been made to the INF file. So it was a DriverImport issue.

Try this one please ftp://driver.jmicron.com.tw/jmb36x/Win2 … 09WHQL.zip

R1.17.42.09WHQL (10/23/08')

    - Fail to enter hibernation on some platforms.

Be patient my friend, roguespear is very busy...we all are. But I'm sure he won't forget you. big_smile

158

(88 replies, posted in DriverPack LAN)

Well it should be available in the next few days then.

159

(88 replies, posted in DriverPack LAN)

Fragbert, I just want to let you know that I'm already aware of 13.3 however I'm still looking for it on intel website. So if you have the direct link please post it. Thank you.

KB888111.exe is part of XP SP3 so I suggest you update your OS pal. Leave the past behind. big_smile

Kickarse is right a HAL issue won't show you any bsod. In fact, you will get a black screen.

No problem, I'll work on it.

In order to help you earl7 we need some details. Please provide us a direct link to download the driver or at least the motherboard website. Also we need the hwids list of your hardware. Please run the save_hwids located in my sig.

RogueSpear is on fire. big_smile

I agree CRT drivers are irrelevant.

The fix is to not run the makePNF command

I'm not running it either cause I have heard some people having issues with it. Thanks for letting us know.

Wow great work RogueSpear big_smile

that 5% always takes 95% of the whole time...irony big_smile

Well I got the info I need so far, thank you. I will attempt to fix your issue in the next days. nVidia mess is driving everyone crazy.

MrGuitar wrote:

sysprep has been running for over 3 hours and it looks like there's no end in sight

3 possible reasons:

1. one of your HWID is wrong
2. one or your INF path or filename is wrong
3. There is an HWID duplicated in your sysprep.inf For example nvidia nForce4 has 2 flavor of the same driver one for intel one for AMD. You can only use one of the INF in the sysprep.inf because the driver share the same HWIDs and the sys file name is identical. So they overwrite eachothers.

Same thing happens for intel iastor.inf, intel has different drivers but they all use the same inf file name. So the last one specified in your sysprep.inf overwrite the previous ones...That's why OfflineSyprep is way better, it only inject the drivers you need so no conflicting driver!


You must verify every lines and make sure they are valid. Take notes that when we update the mass storage pack you must reverify all your paths since they can change.

Jake's agree with Kickarse

mrguitar wrote:

If the drivers need to be listed in sysprep.inf I don't see why my 755s would work w/o them

Probably because your others ide devices are supported by mshdc.inf and are populated by the bmsd switch. In fact Intel ICH1 to ICH6 is supported by mshdc.inf in XP. The hard drive controller your having problem with is an ICH7 controller so it must be specify in sysprep.inf or you will have troubles.

Mshdc.inf refer to pciide.sys and intelide.sys which are present natively in XP. Here is what your SysprepMassStorage section should look like:

[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

I've searched into whole DriverPacks for PCI\VEN_8086&DEV_27C0 and PCI\VEN_8086&DEV_27DF, they are only referenced in I5, so no conflicting driver with the latest DriverPacks.

Since OverFlow is a noob with sysprep big_smile, I will help you.

"As a dirty fix is there a way to force the standard IDE driver? Any and all help is appreciated. "

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.

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

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

Good Luck!

Chipset, LAN and Mass are next.

I must disagree, I don't see the point of including drivers already supported by pciide.sys and intelide.sys which are inclued in 2K,XP and 2K3. Unless the INF fixes some issues and I doubt this since there is no sys file updates. DriverPacks officially support 2K, XP and 2K3 and that's it for now.