Druide

i found it easier to install the drivers of whatever you need for your machine(s) and then use something like 'driver genius professional edition' which has features like making cabs, autoinstall multiple drivers at once whithout rebooting if you use a .vbs script or autoit. Another option is just to select to backup the SB audigy drivers and to place them into your $$\system32\.... and a copy of you .inf in the $$\inf\.. directory (create it if you havent already) There are multiple options if you use your imagination, to switch a cd/dvd only to install the drivers for your hardware makes the unattended installation far from unattended, just copy those drivers to their place in system32 or create $$\system32\drivers\.. (and put all the drivers you need inthere) while installing you just choose select the location to install the drivers (dont let it search bacause it will take forever with multiple hardware drivers installation) when you put the inf files of your drivers in the $$\inf\.. directory then you only have to point it to the $$\system32\drivers\SBAudigy\ (or so) sbaudigy drivers are only 4.7 mb so why switching disks ?

Hi this is my first post here... After lots of reading and stuff, i started my own unattended winXP SP2 DVD's but i noticed that working with the WPI interface some programs did not got installed due to a setup.exe that already is processing and that causes errors in the final result of your installation. After 10 minutes of searching i found a great tool to make it all install without any double checking after timing the install of each software that was missing. You need to use the command SLEEP for 180 that means wait 180 seconds = 3 minutes before you execute the next line that made all the difference in the world for me, and use the command SLEEP /? in your command window ( cmd.exe in RUN) to see what this fine tool can do for you, it's small but capable to keep my hair color the way it is and not grey SLEEP — Batch util sleeps until event occurrence. * * * * * [added 1998-03-21, updated 2005-04-10] A very flexible command line tool for scheduling events; intended for batch files. From the docs: The possible events are: FOR a length of time, TILL a certain time, a question ASKed of the user, certain FILESPECS appear or disappear, the UPS is active, or a SCHEDuled event. Commands can be combined. Sleep is DOS, DesqView (uses DV System Memory), OS/2, and Windows aware. Sleep will accept an indirect command file. Multiple lines can be used and command files can be nested. The resulting command line must be under 16K. Sleep takes up to 100 filespecs, with paths and wildcards. Sleep will exit when any of these filespecs is created (+) or deleted (-). If also prefixed by "&", the conditions for those filespecs are ANDed rather than ORed. Serial and parallel port monitoring: Sleep outputs a byte to the port's control register, then monitors the port's status register, looking for the presence (+) or absence (-) of a bit or bits. Scheduled events can stored in a file which contains one line per event. Sleep returns the error level of an event when it occurs. Sleep can also be called to return an error level based on the date or time. The cursor keys can be used to modify time remaining. Usage: INDIRECT COMMAND FILE.Sleep "@"<file> FOR syntax............Sleep for [[hh":"]mm":"]ss TILL syntax...........Sleep till [[hh":"]mm":"]ss ASK syntax............Sleep ask '<prompt string>' <responses> FILESPECS syntax......Sleep ["&"]"+"|"-"<filespec> ... PAR and SER syntax....Sleep par|ser <port adr> <out> "+"<in> "-"<in> SCHED syntax..........Sleep sched <file> No documentation - type SLEEP /? for extended help screens. Author: John R. Souvestre (1997). Sleep direct download click here Unpack it and copy/move it to $OEM$\$$\System32\ Tested on WinXP Pro SP2 Note this is a different tool then the one on this page They are not the same I want to thank everyone involved here for their great help/answers that we all can find at msfn.org TWO thumbs UP SLEEP.EXE