asked on

Sysprep troubles (MassStorage)

HI:

I have worked with sysprep with w2k and am fairly familiar with its operation - or at least I thought.

I am trying to build an image for XP. I used the feature for automatically building the [SysprepMassStorage] section and it looked like it would run ok. I tried testing it on a Virtual PC and it fails to load. I have attached the relevent parts of my sysprep.inf file.

1) How can I find out what mass storage driver an individual PC is using?
2) Does it look like there is anything wrong with my sysprep.inf file?

Thanks
Paul

[Unattended]
InstallFilesPath=C:\setup\i386
OemPnPDriverPath=setup\drivers\mk33\idewinxp
OemSkipEula=Yes
TargetPath=\WINDOWS

[GuiUnattended]
AdminPassword=
EncryptedAdminPassword=NO
AutoLogon=Yes
AutoLogonCount=1
OEMSkipRegional=1
TimeZone=3
OemSkipWelcome=1

[UserData]
ProductKey=
FullName="Registered User"
OrgName=""
ComputerName=%tagnumber%

[Display]
BitsPerPel=32
Xresolution=1024
YResolution=768

[Identification]
JoinWorkgroup=WORKGROUP

[Networking]
InstallDefaultComponents=No

[NetClients]
MS_MSClient=params.MS_MSClient

[Branding]
BrandIEUsingUnattended=Yes

[Sysprep]
BuildMassStorageSection=Yes

[SysprepMassStorage]
*int0800=c:\windows\inf\machine.inf
pci\ven_8086&dev_0008=c:\windows\inf\machine.inf
pci\ven_8086&dev_0326=c:\windows\inf\machine.inf
pci\ven_8086&dev_0483=c:\windows\inf\machine.inf
PCI\VEN_1106&DEV_0571=C:\Setup\drivers\MK33\IDEWinXP\VIAIDEXP.INF

sj_hicks

Refer to my post in https://www.experts-exchange.com/questions/21141797/XP-Sysprep-and-multiple-machine-types.html

It lists all mass storage device entries. Include them all, re-sysprep machine and you should be fine on standard PCs.

QTCCK

I would suggest that you - before sysprep'ing the master installation - change the IDE Adapter to "Standard PCI IDE" in the Device Manager, else Win XP might hang just before the Mini-Setup starts.

sj_hicks

While QTACCK's suggestion will probably work, I highly recommend adding the sysprep mass storage devices described above instead. This will allow for most hardware mass storage devices. If you have any non-standard ones such as SCSI raid boot devices or something, you should be able to determine the PNPID and inf driver file, includes the drivers in the image and make your own entry to sysprep.inf [SysprepMassStorage] section as well.

sj_hicks

If the above mass storage list doesn't work:
* Do a standard XP install on you virtual machine
* Determine the PNPID (PCI_VEN #) of the mass storage controller - I usually finding it thru WMI the easiest method
* Add the PCI_VEN number to the sysprep.inf. Chances are that you can just reference it to machine.inf.

pnagl

ASKER

I'll give it a try. In the link you gave me there are 2 sections; [SysprepMassStorage]
and [sysprepcleanup]. What does the sysprepcleanup section do?

Can you go in a little more detail on finding the PNPID? You said that "usually finding it thru WMI the easiest method". Can you give me a rough outline on doing that?

Thanks
Paul

sj_hicks

Paul, am unsure what [sysprepcleanup] is for. Don't recall seeing it before and can't see a reference to it in the deploy.chm helpfile.

The below URL is a link to a script which will list all PNP devices on the local machine including description and PNPID (Device ID). It'll list a lot of devices, so you'll need to look through them to determine you mass storage device.
http://www.microsoft.com/technet/community/scriptcenter/compmgmt/scrcm58.mspx

Have you tried re-sysprepping with the list of MassStorageDevices reference above? Note that the sysprep must be re-run; you can't just update the sysprep.inf in you image file (e.g. ghost image).

QTCCK

AFAIK, the [sysprepupcleanup] is automatically generated and added to the sysprep.inf once you start sysprep.

I don't recall having put it in any sysprep.inf myself, but I recall having seen it there on machines I finalized, but didn't allow to shutdown.

pnagl

ASKER

I just tried re-sysprepping and it failed on both of my test machines. One is a virtual PC andthe other is a PC with an AOpen motherboard. It seems weird that the virtual pc would give me problems since I don't need any special drivers to install to that one. I parsed the inf for the controller and thought I had the rith pnpid which i included in sysprep. The Virtual PC gives me an unrecoverable processor error while the other one makes it through the non graphical startup (the white progress bar completes) and then just stops.

Paul

ASKER CERTIFIED SOLUTION

QTCCK

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

pnagl

ASKER

I'll try re-syspreping it and disabling ACPI. Can I just delete anything that says ACPI out of device manager?

Paul

QTCCK

I am afraid, this won't work, if I got you right.

You either need to disable ACPI and do a repair installation on the original, then sysprep it; or do a repair installation on the clone.

I would opt for the second. Leave the original as it is and do the repair installation on the clone.

sj_hicks

What machine are you creating the sysprep image on? I usually use an older PC for which XP has all the drivers built in (HP Vectra or similar). This is generally quite compatible with most hardware. The other option is to try create the image on the PC with the AOpen MB (or event the virtual PC) and see if it will the work on the other hardware.

I wouldn't recommend disabling ACPI or using a non-ACPI HAL.

pnagl

ASKER

Yeah, Unfortunately I did the image on my new Dell 600m. That was a mistake. I am going to try and do the recovery on the virtual pc and if it is good make that my master platform.

QTCCK

Depending on what youintend to do, creating an ACPI enabled master is not the worst thing to have; without ACPI, you loose some functionality on newer PC, like XP shutting down in a orderly manner and turning the machine off when you hit the power button of the PC.

People are getting used to this behaviour and without ACPI HAL the PC just turns off...