baudchaser

Bashrat, I haven't tried that yet, but was able to get it working....without SP2 at least. Here is a recap of what I did to a plain Windows XP VLK CD to get it working: 1. Added to $OEM$\$1\Drivers\00_SATA: txtsetup.oem sisraid.sys sisraid.cat sisraid.inf property.dll 2. Added to i386 directory: sisraid.sys property.dll 3. Added to $OEM$\$$\System32: property.dll 4. Added to Winnt.sif: [Unattended] OemPreinstall=Yes OemPnPDriversPath="Drivers\00_SATA" DriverSigningPolicy=Ignore 5. Added to txtsetup.sif: [SourceDisksFiles] sisraid.sys = 1,,,,,,4_,4,1,,,1,4 property.dll = 1,,,,,,4_,2,0,0,,1,2 [HardwareIdsDatabase] PCI\VEN_1039&DEV_0180 = "SiSRaid" [scsi.load] sisraid = sisraid.sys,4 [scsi] sisraid = "WinXP SiS Raid/IDE Controller" This worked, no BSOD after the first reboot. 6. Slipstreamed SP2 -> "Setup did not find any hard disk drives installed in your computer." I just tested this again to verify, and yes, the only change was slipstreaming SP2. ***Edit: Duh, I just realized that the txtsetup.sif was overwritten during the slipstream. So obvious! Going to go back and try again.... I was also able to get it working w/o modifying the txtsetup.sif file, by adding the [MassStorageDrivers] and [OEMBootFiles] sections to the winnt.sif file method. I don't remember if I was able to get this working with SP2, and am about to try again. My ultimate goal is to be able to integrate the SATA driver into a multiboot CD which has both an OEM and VLK version of Windows XP for use at work. I was not able to get this working via the winnt.sif only method, and am going to go back and see if SP2 had anything to do with it...

htc, I had actually already tried integrating property.dll in the system32 dir per your post, but was still getting the bsod. I'll go back and try again to confirm.

jbm, thanks for the suggestion, but no go. I'm curious to see if anybody else has been able to successfully integrate the SiS 180 SATA driver. I've gone over several guides and can not find what I am doing wrong. I've verified the driver does work by installing it manually, and it gets past text mode phase of setup.

I'm trying to integrate sisraid.sys (SiS SATA driver) into a plain Windows XP VLK cd. The following files have been added to $OEM$\$1\Drivers\00_SATA: txtsetup.oem sisraid.sys sisraid.cat sisraid.inf property.dll The following has been added to the WINNT.SIF file: [Unattended] OemPreinstall=Yes OemPnPDriversPath="Drivers\00_SATA" DriverSigningPolicy=Ignore The following is the contents of the TXTSETUP.OEM file: [Disks] d1 = "SiS Raid/IDE Driver Diskette", \SISRAID, \ d3 = "SiS Raid/IDE Driver Diskette", \SISRAID, \RAID\WIN2000 d4 = "SiS Raid/IDE Driver Diskette", \SISRAID, \RAID\WINXP [Defaults] scsi = SISRAID_XP [scsi] SISRAID_XP = "WinXP SiS Raid/IDE Controller" SISRAID_2000 = "Win2000 SiS Raid/IDE Controller" [Files.scsi.SISRAID_XP] driver = d4, SiSRaid.sys, SiSRaid dll = d4, Property.dll inf = d4, SiSRaid.inf catalog= d4, sisraid.cat [HardwareIds.scsi.SISRAID_XP] id="PCI\VEN_1039&DEV_0180", "SiSRaid" [Files.scsi.SISRAID_2000] driver = d3, SiSRaid.sys, SiSRaid dll = d3, Property.dll inf = d3, SiSRaid.inf catalog= d3, sisraid.cat [HardwareIds.scsi.SISRAID_2000] id="PCI\VEN_1039&DEV_0180", "SiSRaid" [Config.SiSRaid] value = parameters\PnpInterface,"5",REG_DWORD,1 The following is being added to the end of the TXTSETUP.SIF file before the EOF marker: [SourceDisksFiles] SISRAID.SYS = 1,,,,,,3_,4,1 [HardwareIdsDatabase] PCI\VEN_1039&DEV_0180 = "SISRAID_XP" [SCSI.load] SISRAID_XP = SISRAID.SYS,4 [scsi] SISRAID_XP = "WinXP SiS Raid/IDE Controller" The sisraid.sys file is being cabbed to sisraid.sy_ and added to the i386 directory. The driver is initially detected as setup is able to complete text mode phase of setup where the files are copied to the hard drive. The machine then reboots, the Windows XP splash screen appears, and then I get a BSOD Stop error 0x0000007B. Looking for any ideas you are able to offer.

