• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2637
  • Last Modified:

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
0
pnagl
Asked:
pnagl
  • 5
  • 5
  • 4
1 Solution
 
sj_hicksCommented:
Refer to my post in http://www.experts-exchange.com/Operating_Systems/WinXP/Q_21141797.html

It lists all mass storage device entries.  Include them all, re-sysprep machine and you should be fine on standard PCs.
0
 
QTCCKCommented:
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.
0
 
sj_hicksCommented:
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.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
sj_hicksCommented:
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.
0
 
pnaglAuthor Commented:
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
0
 
sj_hicksCommented:
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).
0
 
QTCCKCommented:
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.
0
 
pnaglAuthor Commented:
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
0
 
QTCCKCommented:

Both problems can be related to HAL/ACPI troubles. When I tried to use an image created on an older, non-ACPI PC, it would load up the dos-alike boot part, but fail to switch to the GUI setup.

Have a look at this link: http://support.microsoft.com/default.aspx?kbid=824664&product=vpcwin2004

I used the same method as described and it worked out well for me. BTW, as you encounter this problem it seems as if you successfully managed to work out the IDE controller troubles you had earlier - so don't give up. ;-)


Beside, I hope to have the opportunity to use a sysprepped image on Virtual PC tomorrow, as I want that for one of my projects, too (to have a clean master for packaging additional software to be deployed on the clones).


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

Paul
0
 
QTCCKCommented:
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.

0
 
sj_hicksCommented:
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.
0
 
pnaglAuthor Commented:
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.
0
 
QTCCKCommented:
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...

0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 5
  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now