On Tue, Nov 27, 2007 at 06:13:51PM +1100, paul kelly wrote: > Hi - I am about to try out this driver pack method also. > However with all the traffic on the subject I've become confused on best > approach. > Can any one who understands this better give me a condensed (simple) version > of how best to implement ... apologies I'm fairly new to much of this :)
Steps 1: 1. Download all driverpack files. 2. Run the program and give it the directory, I will assume z:\os\winxpsp2. Use method 2. Method 1 is cleaner but won't work (at least not for all drivers). This directory should contain the i386 directory from a clean copy of the Windows CD. The process must have write permissions. 3. Ensure z:\os\winxpsp2\OEM (created in above step) is copied to c:\OEM during installation. Apparently this can be done by copying/moving to i386\$oem$\$1\OEM (not tested personally). 4. I had do some additional black magic to get it to work. In particular, I had to copy presetup.cmd and setuporg.exe from z:\os\winxpsp2\i386 to z:\os\winxpsp2\i386\$OEM$\$$\System32, and delete the entries for these files in z:\os\winxpsp2\txtsetup.sif 5. Apparently on startup, by default, it will ask you if you want to add the OEM directory (and directories under it) to OemPnPDriverPath; say no. Step 4 is ugly. Solutions welcome! -- Brian May <[EMAIL PROTECTED]> ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
