adding drivers to an iso image

G

Guest

I have an iso image of XP with service pack 2 and I want to add some chipset
drivers SATA drivers and alike (from Intel) so that I can complete an
install of the OS. I add the drivers per the Intel docs but setup cannot seem
to find them.

After adding the drivers to the image I burn it onto a CD and re-boot. The
setup process proceeds until it cannot recognize the drive type. My thought
was that if I put the drivers on the ISO setup would find them but this does
not work.

Any help would be appreciated.
 
M

Mario Schmidt

sienaman said:
I have an iso image of XP with service pack 2 and I want to add some chipset
drivers SATA drivers and alike (from Intel) so that I can complete an
install of the OS. I add the drivers per the Intel docs but setup cannot seem
to find them.

After adding the drivers to the image I burn it onto a CD and re-boot. The
setup process proceeds until it cannot recognize the drive type. My thought
was that if I put the drivers on the ISO setup would find them but this does
not work.

Any help would be appreciated.
Click to expand...

http://unattended.msfn.org/unattended.xp/view/web/36/SESSID=5bcc818cc517175eb418203b42b796c9/

A lot of other interesting stuff there.
 
M

Mario Schmidt

Mario said:
http://unattended.msfn.org/unattended.xp/view/web/36/SESSID=5bcc818cc517175eb418203b42b796c9/
Click to expand...

BTW:

The copy-section on that page is NOT COMPLETE! You also have to copy the
..sys file of the driver directly to you I386 folder on the CD. If there
is already a file with the same name but a ".sy_" as the extension,
delete that existing file.

It is IMPORTANT that you can' t just copy & paste stuff shown there, you
have to use the information provided by the TXTSETUP.OEM file of YOUR
drivers instead!
 
G

Guest

Mario, thanks for the info but these particular drivers do not come with a
TXTSETUP.OEM. The driver set does some with a file called INFAnswer.txt but
it does not look anything like TXTSETUP.OEM. The contents of the file are as
follows, any info you have would be appreciated.

;
********************************************************************************
;
********************************************************************************
; ** Filename: INFAnswer.txt **
; ** Abstract: Windows* XP installation answer file to enable
; ** Intel(R) INF file preload.
; ** Last Update: Sept 12, 2003 (Version 6.0.0 Build 1001)
;
********************************************************************************
;
********************************************************************************
; Sample Unattended Setup Answer File **
; **
; This file contains information about how to automate the installation **
; or upgrade of Windows XP Pro Codename Whistler so the **
; Setup program runs without requiring user input. **
;
********************************************************************************

[Unattended]
UnattendMode=Fullunattend
UnattendSwitch=Yes
OemPreinstall=Yes
ConfirmHardware=No
OverwriteOemFilesOnupgrade=No
OemSkipEula=Yes
TargetPath=WINDOWS
;Filesystem=ConvertNTFS
DriverSigningPolicy=Ignore
OemPnPDriversPath="DRIVERS\INTELINF"
CrushDumpSetting=1

[UserData]
FullName="User_Name"
OrgName="Corporation_Name"
ComputerName=*
ProductKey="xxxxx-xxxxx-xxxxx-xxxxx-xxxxx"

[GuiUnattended]
Timezone=4 ;Set to the Pacific Northwest
AdminPassword=*
AutoLogon=Yes
AutoLogonCount=99
OemSkipReginal=1
OemSkipWelcome=1

[Display]
BitsPerPel=16
XResolution=640
YResolution=480
VRefresh=60

[RegionalSettings]
LanguageGroup=1
SystemLocale=00000409
UserLocale=00000409
InputLocale=0409:00000409

[Shell]
DefaultStartPaneloff=Yes

[ComputerSettings]
PowerScheme=Presentation

[Branding]
BrandIEUsingUnattended=Yes

[Networking]
InstallDefaultComponents=Yes

[NetAdapters]
Adapter1=params.Adapter1

[params.Adapter1]
INFID=*

[NetClients]
MS_MSClient=parama.MS_MSClient

[NetServices]
MS_SERVER=params.MS_Server

[NetProtocols]
MS_TCPIP=params.MS_TCPIP

[params.MS_TCPIP]
DNS=Yes
UseDomainNameDevolution=No
EnableLMHosts=Yes
AdapterSelections=params.MS_TCPIP.Adapter1

[params.MS_TCPIP.Adapter1]
SpecificTo=Adapter1
DHCP=Yes
WINS=No
NetBIOSOptions=0

;
********************************************************************************
; Copyright (c) 2003 Intel Corporation **
; Copyright (c) 1994 - 2002 Microsoft Corporation **
; **
;
********************************************************************************
; Intel is making no claims of usability, effecacy or warranty **
;
********************************************************************************
; Information in this document is provided in connection with Intel
products. **
; No license, express or implied, by estoppel or otherwise, to any
intellectual **
; property rights is granted by this document. Intel assumes no liability **
; whatsoever, and Intel disclaims any express or implied warranty, relating
to **
; sale and/or use of Intel products for particular purpose, merchantability,
or **
; infringement of any patent, copyright or other intellectual property
right. **
; Intel products are not intended for use in medical, life saving, or life **
; sustaining applications. **
;
;
********************************************************************************
; Intel corporation disclaims all warranties and liabilities for the use of **
; this document and the information contained herein, and assumes no **
; responsibility for any errors which may appear in this document, nor does **
; Intel makes a commitment to update the information contained herein.
Intel **
; reserves the right to make changes to this document at any time, without **
; notice. **
;
********************************************************************************
;
********************************************************************************

; Third-party brands and names are the property of their respective owners. **
;
********************************************************************************
;*********************************************************************************
 
M

Mario Schmidt

sienaman said:
Mario, thanks for the info but these particular drivers do not come with a
TXTSETUP.OEM. The driver set does some with a file called INFAnswer.txt but
it does not look anything like TXTSETUP.OEM. The contents of the file are as
follows, any info you have would be appreciated.
Click to expand...

You may get the same info from the .inf file that is with the SATA
drivers. There you can find the PCI-IDs and Device-IDs etc. The missing
parts you have to fiddle together with the given information on the site.
 
M

Mario Schmidt

sienaman said:
Mario, thanks for the info but these particular drivers do not come with a
TXTSETUP.OEM. The driver set does some with a file called INFAnswer.txt but
it does not look anything like TXTSETUP.OEM. The contents of the file are as
follows, any info you have would be appreciated.
Click to expand...

You may also post a link to the drivers so that I may take a look into it.
 
M

Mario Schmidt

You may also take a look at www.driverpacks.net

The guy hosting that site makes driver packs of most common hardware
that can be integrated easily in the windows distribution. There is also
a MassStorage Driver Pack that takes care of some SATA drivers. Maybe
yours is supported?

Reading documentation on the site is NECESSARY BTW.
 
G

Guest

Hi Mario

Is this procedure applicable to all kinds of drivers ?
I want to integrate to my win xp pro sp2 CD
the driver of my TFT Display, SATA/RAID-Controller on my MB,
maybe some others yets.

--
win xp pro sp 2 engl
intel p4 2.8 533
1 GB RAM
asus p4s800d-e dlx
asus 9600XT TVD 128 MB
PATA WD 80 GB
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

adding drivers during install 1
Windows XP Service Pack 3 - ISO-9660 CD Image File 8
Sysprep doesn't find drivers? 5
Not all $OEM$\Drivers are loaded 1
Sysprep Not adding entries to CriticalDeviceDatabase 1
Adding Drivers to WinXP WIM Image via System Image Manager 3
add drivers to sysprep for ghost image 1
Adding PnP drivers to a Sysprep image 2

Top