jbm

Just make a .reg file and place it in the same directory where cmdlines.txt is and call it from cmdlines.txt like this. [COMMAND] "REGEDIT /S preferences.reg" Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Control Panel\Desktop] "UserPreferencesMask"=hex:9e,1e,07,80

If the program really doesn't have silent switches you could create a second runonceex.cmd file, (name it runonceex2.cmd for example) that installs that program and call it at the end of your first one.

The best way I've found is to set quick launch how you want it then save the key that 2forza showed you in a reg file. And Import that during the install.

You canjust paste it all on the end of the txtsetup.sif

I believe so. but don't shoot me if it doesn't.

Try this "nero-6.6.0.14.exe /SILENT /NOREBOOT /SN=XXXX-XXXX-XXXX-XXXX-XXXX-XXXX /WRITE_SN" you don't need to install version 6.0.0.0 just install 6.6.0.14 If that doesn't work try this reg file. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Ahead] [HKEY_LOCAL_MACHINE\SOFTWARE\Ahead\Nero - Burning Rom] [HKEY_LOCAL_MACHINE\SOFTWARE\Ahead\Nero - Burning Rom\Info] "User"="Name" "Company"="Org" "Serial6"="xxxx-xxxx-xxxx-xxxx-xxxx-xxxx"

If you set oempreinstall to no then it ignores the oempnpdriverspath and it will not copy anything in your $oem$ folder to the hard drive. It will still run your cmdlines.txt just place your regtweak files in the same place your have your cmdlines.txt. Installing drivers and apps is another thing. Theres other posts about installing apps from cd, as far as drivers this is what I came up with and it seems to work for me but there is no guarantee I got the ideas for these procedures from reading many posts and guides on www.msfn.org So thanks to everyone there. To be able to use to set OemPreinstall = No and still use OemPnPDriversPath and F6. And Cmdlines.txt still works. step 1 Make a self extracting file of your driver directory that you use in PNPDRIVERSPATH. We'll call it drivers.exe. set it to extract in the current folder with no prompting. Should create a folder .\DRIVERS Step 2 copy the file you just created to AMD64 directory in your CD/DVD source. Step 3 Add the following to your winnt.sif file [unattended] DetachedProgram="%windir%\drivers.exe" step 4 Edit txtsetup.sif [sourceDisksFiles] bootvid.dll = 1,,,,,,3_,2,0,0,,1,2 drivers.exe = 1,,,,,,3_,1,0,0,,1,2 <-add this line. this copies drivers.exe to the /windows directory during textmode install. step 5 Edit HIVESFT.INF and HIVESFT32.INF and add edit the device path. Search for DevicePath in each file. My path I use is HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion","DevicePath",0x00020002,"%SystemRoot%\inf;%systemroot%\DRIVERS\CHIPSET\NFORCE\SMBus;%systemroot%\DRIVERS\CHIPSET\NFORCE\GART;%systemroot%\DRIVERS\LAN\nforce;%systemroot%\DRIVERS\GRAPHICS\nvidia;%systemroot%\DRIVERS\SOUND\AUDIGY2;%systemroot%\DRIVERS\SOUND\nforce;%systemroot%\DRIVERS\SOUND\ALC850;%systemroot%\DRIVERS\STORAGE" After the %systemroot%\inf; is the samething you would have put in OEMPNPDRIVERSPATH in you winnt.sif Step 6 Make your CD/DVD

You won't see anything like that in your txtsetup.oem. Just take the name of your driver and replace the fasttx2k with the name of your driver so it becomes mydriver.sys = 1,,,,,,3_,4,1,,,1,4 mydriver.inf = 1,,,,,,,20,0,0 Where mydriver is the actual name. You should end up with something like this I just realised your tr [SourceDisksFiles] viaxbus.sys = 1,,,,,,3_,4,1,,,1,4 viaxport.sys = 1,,,,,,3_,4,1,,,1,4 viaxraid.sys = 1,,,,,,3_,4,1,,,1,4 [HardwareIdsDatabase] PCI\VEN_1106&DEV_3149 = "viaxbus" PCI\VEN_1106&DEV_3249 = "viaxbus" RAID_Virtual_Channel = "viaxraid" [SCSI.load] viaxbus = viaxbus.sys,4 viaxport = viaxport.sys,4 viaxraid = viaxraid.sys,4 [SCSI] viaxbus = Via smartx Bus driver" viaxport = "Via Smartx Port driver" viaxraid = "VIA Smartx Raid driver" Don't forget to edit your winnt.sif and add the oempnpdriverpath and to copy the files to that directory and to your i386 directory. I just realised your tying to integrate your driver into XP64, right? If you are its more complicated than for 32bit XP. The only way I've been able to get it to work is to follow the steps in these posts. http://www.msfn.org/board/index.php?showtopic=47053 but there's no guarantee it will work. It didn't work on my nforce3 raid drivers, but did on my promise and silicon image.

