dk_
Content Type
Profiles
Forums
Events
Posts posted by dk_
-
-
to Br4tt3 - think the same
If you dhcp server send to deploying machine only IP - big reason to long resolveing NAME, IP of Primary Domain Controller. Try to manually set network parameters like:
[MS_TCPIP parameters]
DeadGWDetectDefault = No
DNSDomain = fabrikam.com
DNSSuffixSearchOrder = server1.fabrikam.com, fabrikam.com
DontAddDefaultGatewayDefault = No
EnableICMPRedirect = No
EnableLMHosts = Yes
EnableSecurity = Yes
ScopeID = REDMOND
SyncDomainWithMembership = 1
UseDomainNameDevolution = No
[params.MS_TCPIP.Adapter01]
SpecificTo = Adapter01
DisableDynamicUpdate = No
EnableAdapterDomainNameRegistration = No
DefaultGateway = 193.1.1.1
DHCP = Yes
DHCPClassId = abc
DNSDomain = fabrikam.com
DNSServerSearchOrder = server1.fabrikam.com, fabrikam.com
IPAddress = 193.1.1.33,193.1.1.34
IpAllowedProtocols = 10
NetBIOSOptions = 1
TcpAllowedProtocols = 10
UdpAllowedProtocols = 10
SubnetMask = 193.1.1.255
WINS = Yes
WINSServerList = 193.1.1.95,193.1.1.97
---
And another solution - disable Intel Pro/Wireless 2200BG NIC and integrated Bluetooth and test after this.
to bluescreens
"where does Sysprep come into this?" at final stage, then resealing deployed OS
0 -
May be this text will be helpful for you.
Try to "connect" first page with last or combination of only necessary screens using
<FORM ACTION="screen name"> </FORM>
Good luck B)
0 -
New powertoy from Microsoft!
Current version: Beta 1 (0.0.1.62)
Date: January 24, 2006
The OPK eXtender is a powertoy for the Windows® OEM Preinstallation Kit (OPK) that adds system builder-specific features to the OPK. OPX extends the functionality of the OPK in two ways:
• Automating many of the manual OPK tasks.
• Adding new features designed to meet the needs of system builders.
OPX adds a management layer to the preinstallation infrastructure that you create with the OPK. With the graphical user interface (GUI) of OPX, you can run the most frequently used command-line OPK tools and manage the configuration sets created by the OPK.
You can use OPX to manage all the software resources that you use to build new PCs--Windows SKUs, product keys, out-of-box drivers, Windows updates, your company logos, your support information, and so on. This makes it easier for you to automate the process of building a Windows PC, using either the network-based or CD-based method.
With the OPK and OPX together, you can build new Windows PCs--customized with your branding, support information, extra drivers, and Windows updates--faster than by hand or by using the standard OPK techniques. This lowers your manufacturing costs. By adding your branding and support info, you build a better relationship with your customers by delivering more that just a “whitebox”.
OPX features
OPX adds these new features to the OPK:
• A reinstall CD solution for your customers: This is a solution that restores the PC to the state that you sold it in. Use OPX to create a CD image (.iso) containing the out-of-box drivers for the PC to burn to CD, as well as a Winnt.sif that adds your branding and runs Sysprep. With that CD and a floppy containing the Winnt.sif and some OPX files, your customer can boot the PC with the hologram Windows CD and Winnt.sif and the OPX files will automate the reinstallation of Windows with your customizations. The next release of OPX will add update and applications support to the reinstall solution.
• The “one-off” preinstallation: When you take an order for a single PC, use this method to extend the standard CD-based preinstallation. You can use OPX to build a custom Winnt.sif that adds your branding and support info to the new PC and reseals it with Sysprep. This method works for Windows XP, Windows Server 2003, and Windows versions that require two CDs for installation such as Windows Media Center Edition 2005, Windows XP Tablet PC Edition, and Windows Server 2003 R2 Edition. It also adds F6 support for custom mass-storage drivers, and optional WSUS integration for adding Windows updates.
• Driver scanning of new PCs: The Scan command analyzes the hardware of a new PC and identifies any missing drivers. The results of the scan are listed in a driver enumeration file (.def) and displayed in the DEF tab. You can load that DEF in the OPX install on your technician computer and use it to add the missing drivers to your repository and then to one or more configuration sets.
• A repository of out-of-box drivers: As you build PCs, whenever you add hardware that uses an out-of-box driver you can add that driver to the OPX repository. When you have a repository, you can use OPX to scan a new PC to identify the missing drivers, and automatically update configuration sets to add those drivers from the repository. OPX modifies all answer files for you, including Txtsetup.oem for mass-storage drivers. Then, you run the network-based preinstall using the updated configuration set and Windows is installed with the out-of-box drivers.
• System builder profiles: A profile is the set of information that you use to brand a new PC: your logos, a desktop background, your support info, IE home page, and so on. You can automatically update one or more configuration sets with a profile. If you build PCs for another system builder, you can add their profile to config sets to create PC branded with your partner’s branding.
OPX automates these standard OPK tasks:
• Updating configuration sets to add support for out-of-box drivers: Once you’ve used the Scan command to identify the missing drivers on the new PC, and you’ve added those drivers to the repository, you can use OPX to automatically add those drivers to a configuration set. OPX copies the drivers to the $OEM$ directories and edits the answer files accordingly. This includes mass-storage drivers as well.
• Creating customized Windows PE builds and ISOs: OPX provides a GUI to the Windows PE build tools (Mkimg and Oscdimg) to make it simple for you to create custom Windows PE builds. You can also add drivers from your repository to your Windows PE builds, including mass-storage drivers.
• Creating a UFD that boots with Windows PE: The Server 2003 SP1 OPK added the ability to create bootable USB flash devices (UFD) that can boot Windows PE. If you have the Server 2003 SP1 OPK installed, you can use OPX to create the bootable UFD from your custom Windows PE build.
• Adding Windows Server Update Services (WSUS) integration: If you have a WSUS server, you can automatically use it with your configuration sets or CD-based installations to add Windows Updates to your preinstallation process. OPX configures the Windows Update Agent (WUA) service to access Windows Server Update Services (WSUS) for updates.
• Running the Mkimg, Oscdimg, Drvinst, and Formatufd commands: The OPX GUI makes it easy for you to run these OPK command-line tools without needing to open a command prompt and remember the syntax of each command. Edit fields are available if you need to edit the command-line options.
• Checks answer files for common errors: OPX checks the answer files in a configuration set for common errors such as missing disk configuration, support information or driver signing policy.
Some screensots in attachments...
http://search.microsoft.com/results.aspx?q...n-US&FORM=QBME1]
http://search.microsoft.com/results.aspx?q...n-US&FORM=QBME1
At the end - bad news: now accessible only by Microsoft registred systembuilders
0 -
Excuse me for my English...
This is short guide how to installing MS RIS and deploying WinXP OS w Drivers and additonal software.
Hardware:
Server 1 - AD + DHCP (w2k3std)
Server 2 - RIS (w2k3std)
Test workstations w Intel and Sis MB (wXP prof, wXP Home as Guest OS
LAN - included
AD:
Must exist user w/o Admin privilege, but w right to "Join a computer to the domain"
This right may added via "Domain security policy" -> Local Policy \ User Right Assignment \ Add workstations to domain
Or Active Directory Users and Computers \ "DOMAIN" \ Delegate Control -> Join a computer to the domain.
Or together
DHCP:
1 Scope w Ip range 192.168.0.xx - 192.168.0.xx
Scope options like Proxy, dns, wins, ntp - NOTHING ELSE
INet may say to you - Add option #60, 66, 67 - its not needed for modern NICs w PXE 2.xx boot rom like Intel PRO 100/1000, Marvell, Realtek, Sis LOM
(IMHO
RIS:
Little story
I have E55 Error... something like "PROXY DHCP do not answer" After reading PXE spec. I'm understand what is PROXY DHCP - its RIS binl service. Good name for TFTPD...
In Binlsvc.log found - Sending response to 255.255.255.255 only!!! Of course its nothing to work PXE client show me that it takes IP from DHCP... but RIS is sending reply to all... HM... And I'm stop and disable DHCP service on RIS service (w/o any scope) -- remote boot starts to work.
End of Little story
Nothing intresting in tuning RIS. Adding RIS from Install/Remove, then risetup -add to next images.
2 servers is not necessary, may be one is better, but...
OSC:
laziness - is the main world engine
In RemoteInstall\OSChooser\%LANG%\login.osc
My %LANG is Russian
Lets find strings
 User name: <INPUT NAME="USERNAME" MAXLENGTH=255>
 Password: <INPUT NAME="*PASSWORD" TYPE=PASSWORD
MAXLENGTH=20><BR>
and add
VALUE="USER_NAME_IN_AD_W_PRIV_TO_ADD_NEW_PC_TO_AD"
VALUE="PASSWORD_OF_THIS_USER"
like this:
 User name: <INPUT NAME="USERNAME" MAXLENGTH=255 VALUE="USER_NAME">
 Password: <INPUT NAME="*PASSWORD" TYPE=PASSWORD MAXLENGTH=20 VALUE="PASSWORD"><BR>
it's all my changes in .OSC files
WAR1 - w Intel NICs:
Trying to install wIn from RIS and, of course, Error about Win "don't have necessary network drivers" MS.com says to add drivers to i386 folder and $OEM$\$1\Drivers\Nics and edit Ristndrd.sif w follow:
OemPreinstall=Yes
OemPnPDriversPath = "drivers\nic\ipro100"
But it's NOT work!!!
SPECIAL for MS RIS Intel have SOLUTION! Named (from Intel): "RIS-Specific INF files for use with Intel 10/100 Network Adapters on Windows* XP RIS images."
http://downloadfinder.intel.com/scripts-df...ldID=6761&agr=N
Great - it's WORK
....But not all - new Intel LOM (Lan on MotherBoard) on i915 chipset failed w same Error
Installing wIn from CD and cheking Hardware ID = pci\ven_8086&Dev_1065. Seeking Dev_1065 in downloaded from Intel INF. None
(After dancing around INF file with shaman tambourine... combine SPECIAL INF w ORIGINAL INF for this NIC
Hand made INF ))Nics from SIS, Marvell and Realtek working fine 8-)
WAR2 - w MassStorageDevices:
After 3 days of experiments found 4 points of parsing MassStorageDrivers
1) Textmode setup before copying files
2) Textmode setup after copying files to c:\bla-bla.~LS
3) Before loading GUI setup
4) Loading Installed wIn
Steps
1) In $OEM$ folder creating TEXTMODE folder
2) Copy txtsetup.oem from original driver to Textmode folder
3) Parsing txtsetup.oem (examples from my txtsetup.oem):
[Disks] ;Location of sys, cab, dll & inf files. This section needed for section [Files.xxxxxx]
d1 = "SiS Raid/IDE Driver Diskette", \disk.tag, \
NameOfDisk(any) = "Unused information(any)", PathToTagFile\TagFile(Unused by Setup) , PathToFiles (\ - root of TEXTMODE)
In RIS may be only one "Disk" maped to root of Textmode like
disk = "Textmode MSD",\ ,\ (but not tested)
About points of parsing MSD... On first point (Setup is loading drivers...) setup parser understend folder structure under Textmode!!!!!
May be:
+ Textmode
|--------SisRaid
|--------IntelRaid
and [Disks]
disk1 = "SiS Raid/IDE Driver Diskette", \disk.tag, \SiSRAID\
!!!!!!!!!!!!!!!
Setup load correct driver and possible to manage partions
BUT on Second stage (copying files from c:\bla-bla.~LS to c:\windows) setup stops w error somthing like "sysraid.sys not found -> Retry, Skip" After skipping and rebooting GUI setup will load BSOD
Point 3So... structure of folders in Textmode is impossible :'(
Ok, get back to txtsetup.oem. Next section
[Defaults]
scsi = VMSCSI
This section Seems not important or not used by setup
[scsi]
SISRAID964_181 = "WinXP SiS180 Raid Controller"
VMSCSI = "VMware SCSI Controller Installation Disk"
iaStor = "Intel® 82801ER SATA RAID Controller"
InternalNameForThisSIF = "Discription"
"Discription" MUST BE in ristndrd.sif (i386\Templates) like this
[MassStorageDrivers]
"WinXP SiS180 Raid Controller" = "OEM"
"VMware SCSI Controller Installation Disk" = "OEM"
"Intel® 82801ER SATA RAID Controller" = "OEM"
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"
Next sections
[Files.scsi.SISRAID964_180] ;[Files.scsi.InternalNameForThisSIF(from [sCSI])]
driver = d1,SiSRaid.sys, SISRAID ; SISRAID - name of service must be = name of file
!IMPORTANT START!
catalog= d1,Property.dll
;Original line was DLL= d1,Property.dll, DLL MUST BE RENAMED to "CATALOG" NOT TO INF, as you may read in other web-sites, because setup process rename files w INF predict to "OEMscsXX.inf" and place to \%windir%\OemDir !
03.09.2004 14:40 1 779 oemscs01.inf
30.03.2001 22:58 135 168 oemscs02.inf ; this is not INF!!!! By size
27.09.2004 12:41 8 264 sisraid.cat
03.09.2004 13:43 46 464 SiSRaid.sys
For SiS Raid I'm found error (then dll was renamed) in setupapi.log in \%windir% (not full log)
[2004/10/19 17:40:16 288.1111 Driver Install]
#-019 Searching for hardware ID(s): pci\ven_1039&dev_0180&subsys_810e1043&rev_01,pci\ven_1039&dev_0180&subsys_810e1043,pci\ven_1039&dev_0180&cc_010485,pci\ven_1039&dev_0180&cc_0104
#I022 Found "PCI\VEN_1039&DEV_0180" in C:\WINDOWS\inf\oem0.inf; Device: "SiS 180 RAID Controller"; Driver: "SiS 180 RAID Controller"; Provider: "Silicon Integrated Systems Corp"; Mfg: "Silicon Integrated Systems Corp"; Section name: "SIS180PCI".
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "PCI\VEN_1039&DEV_0180&SUBSYS_810E1043&REV_01\3&267A616A&0&28".
#-167 SPFILENOTIFY_NEEDMEDIA: Tag = "", Description= "SiS 180 Raid Controller Driver Disk", SourcePath = "C:\WINDOWS\OemDir", SourceFile = "property.dll", Flags = 0x00000000.
#E169 SPFILENOTIFY_NEEDMEDIA: returned FILEOP_ABORT. Error 1223: The operation was canceled by the user.
#W187 Install failed, attempting to restore original files.
#I060 Set selected driver.
#-166 Device install function: DIF_INSTALLDEVICE.
#I125 Installing NULL driver for "PCI\VEN_1039&DEV_0180&SUBSYS_810E1043&REV_01\3&267A616A&0&28".
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Installing NULL driver - is really BSOD
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
#I121 Device install of "PCI\VEN_1039&DEV_0180&SUBSYS_810E1043&REV_01\3&267A616A&0&28" finished successfully.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!! finished successfully :DDDDDDDDDDD
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
This is Point 4
!IMPORTANT STOP!
inf = d1,SiSRaid.inf
catalog= d1,sisraid.cat
this sections from original driver w/o changes
[HardwareIds.scsi.SISRAID964_180]
id="PCI\VEN_1039&DEV_0180", "SISRAID"
[Config.SISRAID]
value = parameters\PnpInterface,"5",REG_DWORD,1
All about txtsetup.oem, full listing of my config fliles will be at the end of post
Steps continue:
4) After compiling txtsetup.oem copy all files listed in [Files.xxxxxx] sections to Textmode\
5) In ristndrd.sif (i386\Templates) MUST BE Sections from [sCSI]
"WinXP SiS964 Raid Controller" = "OEM"
"VMware SCSI Controller Installation Disk" = "OEM"
"Intel® 82801ER SATA RAID Controller" = "OEM"
;AND THIS (below)
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"
Another intresting thing... In ristndrd.sif section [OEMBootFiles] is EMPTY (but exist)! I'm not list files from Textmode to this section and all working fine!!!!!!!!
Tip. All errors during setup w MassStorageDrivers like error in bla-bla.c file string XXXX BECAUSE txtsetup.oem is BAD. Write it carefully!!!
Deploy process:
Client from PXE install OS
At the end of Install run sysprep -factory -quiet - reboot
Factory copy from network share needed files; pnp drivers, Mui, other...
Factory install pnp drivers
Starting reseal
At the end of reseal installing MUI, reg tweaks, OEM logos
Directory structure:
RIS Server\D\
+OEM
|--Drivers -> Then copy drivers via Factory paths !!automatically!! added to HKLM \ SOFTWARE \ Microsoft \ Windows \ CurrentVersion \ DevicePath
|----- 00_addons
|----- 01_chipset
|----- 02_Video
|----- ......
|-- Mui
|-- Mui2k3
|-- OEM -> My .cmd files; oeminfo.ini, oemlogo.bmp and other
|-- Storage -> For 2k3 server raid drivers
+RemoteInstall
|-- Admin
|----- NicI386 - collection of files, to add in I386 folder for new Image
|----- TextMode - MSD
|--Setup\Russian\Images\XPC.SP2
|----- $OEM$
|--------$1
|----------- Drivers
|-------------- Nic -> For Factory work
|----------- Sysprep
|-------------- factory.exe
|-------------- netcfg.exe
|-------------- setupcl.exe
|-------------- sysprep.exe
|-------------- sysprep.inf
|-------------- winbom.ini
|-------- Textmode
|----- i386
LISTINGs
-------------
ristndrd.sif
-------------
[Data]
AutoPartition="0" ;Setup don't auto create partitions
MsDosInitiated="1"
UnattendedInstall="Yes"
floppyless="1"
OriSrc="\\%SERVERNAME%\RemInst\%INSTALLPATH%"
OriTyp="4"
LocalSourceOnCD=1
[setupData]
OsLoadOptions="/noguiboot /fastdetect"
SetupSourceDevice = "\Device\LanmanRedirector\%SERVERNAME%\RemInst\%INSTALLPATH%"
[GuiUnattended]
AdminPassword=*
AutoLogon=Yes
AutoLogonCount=99
OEMSkipRegional=1
OEMSkipWelcome=1
TimeZone=201
[unattended]
AutoActivate=No
CrashDumpSetting=0
DriverSigningPolicy=Ignore
UpdateInstalledDrivers=Yes
FactoryMode=No
FileSystem=LeaveAlone
Repartition=No ;Setup don't auto create partitions
OemPreinstall=Yes
OemPnPDriversPath = "drivers\nic\D-Link\500sx;drivers\nic\D-Link\500T;drivers\nic\D-Link\530;............."
OemSkipEula=Yes
TargetPath=\windows
UnattendMode=FullUnattended
UnattendSwitch=Yes
WaitForReboot=No
OverwriteOemFilesOnUpgrade=No
InstallFilesPath = "\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%"
LegacyNIC = 1
[Display]
BitsPerPel=32
Xresolution=1024
YResolution=768
VRefresh = 60
[PCHealth]
ER_Display_UI=0
ER_Enable_Applications=None
ER_Enable_Kernel_Errors=1
ER_Enable_Reporting=0
ER_Enable_Windows_Components=1
ER_Force_Queue_Mode=0
ER_Include_MSApps=0
ER_Include_Shutdown_Errs=0
RA_AllowFullControl=1
RA_AllowToGetHelp=1
RA_AllowUnsolicited=1
RA_MaxTicketExpiry=28800
[RegionalSettings]
Language = 0419
LanguageGroup=5,1
SystemLocale=00000419
UserLocale=00000419
UserLocale_DefaultUser = 00000419
InputLocale=0409:00000409, 0419:00000419
InputLocale_DefaultUser=0409:00000409
[shell]
DefaultStartPanelOff=No
DefaultThemesOff=Yes
[TapiLocation]
CountryCode=7
Dialing=Pulse
AreaCode=3812
LongDistanceAccess="0"
[TerminalServices]
AllowConnections=1
[userData]
ProductKey=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
FullName="OEM"
OrgName="BTG-OEM"
ComputerName=*
Repartition=No ;Setup don't auto create partitions
UseWholeDisk=No ;Setup don't auto create partitions
Profiles = WindowsFirewall.TurnOffFirewall
[WindowsFirewall.TurnOffFirewall]
Command1="c:\sysprep\sysprep -factory -quiet -reboot"
"WinXP SiS964 Raid Controller" = "OEM"
"WinXP SiS180 Raid Controller" = "OEM"
"VMware SCSI Controller Installation Disk" = "OEM"
"Intel® 82801ER SATA RAID Controller" = "OEM"
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"
Description ="XP Prof Corp SP2"
Help ="MSD: VmWare BUSLogic, SiS: 964_180,964_181,965, iNTEL: 82801ER SATA Raid"
LaunchFile = "%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com"
AutoDetectNetwork = Yes 'If you have error 1231 in winbom.log this line must BE
FactoryComputerName = * 'If you have error 1231 in winbom.log this line must BE
RebootAfterComputerName = Yes 'If you have error 1231 in winbom.log this line must BE
ResealFlags = -activated -nosidgen
Logfile = c:\windows\factory.log
\\RISserver\oem\drivers = PnPDrv
OEMBrandIcon = %WINDIR%\Oem\btgSM.ico
OEMBrandLink = "http://www.btg.ru/"
OEMBrandLinkInfoTip = "Just Tip
"OEMBrandLinkText = "It'll be in Start menu"
UserLocale_DefaultUser = 00000419
InputLocale=0409:00000409, 0419:00000419
InputLocale_DefaultUser=0409:00000409
ProductKey = "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
Command1="c:\windows\oem\mui.cmd"
Command2="c:\windows\oem\factory.cmd"
Command3="c:\windows\oem\all.cmd"
d1 = "SiS Raid/IDE Driver Diskette", \disk.tag, \
d2 = "SiS Raid/IDE Driver Diskette", \disk.tag, \
d3 = "VMware SCSI Controller Installation Disk", \disk.tag, \
d4 = "Intel Application Accelerator driver", \disk.tag, \
SISRAID964_180 = "WinXP SiS964 Raid Controller"
SISRAID964_181 = "WinXP SiS180 Raid Controller"
VMSCSI = "VMware SCSI Controller Installation Disk"
iaStor = "Intel® 82801ER SATA RAID Controller"
;;;;;;;;;;;;;;;;;;;;;;;;;;;SiS 181;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
driver = d1,SiSRaid.sys, SISRAID
[HardwareIds.scsi.SISRAID964_180]
id="PCI\VEN_1039&DEV_0180", "SISRAID"
value = parameters\PnpInterface,"5",REG_DWORD,1
;;;;;;;;;;;;;;;;;;;;;;;;;;;SiS 181;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
driver = d2,SiSRaid1.sys, SiSRaid1
[HardwareIds.scsi.SISRAID964_181]
id="PCI\VEN_1039&DEV_0181", "SiSRaid1"
value = parameters\PnpInterface,"5",REG_DWORD,1
;;;;;;;;;;;;;;;;;;;;;;;;; VMWARE ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
driver = d3, vmscsi.sys, VMSCSI
value = Parameters\PnpInterface, 5 ,REG_DWORD, 1
value = Parameters\Device, NumberOfRequests, REG_DWORD, 128
id = "PCI\VEN_104B&DEV_1040", "VMscsi"
;;;;;;;;;;;;;;;;;;;;;;;;;;; 82801ER ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
driver = d4, iaStor.sys, iaStor
value = "", tag, REG_DWORD, 1b
value = "", ErrorControl, REG_DWORD, 1
value = "", Group, REG_SZ, "SCSI miniport"
value = "", Start, REG_DWORD, 0
value = "", Type, REG_DWORD, 1
id = "PCI\VEN_8086&DEV_24DF&CC_0104","iaStor"
P.S. Special thanks to Michael Waterman for RebootAfterComputerName = Yes
0 -
Special INF files for Intel NICs and RIS
e1000325.exe
e100b325.exe
through http://downloadfinder.intel.com/
or
0
....
2k Server RIS, XP and SATA Driver - Help needed.
in Unattended RIS Installation
Posted · Edited by dk_
try to change in txtsetup.oem:
disk1 = "Silicon Image SiI 3x12 SATARaid Driver Installation Disk",\txtsetup.sif,""
to
disk1 = "Silicon Image SiI 3x12 SATARaid Driver Installation Disk", \si3112r.sys, \
May be something helpful find here
http://www.msfn.org/board/index.php?showtopic=30890
(if you have BSOD - remove HDD and connect to another PC and see files listed below)
MSD files copied from RIS server here: C:\windows\oemdir\
"BSOD"
can be finded here: c:\windows\setupapi.log