I made an older pack which I am in the process of updating. Link is below.
http://www.mediafire.com/file/ep33ppd6z … storage.7z

From my testing, you can't use ibexahci.inf,Tcrkahci.inf,and cougahci.inf as they require msahci which is not included in windows xp. These drivers are for windows vista and above. I have no idea how you even got them to sysprep; when I try them on xp an error pops up when I attempt to run sysprep.
Also, you have a lot of duplicate entries in i2, i3 and i9 which maybe causing some other issues.

can you post your sysprep.inf?

54

(109 replies, posted in Universal Imaging)

I haven't done anything with virtualbox lately, so I cant help you troubleshoot your slowness. I changed to vmware awhile back and have had good results with it. I do have a beefier system than what you have.
As for the continue/stop issue, I have never seen it get stuck in a loop. In order to get rid of those messages, I would have to remove the drivers that would cause the conflict. That would be a lot of hwids that wouldn't be included then.( I blame manufacturers for not making unique file names for files and/or universal drivers with all hwids.)
I will be redoing the pack shortly and will see what I can fix.

Are you adding all of those at once?

56

(109 replies, posted in Universal Imaging)

Vmware is great also even though it isn't free. I use it over virtualbox. It is also a great addition to your/my resume tongue

57

(109 replies, posted in Universal Imaging)

You should grab virtualbox or vmware workstation and make your images from there. It is way simpler and faster than a real pc/laptop.

58

(109 replies, posted in Universal Imaging)

I checked out a D600 and it uses the 8086:24CA. if you are using the sysprep.inf and the mass storage files that I linked you should have no problem.
I will have an updated version shortly that may help your issues, but it may be something with your process.

59

(109 replies, posted in Universal Imaging)

Can you post the models of the laptops?

60

(109 replies, posted in Universal Imaging)

Glad it worked. You could always try a Windows 7 PE disk to grab your hwids. I am quite surprised you have all the lines for scsi in your sysprep. I haven't used or seen them in a long time.
Here is my 2010 syprep and mass storage : http://www.mediafire.com/?ep33ppd6z1rg7se
It has quite a bit more hwids if you end up needing them.

61

(109 replies, posted in Universal Imaging)

I just loaded a GX620 here at work. It showed two different hwids in the device manager: 8086:27DF (ICH7) and 8086:27C0 (N10/ICH7). I am using the ich78id2.inf. I am using the one from intel since mr_smartepants said he modified it to break driver signing. Sata controller is set to normal in bios.

62

(109 replies, posted in Universal Imaging)

Dell 620 and D800 machines are common machines that I image at work. I don't have problems with the image that I use. Can you post your sysprep.inf?

63

(109 replies, posted in Universal Imaging)

The line looks correct.
ich78id2.inf  requires intelide.sys
ich78ide.inf requires pciide.sys.
Pciide.sys is a generic driver so it maybe more compatible. It does not support hot swap like the intelide driver.
If one doesnt work, I would try the other.

64

(109 replies, posted in Universal Imaging)

If you are calling the mass storage drivers from the sysprep.inf, you do not need steps 14-20.
Remove detect non plug and play from step 24. It doesn't do anything anymore and it adds time to the sysprep process.

Here is the driver from that toshiba zip file
http://www.mediafire.com/file/i62sbvh1xfflbzo/Driver.7z

66

(109 replies, posted in Universal Imaging)

you can manually open the inf files and look in them to see which ones are contained in them
or
run Find Hwid's by kickarse on the folder, it will output a file with the hwids and what they are.

67

(109 replies, posted in Universal Imaging)

you driver is contained in the masstorage pack, I8 folder. Assuming that you keep the same folder structure of the masstorage pack your line for sysprep should look like:

PCI\VEN_8086&DEV_3B2F&CC_0106="C:\D\M\I8\iaAHCI.inf"

68

(5 replies, posted in Universal Imaging)