This is the method I use http://greenmachine.msfnhosting.com/READING/addraid.htm To figure out whats needed for your own drivers look in it's txtsetup.oem file. Here's an example [SCSI] Si3114r_AMD64 = "Silicon Image SiI3114R Controller (AMD64 or EM64T)" ;The above line goes under the [SCSI] section of txtsetup.sif [HardwareIds.SCSI.Si3114r_AMD64] id = "PCI\VEN_1095&DEV_3114&SUBSYS_61141095", "si3114r" id = "PCI\VEN_1095&DEV_3114&SUBSYS_288510F1", "si3114r" id = "PCI\VEN_1095&DEV_3114&SUBSYS_81361043", "si3114r" ;The lines above would go under [HardwareIdsDatabase]. But you need to change them to the form. PCI\VEN_1095&DEV_3114&SUBSYS_61141095 = "si3114r" I'm not familiar with the use of the driverpack so I can't help you there. But I think you would get a better response if you asked a more specific question. Like I've done such and such but it didn't work as it said it would. Or I don't under stand this step.

First read the guide. The part your looking for is under intermediate/device drivers/sata/raid. Then search the forum, you'll find lots of posts on the subject. Have you done any searching at all?

Yes

Drivers do have to be 64bit. I've been able to integrate most drivers to the CD using this method. http://www.msfn.org/board/index.php?showtopic=47053 The only one that didn't work is nforce3 raid. The winnt.sif goes in the AMD64 folder.

No. At first it will appear to because you'll be asked to choose the drivers on the floppy. But later in the install setup wont be able to find them.

just add this line to the end of your runonceex cmd file. rundll32.exe iernonce.dll,RunOnceExProcess This will run the installs as the cmd file runs. If you have some programs you need to install after you logon place them after the above line.

With 2 32bit cores you still couldn't run 64bit OS's or programs. But a multi threaded 32bit app would run faster on the dual core cpu. But aren't the new Intel dual core (Pentium D) processors 64bit capable? Regardless my next upgrade will probably be a AMD64 X2.

place it in your $oem$ directory with cmdlines.txt and call it in your cmdlines.txt like this. [COMMANDS] "useraccounts.cmd"

If I made a 32bit XP install CD, except I used ntldr and ntdetect.com from my XP64 CD. Would I be able to install XP32 bit to another drive and not have to copy these files afterwards to beable to boot my XP64 install. Or would I have trouble installing 32bit XP after doing this? I'm thinking if these files contain 64bit code it wouldn't work. Tried it,it works

I have an Sound blaster audigy but it should be about the same. If your installing under XP delete all the folders for other OS's copy everything in the first win2k_xp directory to your cd. there's another win2k_xp directory under this. so for my audigy I have. SOUND ..AUDIGY2 ...COMMON ...LANG ...WIN2K_XP The drivers will be installed, but you will have to figure another way to install the extra programs.

Glad you got it working Here's what I use in my winnt.sif for display [Display] BitsPerPel=32 Xresolution=1280 YResolution=1024 Vrefresh=60 Can't help you with OOBEINFO but I use a bat file to create accounts and to set autologon cmdow @ /HID @ECHO OFF net accounts /MAXPWAGE:UNLIMITED net user Jim password /add net localgroup Administrators Jim /add REG ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v "DefaultUserName" /t REG_SZ /d "Jim" /f REG ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v "DefaultPassword" /t REG_SZ /d "password" /f REG ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v "AutoAdminLogon" /t REG_SZ /d "1" /f EXIT

16: http://support.microsoft.com/default.aspx?...kb;en-us;312535

If your're not try checking close disk option

Your winnt.sif isn't named winnt.sif.txt is it?

start regedit then highlight Hkey_local_machine, then on file menu click on load hive. Type a name for the key and the hiv file will be loaded under that key.

If windows has drivers for your controller, then you'll have no problems. Otherwise you'll have use the F6 method or add them to your CD.

It's also easier to copy and paste when yo want to create a new file.