I was getting the add hardware wizard for a video driver in the middle of an unattended cd. I had the right driver, winnt.sif was correct, etc. In fact, my unattended cd includes drivers for several machines the company uses, and only one model seemed to do this. It looked like setup was continuuing in the background, so I just didn't touch anything. Sure enough, setup continued, the add hardware wizard went away, and at the end of setup the machine did indeed have the right driver. So, have you just tried waiting it out? I did the same thing you did several times, and clicked through the wizard, but it proved to be unneccessary in my case.

I'm having a problem setting Wallpaper and Background Color through an unattended setup. What I want to do is have the company logo displayed in the middle of the screen, with a specific background color around it, for BOTH the desktop AND logon screen....4 separate registry entries, I believe. When I import the following keys after setup (already logged into windows), I get the desired results, but the HKCU entries are, of course, only applied to that logged in user. I have read that installing an HKCU entry during the cmdlines.txt portion of setup will import the key to the default profile, but that does not seem to be working. What is happening when I run the code in cmdlines.txt is: 1. I get the logon screen background color, but not the wallpaper 2. I get the desktop wallpaper, but not the background color. ;VERIFIED - Set the Logon Screen Background Color [HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "Background"="R128 G171 B213" ;did not work during install - Set the Logon Screen Wallpaper [HKEY_USERS\.DEFAULT\Control Panel\Desktop] "Wallpaper"="C:\\Windows\\Web\\Wallpaper\\Wallpaper.bmp" ;did not work during install - Set Desktop Background Color [HKCU\Control Panel\Colors] "Background"="R128 G171 B213" ;VERIFIED - Set the Wallpaper [HKCU\Control Panel\Desktop] "Wallpaper"="C:\\WINDOWS\\web\\wallpaper\\Wallpaper.bmp" Any ideas from anyone? I don't want to use themes, b/c I can't trust Active Desktop's stability in a production environment, and I don't want to simply have the wallpaper stretch across the entire screen, b/c it looks like crap. I would really like to figure out how to accomplish this through the registry. If I had to, I could re-apply the Logon screen wallpaper and background color after setup, b/c neither involves an HKCU key, so the most critical thing to figure out is how to set the background color for the Default user...

From the Microsoft site: In Microsoft Windows XP, the maximum length of the OEMPnpDriversPath value is 4,096 characters. This limit applies to both unattended Setup and the Sysprep tool. When you use Winnt.exe, the OEMPnpDriversPath value is limited to 1,024 characters. On your CD, create a 'Drivers' folder under '$OEM$\$1\'. In 'Drivers', you can have multiple folders for Chipset, Video, etc, and then break those folders up into Manufacturers. It's actually described in depth here on this site: http://unattended.msfn.org/xp/drivers.htm I highly recommend reading through that guide, as it offers some really good suggestions, such as placing numbers in front of each folder so that setup will install certain drivers (such as chipset drivers) first (i.e. 000_Chipset, 001_Video, 002_Audio, etc.). Your WINNT.SIF will look something like this: OemPnPDriversPath="Drivers\000_Chipset\Intel;Drivers\000_Chipset\nVIDIA;Drivers\001_Video\ATI;Drivers\001_Video\nVIDIA;Drivers\002_Audio\Sigmatel" DriverSigningPolicy=Ignore