Jump to content

Recommended Posts

Posted

Hello.

I'm having alot of trouble getting a sysprep install to properly detect the Intel Chipset in a TECRA M3 laptop. Here is what I have done so far.

I installed Windows XP SP1 from a CD that was unmodified other then having SP1 slipstreamed onto it. The CD was obtained from Microsoft Volume Licensing. This install I basically picked all of the base options. Because the ethernet NIC is so new there isn't even any networking on it.

I then copied a directory onto the hard drive of the laptop which contains the inf and cat files for all the intel chipsets integrated into one large directory. This directory was copied to c:\drv\intelinf.

I then created the following sysprep.inf file and placed it in the c:\sysprep directory along with the sysprep executable files.

Here is a copy of my sysprep.inf file

;SetupMgrTag

[unattended]

OemSkipEula=Yes

OEMPnPDriversPath = drv\intelinf

InstallFilesPath = "C:\Sysprep\i386"

OemPreinstall = Yes

KeepPageFile =

DriverSigningPolicy=Ignore

[GuiUnattended]

OEMSkipRegional=1

OEMDuplicatorstring="Sysprep Image P3.11"

TimeZone=10

OemSkipWelcome=1

AutoLogon = Yes

AutoLogonCount = 1

AdminPassword = "*******"

[userData]

FullName="Foo Inc."

OrgName="Foo Inc."

ComputerName=*

ProductKey=*****-*****-*****-*****-*****

[Display]

BitsPerPel=16

Xresolution=1024

YResolution=768

Vrefresh=60

[identification]

JoinWorkgroup=GLOBAL

[Networking]

InstallDefaultComponents=Yes

[sysprep]

BuildMassStorageSection=Yes

[branding]

BrandIEUsingUnattended=Yes

[Proxy]

Proxy_Enable=0

Use_Same_Proxy=0

After that is done I run c:\sysprep\sysprep.exe -reseal -mini -pnp. The system takes a fairly long time to sysprep then shuts off. At the moment all I do is reboot the system and when I do it goes through a nice automated mini setup. When the system reboots again I logon and check the device manager and nothing has changed. All of the chipset related components including PCI bridges, PCI Express stuff and USB drivers and many other things are still the generic drivers not the intel drivers.

In my experimentation I've added the drivers for the video card, lan, and sound to the OEMPNPDrivers line is sysprep.inf and they do get detected, just the chipset stuff doesn't. The only difference I can see is that most of the chipset stuff has been detected and identified as generic pci bridge or Standard USB Host controller, whereas everything else (which does get properly detected) is completely unkown to the OS.

Does anybody know what is going on here.


Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...