Jump to content

lowteq

Member
  • Posts

    3
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Canada

About lowteq

lowteq's Achievements

0

Reputation

  1. 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.
  2. Hello. The quotes are correct in my actual unattend.txt file, I just quoted in my post. I also changed my $oem$ directory. So now I have a c:\$oem$\$1\drivers\net\ethernet directory which contains the decompressed driver files. In my unattend.txt file I still have the line OEMPnPDriversPath=drivers\net When I ran the installation again it still didn't work. Does anybody have any other hints? Thanks for the suggestions so far.
  3. Hello. I'm having some trouble getting the ethernet drivers to install during an unattended installation of Windows XP. I have placed the decompressed drivers in c:\$oem$\$1\drivers\net. In the [unattend] section of my unattended.txt file I have a line which says "OEMPNPDRIVESPATH=drivers\net". In the [Networking] section I have a line which says "InstallDefaultComponents=Yes". However after the install is finished I check the device manager and see that the ethernet drivers did not install. Have I missed something? I've read the guide on this site (thanks to whoever wrote that by the way) and variouis pieces of Microsoft documentation and can't see anything obvious. The ethernet drivers I'm trying to install is the HP NC10xx/67xx/77xx/150x/320x Gigabit Ethernet NIC Driver. Installing them manually using the upgrade driver option from device manager works fine. Anybody have any hints for me. They would be appreciated. Thank you.
×
×
  • Create New...