Glowy

Uhm I don't want to be a smartass or something But why not copy the files and add registry keys to associate te filetypes. than you have no problems when a new version of winamp comes out (happens quite often) And since Winamp uses an INI file to store all it's settings you can customize your settings and copy it with your install Here's what I did: Made an install of Winamp on a PC copied the files that were changed into the $Progs dir on the unattended CD and imported the changed registry. It also copys some px....dll files into the system32 dir these can be put into the $1\system32 dir. I used WininstallLE to see wich files whent where and what registry values were changed. Winamp503.REG

Hi boeur, Are you trying to make bootdisks (floppy) or are you making a Windows CD ? When creating a CD, maybe Greenmachine's site will help. here's the topic about SATA drivers: http://greenmachine.msfnhosting.com/READING/addraid.htm hope this helps.

After using the forum for a long time, I thought maybe it's time to do some posting myself and (maybe) help some people out. about me and unattended I've been using Greenmachine's XPCreate http://greenmachine.msfnhosting.com/XPCREATE/ in combination with Xplode http://xplode.voidfx.com/ creating my unattended CD an it's nearly finished. And using the MSFN unattended guide I managed to throw in some apps too

lallius Sure are some Nice tweaks. maybe it's better to use %SystemDrive% or %SystemRoot% when adding direct file links. I've been Using Greenmachines XPCreate http://greenmachine.msfnhosting.com/XPCREATE/ in combination with Xplode http://xplode.voidfx.com/ and when I used direct file links instead of variables I got problems when installing on another drive than C