invalid key name and question about sata injection

has anyone tested a stable massStorage driverpack with xp sysprep?

i tested the sysprep on the same computer and ran the same command, reg add "HKLM\SYSTEM\ControlSet001\Services\intelppm" /v Start /t REG_DWORD /d 4 /f

it works and disable intelppm.
i believe the entry doesn't exist before. That could be error with invalid key name because i didn't install audio driver.

Last edited by roadorange (2010-12-20 18:41:27)

OverFlow, i really wanna thank you that you reply my post. i am happy. hahaha
4. The reason i ask about reset the trial to give 3 days because i don't like to call microsoft to activiate the product. I love to use internet activation with few clicks. I work in a computer repair center and definitenly use legitimate product and it's legitimate business. I understand each machine has product key to use to activiate.
Sometimes, the sysprep image is not able to grab all the driver and is not able to activiate over the internet. It just happens sometimes. In that case, i have to call microsoft.
That's why it's always good to have windows remain 3 days to use. So i can login windows and install the remaining driver. then activiate the windows over the internet.

3.i am working on offlinesysprep and i just made livexp. i am testing them. i will come back to this forum very soon.

i believe the registry key isn't exist before sysprep because i didn't install audio driver. But the intelppm.sys is still there. It still may cause blue screen when deploy to AMD. I think it might be good idea to rename the file. i duno.

thank you. overflow

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.

Mr_Smartepants wrote a script to make XP a preactivated copy (Like an OEM restore CD). I don't remember where he put it. MSFN.org i think... Ill ask him to chime in here . My guess is it only works for Installs and not for images though.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

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.

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.

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.