DriverPacks.net Forum - Driverpacks Slipstream breaks XP home install

Re: Driverpacks Slipstream breaks XP home install

2010-12-23T07:59:42Z

Never use a copy downloaded from the net. You have no idea what you are going to get. Mostly / usually a headache.

Only use an Original Hologramed disc as your source. (no hash required)

Warez and Pirating are not supported... Go Legit or go home.

Closed.

Re: Driverpacks Slipstream breaks XP home install

2010-12-22T21:49:09Z

I'll have to remake it, but I'll have a full copy of the winnt file for you this afternoon (australia time ^_^). I do remember checking the winnt file earlier and finding it ok however. Something I haven't considered is that it isn't a proper RTM copy of xp home sp3 (maybe a slipstreamed one or something). if you could post the hashsum of it, that would be useful, otherwise I'll try finding a different XP home source and trying the same process (thanks to our good friends at bittorrent).

Re: Driverpacks Slipstream breaks XP home install

2010-12-22T06:26:09Z

Well that's very odd considering DriverPacks BASE only adds 3 lines to the winnt.sif and they don't affect account creation. You didn't mention, so I can only assume you're doing a full install, not an upgrade (the winnt.sif entries break the win32 upgrade process).
Verify that the below entry exists in the winnt.sif after DriverPacks integration.

[UserData]
ComputerName=*
FullName="Whatever"

Driverpacks Slipstream breaks XP home install

2010-12-22T03:56:36Z

So I've had a recent issue when trying to set up an automated XP Home. I use a winnt.sif automation tool, slipstream the updates using ryanVM, then run the driverpacks slipstream tool (method 2 with KTD). Now, for the XP Pro CD, this works just fine. For the XP Home CD, it causes the user account creation to fail. Here's a picture of it on first boot.

It can be fixed by going into safe mode-->administrator and creating an account, but I sure as h*ll don't want to do that every time. the XP home install works just fine with the updates and the unattended config. It's only when I try using the driverpacks, and only on the Home edition (like I said, same method works fine on Pro) that this happens. Anybody know why?

EDIT: Another couple of things, if I install *only* the mass storage drivers (for the text mode sequence) the home will still work. Also, if I do the full driverpacks install and then install it on a virtual machine, it works. It's only when doing a CD/DVD/USB install on another computer with a full driverpacks install that this issue happens. The disc I'm modifying is an RTM XP home SP3 CD. The driverpacks base program reports no errors when doing the actual slipstream. The user account never gets created in the first place (no account entry or folders created) so it's not just hiding the account. I've tested this on multiple systems.