Søndag 25 november 2007 23:03, skrev Brian May: > On Fri, 2007-11-23 at 11:27 +0100, Nils Olav Fossum wrote: > > Onsdag 14 november 2007 17:08, skrev Maurice Libes: > > > i make this copy in the UNATTEND.TXT file here: > > > doit_cmds = "Z:;cd Z:\os\winxpsp2\i386;xcopy OEM c:\OEM /Y /E /I;
so if I get this right: Drivers are copied to c:\oem and Windows pick them up and uses them? > > hm, I wonder if this is just a documentation problem, and what we can do > > better.. > > ..Im starting a new thread.. > > If you started a new thread, I apologise, as I must have missed it. hehe, I tried to, but the message is a bit unclear, my bad. see 'Driver install fuzz'. Im trying to get more info to make documentation and I hope to automate the driver install process a bit more, if needed. But, Im not the best doc writer, or in other words: I can do it much better in Norwegian :-) > > Anyway, hard coding the above is kind of ugly, especially as the os > directory is hard coded ( z:\os\winxpsp2 ) - which might be OK if you > have only one OS, but probably won't work if you have multiple OS in > z:\os. Yep, this should be automated, and I believe it is already done, but a little handwork is needed: make a sensible directory structure under z:\os\winxpsp2\$oem$\$1 Lets say you have a HP dc 5750, create a directory 'hpdc5750' In this directory you put the drivers needed for this machine. And nothing more. file name crashes are rare. ATI/AMD, Intel, Broadcom and Realtek all have drivers for download you can use. So has HP, Dell, FujitsuSiemens, IBM, Lenovo ++ I use a combination of drivers from chipmakers and computermakers. Yes, this is a little more work, but the upside is controll over youre drivers. > > Maybe if you have a setting that gives a list of commands to execute > before doit_cmds - that way you wouldn't have to hard code the winnt > command either... But the list of commands to execute could vary > depending on the OS you want installed - e.g. if you want a copy of > winxp with and without the driver packs for some reason. > > In fact I almost did just this myself, but fortunately woke up to the > problem with unattend.cmd before I got myself too confused. Actually, Im trying to get away from the windows-installer, ie: the whole dosemu thing. I will post more in -devel soon. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
