stickzilla

If you have the proper registry keys prepared you can inject them into the registry and copy the .inf and .sys as well to the machine via booting up into Bart PE, and the machine will then boot up on its own After you first boot up I personally recommend then manually reinstalling the drivers while actually in win2k3 (ive done this in 2000 also) This is meant for migrating a machine that may be too complicated to rebuild (or your guys are just lazy!) to completely new hardware.

I've actually got this procedure working, and I have edited and updated the tool I found to work with the P400 SAS controllers that come with HP G5 ML370s. If anybody is interested in me posting a guide for injecting drivers, I'll gladly do it.

At first I was thinking that maybe this poster had a legitimate problem - that these Audio CDs he was working with were custom CDRs that actually did have .WAV files. But my my ! Listen to these fine folk and you'll be A-OK.

I'd be willing to bet that had you left your install alone as a normal Windows XP install, you wouldn't be having these issues. You disabled or removed a needed service, you can't figure out why, and now you're blaming the OS for your mistakes. If people would just leave Windows XP's services alone and not try to "tweak" them, they wouldn't have any issues with their software or hardware. Actually you are just jumping into your guns again. I've been on people's PCs where certain Wireless Network Configuration Utilities would work better than the Windows one, sometimes worse. And by better I mean pick up networks that the others just wouldn't connect to. It's not always people "tweaking".

I'm with allen2, about the audio drivers. A few years back on a machine with similar specs, I was having odd crashes when I was playing media through WMP. Updating the audio drivers ended up fixing it for me.

You think this would work ? - Load the image, but obviously don't boot into it - boot into Bart PE - stage the KB file - Load the registry - edit Run Once to do a silent install - save the registry - take another image of this - load it and see what happens ? heh.

When you stop the services, are you then changing the Startup Type to Disabled ? This is assuming you are doing this through the mmc. Just wanna make sure you aren't simply stopping the service but allowing it to have the Automatic Startup Type.

Just an idea - You have a backup of your Daily XP HD already, but you don't want to lose the work you've done since. Hopefully, the work you've done since is mostly files ? Perhaps .docs, .jpegs, whatever it is that corresponds with your business. Do you have the ability to take a new backup of the XP Daily, then mount it and check to see if your recent files are available (if the HD is screwed, you may not be able to mount the image properly) ? Then just restore the Old XP Daily clone, and then restore those files ? In the end you hopefully get everything back to how you wanted it ?

I promise not to keep bumping this, just wondering if anybody has any answers !

I really don't know if you can have multiple entries, I'd assume not. You are in unknown, testing territory now !

I think it would be worth testing it this way : Create the image on a multiprocessor machine. In the top of your sysprep.inf, in the [unattended] section, add : UpdateUPHAL="ACPIAPIC_UP,%WINDIR%\Inf\Hal.inf" What this will do is during mini setup it will detect if it should remain a halmacpi like when you created the image, or switch to a halaacpi automatically for you. ------------------------------------------ Now I don't know if your older machines are non ACPI. For them, you may have to rely on a doing a manual copy/paste of the hal and kernel files as you've mentioned you do as part of the cmdlines. I honestly don't know about that...because I've never had to work with that.

Have you tried allowing sysprep.ini to determine/assign the HAL for you ? I personally create images using a multiprocessor machine, then let : UpdateUPHAL="ACPIAPIC_UP,%WINDIR%\Inf\Hal.inf" do the changing for me in the sysprep.ini, if it detects the need to. If your image is created on a Uniprocessor, I believe you can change the command to accomodate also. May be of use to you.

I'm curious as to what kind of procedures will create a local profile on an XP pro machine. Scenario : Let's say my machine is a member of a domain. Somebody else has administrative rights also, USERX. I go into SystemDrive\Documents and Settings\ and there are no extra profiles in existence, other than mine and the system ones. The next day, USERX's profile is now there, and the event log just shows generic logon/logoff information repeatedly. Aside from the obvious answers of USERX sitting at my desktop and logging in, thus creating a profile (or using RDP to log in to my workstation), what else can be done remotely that will result in a USERX profile being created ? Let's not count those answers, because I know those aren't happening. I'm asking just out of curiousity. I notice that sometimes when people connect to my machine through a scripting procedure of sorts, a profile is created for them.

I finally got around to doing this today, and... it failed to boot. I'm sure there is some kind of "sysprep equivalent" for this ubuntu distro, I just was curious if it was going to automatically adapt heh.

You sir, inspire adventure and curiosity ! TO THE BOOT DISK WE GO !