Jeff,
You cannot do this. You must create separate images for each HAL type you
have. This article discusses our support policy. It is focused on Windows
XP but most of the concepts still apply
http://support.microsoft.com/default.aspx?scid=KB;EN-US;309283
Scott McArthur[MS]
Microsoft Windows Server Setup Support
This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
| Content-Class: urn:content-classes:message
| From: "JeffO" <
[email protected]>
| Sender: "JeffO" <
[email protected]>
| Subject: Sysprep for multiproc or Uniproc
| Date: Fri, 19 Sep 2003 14:13:12 -0700
| Lines: 9
| Message-ID: <
[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Thread-Index: AcN+8tW4AkAkcxSwRD+bgEnqJ2nJdg==
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Newsgroups: microsoft.public.win2000.setup_deployment
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.win2000.setup_deployment:6627
| NNTP-Posting-Host: TK2MSFTNGXA08 10.40.1.160
| X-Tomcat-NG: microsoft.public.win2000.setup_deployment
|
| I now have a SYSPREP.INF file that will strip the hardware
| configuration at the time sysprep is run and will plug-n-
| play without BSOD regardless of IDE or SCSI drives and
| regardless of controller.
| But I still BSOD when putting my sysprep'd image onto a
| dual processor PC.
| What line(s) do I have to add to strip out the ACPI
| configuration and force it to reconfig next time the image
| is booted?
|
