I tested this method myself and I now know that this method has some advantages and two big disadvantages:advantages:
- Windows directly identifies and installs the drivers. With our method, we always needed to tell windows to search for the drivers. With this method this isnít necessary. (just like you plug in a new USB mouse)
- This is a by Microsoft documented method. This method is already used for some devices (scanners mostly ask to install the software first before you plug & play the device.) This method is stable.
- This method has no problem with double file names: You might think that our method doesn't have this problem either. I'm not so sure about that.
What would happen if their are two device that both use a different version of the file a.sys
Then we would have in our Drvindex.inf:
How does windows know which file to use??
In this method this is all taken care off.disadvantages:
- It takes a lot of space on the harddrive, my D folder now is 644 MB, when this is in a .CAB file, it is only 193MB
- It takes some time to run SetupCopyOEMInf.exe With all Bashrat's DP's this could easily take 15 min.
What I'd like to do is put in a routine to run from RunOnceEx (or possibly cmdlines.txt) that makes this monster cab file from the contents of D, delete D, and make the necessary changes to the registry and anywhere else so that a future PnP enumeration will look in the custom cab in addition to the stock cab.
This would take a lot of time. About 15 min on every boot. Besides with this method this isn't necessary (only you don't have any compression)
Oh yea.. OT but interesting: I discovered today that Viewsonic makes available a single file for download that contains the drivers for dozens of their monitors. Wouldn't it be nice if all monitor manufacturers did this?
Yeah, that would be great. I would wish that all driver manufacturers did this. I think that there is one big reason why this doesn't happen. Just think about all the poor souls with their 56K modem
The only negative I can find so far is that we will still be bound to the 4096 character limitation in the winnt.sif file.
This method solves this problem
Would it be possible to let SetupCopyOEMInf.exe scan inside a .CAB or .7z file?
Edited by erik_demon, 23 April 2005 - 05:47 AM.