what do you mean by idle-mode? does that mean that if I inclue extracting the 7zip archive using Run.Wait it will idle at DetachedProgram?

Also, why the need to input the cd when using this method for any devices that were not connected during install...is it because of a registry setting? Im just asking if it is something we can change because I copy the driver directory from the cd to hard drive just for the purpose of not needing the cd again.

This post has been edited by evilvoice: Aug 13 2005, 03:17 AM

Different write up for the script.



Not sure if the ProcessWait is really needed tho...then again haven't tested this method yet ether.

If you want all drivers get installed from HDD you have only to modify the SetupCopyOEMInf.exe command line.

For example you want the Drivers to be located in \Windows\Drivers you can use this code:

driver.au3

Where in $oem$\$$\System32:


Following files in $oem$


And in $oem$\$$\drivers your driver files

This post has been edited by hp38guser: Aug 13 2005, 09:29 AM

so why the need for a06lp's last note in the first post? I assumed it was something else, like a registry problem, or something, but if using setupcopyoeminf.exe on the windows\source\drivers dir will make it so windows does not prompt for the cd when installing NEW devices, then Ill use that method, just thought it was more in depth.

still havent tried it out yet, but i do think this should be stickied or merged...or something to keep it at the top...a bunch of people say this method works better than the previous version...so maybe the old should be replaced with the new?

Just thought I'd point something out...

The OTHER Drivers-from-CD method didn't work with RyanVM's Update Packs.

However, this method, as outlined in the first post, is tested, and WORKS, with v1.3.1 of his pack. Enjoy!

Does this method work for Windows 2000 Pro? I tried to follow instructions on the first page, change only one thing in Drivers.au3: win51ip.SP2 to cdrom_ip.5. But it didn't work for me.

In old method there is a possibility to compress drivers, place them on CD and then uncompress from CD to the system drive installing from there. Is it possible in new method? Sorry I'm not familiar with AutoIt.

Regards,
Oleg 2

Great work, all of you

Will now test if this works from USB drives as well, by means of the DriveGetDrive("ALL") instruction.

Also, Bashrat, why don't you make this one a sticky and "un-sticky" the "Unlimited number of drivers + keeping the drivers." thread since that one is outdated.

This post has been edited by Afterdawn: Sep 5 2005, 01:15 PM

Yes yes it works like a charm! Now I've got all my applications / hotfixes, tweaks ánd all my drivers on my 2GB USB flashdrive! Only when a new Service Pack is released I will need to update my CD!

Thanks to all of you!

Here is my modified auto-it script file btw:

Note that there are a few things different here:
- All used drive letters will be searched for a directory called \drivers
- It assumes that WatchDriverSigningPolicy.exe and SetupCopyOEMInf.exe are in this directory
- These two files are not deleted, only the auto-it script file (which in my case is called t39.au3 in the Windows directory)

One more thing: When you're installing Windows XP and you are at the partitioning part of the Setup (the only part which isn't unattended in my case), you should be able to see your flashdrive already. This way you can check whether it shall be accessible at the t-39 minute stage. The used filesystem (FAT or NTFS) isn't of any importance.

This post has been edited by Afterdawn: Sep 6 2005, 08:25 AM

glad to hear it works.

one of the great things about the autoit aspect of this method is that its so customizable.

enjoy!

Thanks for your own version of the script. It's more versatile to search for drivers in a directory in ALL used drive letters rather than specifing CDROM or FIXED.

This post has been edited by Bilou_Gateux: Sep 24 2005, 03:26 AM

I'm having a problem where SetupCopyOEMInf.exe does not finish running before Setup starts driver detection. It gets about halfway through and then detection kicks in during integration. It still finishes, but I don't know if I'm losing a few drivers or not. Is there something I can do about this?

Ive actually thought about this (may be why I havent tested it out yet) but I was looking into 7zipping all the files and extracting them and running the commands, but the problem would be if setup starts before it finishes.

Thnx for providimg this nice guide and to all for their inputs.. I am going to make UXPCD withthis methods. I am compressing drivers using this method (http://www.msfn.org/board/index.php?showtopic=35869) , I hope it will not create any problem..

Please PM him to bring it to his attention.

*** removed ***

This post has been edited by Bilou_Gateux: Oct 5 2005, 08:44 AM

I tried this method for a BroadCom 57xx network interface card and it failed. Although it did try to install it evidenced by the yellowed out Ethernet Controller unter network device in the device manager -- that it would not do before. It is the Dell download R87461.exe where I got the driver. What else can I do to get this NIC installed ? Is it a new Microsoft driver signing issue or what ? Thanks.

Bob.Rein@FAA.GOV

Did you extract the files form the download? this method looks for the INF file...

Stickied!

Rewritten the program. It's now even easier!

run autoit3.exe and presetup.au3 from cd (no need for copying to system32 folder anymore):

i386\WinNT.sif

$OEM$\:


$OEM$\presetup.au3

CD-Layout:


Thanks for info idle.newbie

This post has been edited by hp38guser: Oct 9 2005, 04:19 PM