Download all the driverpacks and extract them to a folder.
Download Findhwids from kickarse -link provided  (http://www.mediafire.com/?8c2hh92s85ofqt2)
Start the program, choose where the driverpacks where extracted to, choose a path for the csv, and then hit start.
You should get a large csv file of all the hwids and vendors that exist in the packs.

That happens because it installs a driver and then tries to install a driver that is newer. You would have to remove the either the old or newer driver. I just end up clicking continue anyway.

http://www.mediafire.com/file/ep33ppd6z … storage.7z
Here is the stripped down version of the mass storage pack that I use with sysprep. Make sure that you put the M folder in C:\D otherwise it wont find the driver files. I have included my sysprep.inf so you can just copy and past it into yours.

I will post the pack and sysprep file on when I get back from holiday vacation. If you are repairing only oem brands than there is no reason not to use pre-activation. You don't have to worry about entering keys from coa stickers and your image will stay intact indefinitely( ie no expiration after 30 days).

As for my image process, I use Vmware workstation for the building of my images. I create a virtual machine, install xp, do all the updates, remove all the leftover crap from the updates, install the software that I want ( openoffice, pdf reader, free av , etc.), install my tweaks, copy sysprep folder and driverpack folder over and then run the sysprep process. Once it shuts down, I run Bart PE and choose offlinesysprep, hal detection at first boot. Then I create a disk image with ghost. I then repeat this process for XP home and XP media center.

For oemscan, I've seen it but never used it. I use another one called Oembios changer. Its more manual and I only really use it after I have a good dell image.( I clone the vm, change it from dell to another oem and then capture the image).I hope to eventually work on a automatic solution, but I may just not bother with it as windows 7 becomes more widely used.

1:  If the intelppm does not appear in the registry then you should not have to have a script to disable it. It wont be a problem if you restore it on an amd computer. You should also be looking in HKLM\SYSTEM\CurrentControlSet\Services\intelppm. This bug with intelppm is more suited for amd computers that were upgraded with sp2/3 and that the original image was created on an intel pc. I would assume that since you are going with an image that you would have SP3 and the latest servicepack already integrated, thereby negating the problem. (Of all the images that I have created and the thousands of computers that I have restored, I have never seen this error).

2:I use disk to image with ghost. Partition to image does not work.

3: You can only use offlinesysprep if you wish to integrate all of the drivers from the driverpacks mass storage. If you don't want to use offlinesysprep, you can use sysprep's way of loading drivers but you are limited in how many drivers can be loaded. The drivers in the driver pack consist of ide, sata, scsi and fibre channel drivers. For the desktops that I encounter, I only use ide and sata. My images use the sysprep way and only load the ide/sata drivers. If you choose to go this way I can provide the sysprep entries and modified mass storage pack.

4: Since you are fixing mostly major oem brands of computers ( dell, HP, etc) you should be using Oem pre-activated XP. All major oems use this kind of XP. You should not be using the COA sticker key. Since the OEM XP is preactivated, you will not run into the 30 day issue. ( If you dont believe me, grab a Dell XP restore cd, load it up on your inspiron b120. You will see that its activated once windows is finished. Grab magicjellybean keyfinder and you will see that the xp key doesnt match the coa sticker) Explaining OEM pre-activation is best for another post.

Other thoughts: You can't change sata to ide mode on every computer so you definitely need to integrated the drivers somehow. There is also a performance hit if you go that route.
As for the hal changing, I use the offlinesysprep to do the hal change. It works most (95%) of the time. I always use the base image with the ACPI PC hal.

ahci7xx.sys is currently located in D\M\AM2 of masstorage pack 9.01.
maybe your download is corrupt.

Try to add this to sysprep.inf:
PCI\VEN_8086&DEV_2652&CC_0104="C:\D\M\I2\IASTOR70.inf" ; SCSIAdapter - Intel(R) 82801FR SATA RAID Controller
PCI\VEN_8086&DEV_2653&CC_0106="C:\D\M\I3\IAAHCI.INF" ; hdc - Intel(R) 82801FBM SATA AHCI Controller
PCI\VEN_8086&DEV_2681&CC_0106="C:\D\M\I4\iaAHCI.inf" ; hdc - Intel(R) ESB2 SATA AHCI Controller
PCI\VEN_8086&DEV_27C1&CC_0106="C:\D\M\I4\iaAHCI.inf" ; hdc - Intel(R) ICH7R/DH SATA AHCI Controller
PCI\VEN_8086&DEV_27C5&CC_0106="C:\D\M\I4\iaAHCI.inf" ; hdc - Intel(R) ICH7M/MDH SATA AHCI Controller
PCI\VEN_8086&DEV_2821&CC_0106="C:\D\M\I4\iaAHCI.inf" ; hdc - Intel(R) ICH8R/DH/DO SATA AHCI Controller
PCI\VEN_8086&DEV_2829&CC_0106="C:\D\M\I4\iaAHCI.inf" ; hdc - Intel(R) ICH8M-E/M SATA AHCI Controller
PCI\VEN_8086&DEV_2922&CC_0106="C:\D\M\I4\iaAHCI.inf" ; hdc - Intel(R) ICH9R/DO/DH SATA AHCI Controller
PCI\VEN_8086&DEV_5029&CC_0106="C:\D\M\I3\IAAHCI.INF" ; hdc - Intel(R) EP 80579 SATA AHCI Controller
PCI\VEN_8086&DEV_2682&CC_0104="C:\D\M\I4\iaStor.inf" ; SCSIAdapter - Intel(R) ESB2 SATA RAID Controller
PCI\VEN_8086&DEV_27C3&CC_0104="C:\D\M\I4\iaStor.inf" ; SCSIAdapter - Intel(R) ICH7R/DH SATA RAID Controller
PCI\VEN_8086&DEV_27C6&CC_0104="C:\D\M\I4\iaStor.inf" ; SCSIAdapter - Intel(R) ICH7MDH SATA RAID Controller
PCI\VEN_8086&DEV_2822&CC_0104="C:\D\M\I4\iaStor.inf" ; SCSIAdapter - Intel(R) ICH8R/ICH9R/ICH10R/DO SATA RAID Controller
PCI\VEN_8086&DEV_282A&CC_0104="C:\D\M\I4\iaStor.inf" ; SCSIAdapter - Intel(R) ICH8M-E/ICH9M-E SATA RAID Controller
PCI\VEN_8086&DEV_2929&CC_0106="C:\D\M\I4\iaAHCI.inf" ; hdc - Intel(R) ICH9M-E/M SATA AHCI Controller
PCI\VEN_8086&DEV_3A02&CC_0106="C:\D\M\I4\iaAHCI.inf" ; hdc - Intel(R) ICH10D/DO SATA AHCI Controller
PCI\VEN_8086&DEV_3A22&CC_0106="C:\D\M\I4\iaAHCI.inf" ; hdc - Intel(R) ICH10R SATA AHCI Controller
PCI\VEN_8086&DEV_2680="C:\D\M\I5\ESB2ide.inf" ; hdc - Intel(R) 631xESB/6321ESB/3100 Chipset Serial ATA Storage Controller - 2680
PCI\VEN_8086&DEV_269E="C:\D\M\I5\ESB2ide.inf" ; hdc - Intel(R) 631xESB/6321ESB Ultra ATA Storage Controller - 269E
PCI\VEN_8086&DEV_27C0="C:\D\M\I5\ich7ide.inf" ; hdc - Intel(R) 82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controller - 27C0
PCI\VEN_8086&DEV_27C4="C:\D\M\I5\ich7ide.inf" ; hdc - Intel(R) 82801GBM/GHM (ICH7-M Family) Serial ATA Storage Controller - 27C4
PCI\VEN_8086&DEV_27DF="C:\D\M\I5\ich7ide.inf" ; hdc - Intel(R) 82801G (ICH7 Family) Ultra ATA Storage Controllers - 27DF
PCI\VEN_8086&DEV_2820="C:\D\M\I5\ich8ide.inf" ; hdc - Intel(R) ICH8 4 port Serial ATA Storage Controller - 2820
PCI\VEN_8086&DEV_2825="C:\D\M\I5\ich8ide.inf" ; hdc - Intel(R) ICH8 2 port Serial ATA Storage Controller - 2825
PCI\VEN_8086&DEV_2828="C:\D\M\I5\ich8ide.inf" ; hdc - Intel(R) ICH8M 3 port Serial ATA Storage Controller - 2828
PCI\VEN_8086&DEV_2850="C:\D\M\I5\ich8ide.inf" ; hdc - Intel(R) ICH8M Ultra ATA Storage Controllers - 2850
PCI\VEN_8086&DEV_2920="C:\D\M\I5\ich9ide.inf" ; hdc - Intel(R) ICH9R/DO/DH 4 port Serial ATA Storage Controller 1 - 2920
PCI\VEN_8086&DEV_2921="C:\D\M\I5\ich9ide.inf" ; hdc - Intel(R) ICH9 Family 2 port Serial ATA Storage Controller 1 - 2921
PCI\VEN_8086&DEV_2926="C:\D\M\I5\ich9ide.inf" ; hdc - Intel(R) ICH9 Family 2 port Serial ATA Storage Controller 2 - 2926
PCI\VEN_8086&DEV_2928="C:\D\M\I5\ich9ide.inf" ; hdc - Intel(R) ICH9M/M-E 2 port Serial ATA Storage Controller 1 - 2928
PCI\VEN_8086&DEV_292D="C:\D\M\I5\ich9ide.inf" ; hdc - Intel(R) ICH9M/M-E 2 port Serial ATA Storage Controller 2 - 292D
PCI\VEN_8086&DEV_3A00="C:\D\M\I5\ichaide.inf" ; hdc - Intel(R) ICH10 Family 4 port Serial ATA Storage Controller 1 - 3A00
PCI\VEN_8086&DEV_3A06="C:\D\M\I5\ichaide.inf" ; hdc - Intel(R) ICH10 Family 2 port Serial ATA Storage Controller 2 - 3A06
PCI\VEN_8086&DEV_3A20="C:\D\M\I5\ichaide.inf" ; hdc - Intel(R) ICH10 Family 4 port Serial ATA Storage Controller 1 - 3A20
PCI\VEN_8086&DEV_3A26="C:\D\M\I5\ichaide.inf" ; hdc - Intel(R) ICH10 Family 2 port Serial ATA Storage Controller 2 - 3A26

is there any secret code/switch in the finisher to have it not delete the drivers?