Is it possible in conjunction with SETUPCOPYOEM.EXE?

[MadBoy]

Here's the log output from file. Even thou the @error isn't 0 (that's why it says FAILED there) i can still see OEM files created in Windows\Inf. Seems to work just weird that error isn't 0

[10:30:53] - Detecting Windows version - Windows XP x32
[10:30:53] - Detecting number of devices in system.
[10:30:53] - Found 134 devices without any problems.
[10:30:53] - Checking for drivers directory existance.
[10:30:53] - Drivers directory (e:\Drivers) exist.
[10:30:54] - Manual start used - Waiting for orders.
[10:30:55] - Integrating drivers with SetupCopyOemInf method.
[10:31:00] - Advanced Output: Inf integrated failed: e:\Drivers\1SA207WW\SMAXWDM\SE\SMWDMALI.INF
[10:31:00] - Advanced Output: Inf integrated failed: e:\Drivers\1SA207WW\SMAXWDM\W2K_XP\SMWDMALI.INF
[10:31:02] - Advanced Output: Inf integrated failed: e:\Drivers\1SRO15WW\WIN2K\B57W2K.INF
[10:31:03] - Advanced Output: Inf integrated failed: e:\Drivers\1SRO15WW\WINXP\B57XP32.INF
[10:31:04] - Advanced Output: Inf integrated failed: e:\Drivers\1YG409WW\tp4win2k.inf
[10:31:09] - Advanced Output: Inf integrated failed: e:\Drivers\70CN23WW\RSTRCLMG.INF
[10:31:11] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\EKEYAGT\dk.inf
[10:31:13] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\EKEYAGT\fi.inf
[10:31:15] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\EKEYAGT\fr.inf
[10:31:16] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\EKEYAGT\gr.inf
[10:31:17] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\EKEYAGT\it.inf
[10:31:18] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\EKEYAGT\jp.inf
[10:31:19] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\EKEYAGT\ne.inf
[10:31:20] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\EKEYAGT\no.inf
[10:31:21] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\EKEYAGT\sp.inf
[10:31:22] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\EKEYAGT\sv.inf
[10:31:23] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\EKEYAGT\us.inf
[10:31:25] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\EZBTNS\JP\EZBTNS.INF
[10:31:26] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\FLPTOUCH\Flptouch.inf
[10:31:28] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\OSD\DK.INF
[10:31:29] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\OSD\FI.INF
[10:31:30] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\OSD\FR.INF
[10:31:31] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\OSD\GR.INF
[10:31:32] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\OSD\IT.INF
[10:31:34] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\OSD\JP.INF
[10:31:35] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\OSD\NE.INF
[10:31:36] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\OSD\NO.INF
[10:31:37] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\OSD\SP.INF
[10:31:38] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\OSD\SV.INF
[10:31:39] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\OSD\US.INF
[10:31:41] - Advanced Output: Inf integrated failed: e:\Drivers\75VU08WW\ZOOM\TpScrEx.inf
[10:31:42] - Advanced Output: Inf integrated failed: e:\Drivers\AUDIO\SMWDMALI.INF
[10:31:44] - Advanced Output: Inf integrated failed: e:\Drivers\MODEM\AGRMDWXP.INF
[10:31:45] - Advanced Output: Inf integrated failed: e:\Drivers\NETWORK\AEIWLNIC.INF
[10:31:46] - Advanced Output: Inf integrated failed: e:\Drivers\NETWORK\WIN2K\B57W2K.INF
[10:31:49] - Advanced Output: Inf integrated failed: e:\Drivers\NETWORK\WINXP\B57XP32.INF
[10:31:50] - Advanced Output: Inf integrated failed: e:\Drivers\OTHER\BLUTOOTH.INF
[10:31:51] - Advanced Output: Inf integrated failed: e:\Drivers\OTHER\IBMPMDRV.INF
[10:31:52] - Advanced Output: Inf integrated failed: e:\Drivers\OTHER\IBMTPLCD.INF
[10:31:53] - Advanced Output: Inf integrated failed: e:\Drivers\OTHER\TP4WIN2K.INF
[10:31:54] - Advanced Output: Inf integrated failed: e:\Drivers\VIDEO\CX_06991.INF
[10:31:55] - Advanced Output: Inf integrated failed: e:\Drivers\VIDEO\CX_06992.INF
[10:31:56] - Advanced Output: Inf integrated failed: e:\Drivers\VIDEO\PHILDECN.INF
[10:31:58] - Advanced Output: Inf integrated failed: e:\Drivers\VIDEO\WIN2K\GARTNT.INF
[10:31:59] - Advanced Output: Inf integrated failed: e:\Drivers\VIDEO\WINXP\GARTNT.INF
[10:32:00] - Advanced Output: Inf integrated failed: e:\Drivers\1OMA23WW\nt4\agrmdnt4.inf
[10:32:00] - Advanced Output: Inf integrated failed: e:\Drivers\1OMA23WW\w2kxp\AGRMDwxp.inf
[10:32:05] - Advanced Output: Inf integrated failed: e:\Drivers\1OMA23WW\w98\AGRMDvxd.inf
[10:32:06] - Advanced Output: Inf integrated failed: e:\Drivers\1OMA23WW\wme\AGRMDMEE.inf
[10:32:11] - Advanced Output: Inf integrated failed: e:\Drivers\1OMA23WW\wme\AGRMDMEM.inf
[10:32:13] - Advanced Output: Inf integrated failed: e:\Drivers\1RD631WW\DRIVER\2KXP_INF\C2_21425.INF
[10:32:15] - Advanced Output: Inf integrated failed: e:\Drivers\1RD631WW\DRIVER\2KXP_INF\CX_21425.INF
[10:32:16] - Advanced Output: Inf integrated failed: e:\Drivers\1RD631WW\PHILDEC\WDM_2K\PHILDEC.INF
[10:32:17] - Advanced Output: Inf integrated failed: e:\Drivers\1RD631WW\PHILDEC\WDM_XP\PHILDECN.INF
[10:32:17] - TheENd

Hehe fixed it.. call me id*** ;p Timeings for this log are for inf's that are already integrated. But timeings in my last post gives like 1 inf per second (keep in mind that i have USB 1.1 with drivers so it slows down the whole process a lot i think). Anyway it needs testing

[10:42:39] - Integrating drivers with SetupCopyOemInf method.
[10:42:42] - Advanced Output: Inf integrated ok: e:\Drivers\1SA207WW\SMAXWDM\SE\SMWDMALI.INF
[10:42:42] - Advanced Output: Inf integrated ok: e:\Drivers\1SA207WW\SMAXWDM\W2K_XP\SMWDMALI.INF
[10:42:43] - Advanced Output: Inf integrated ok: e:\Drivers\1SRO15WW\WIN2K\B57W2K.INF
[10:42:43] - Advanced Output: Inf integrated ok: e:\Drivers\1SRO15WW\WINXP\B57XP32.INF
[10:42:44] - Advanced Output: Inf integrated ok: e:\Drivers\1YG409WW\tp4win2k.inf
[10:42:44] - Advanced Output: Inf integrated ok: e:\Drivers\70CN23WW\RSTRCLMG.INF
[10:42:45] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\EKEYAGT\dk.inf
[10:42:45] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\EKEYAGT\fi.inf
[10:42:45] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\EKEYAGT\fr.inf
[10:42:45] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\EKEYAGT\gr.inf
[10:42:45] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\EKEYAGT\it.inf
[10:42:45] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\EKEYAGT\jp.inf
[10:42:46] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\EKEYAGT\ne.inf
[10:42:46] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\EKEYAGT\no.inf
[10:42:46] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\EKEYAGT\sp.inf
[10:42:46] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\EKEYAGT\sv.inf
[10:42:46] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\EKEYAGT\us.inf
[10:42:46] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\EZBTNS\JP\EZBTNS.INF
[10:42:46] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\FLPTOUCH\Flptouch.inf
[10:42:46] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\OSD\DK.INF
[10:42:47] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\OSD\FI.INF
[10:42:47] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\OSD\FR.INF
[10:42:47] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\OSD\GR.INF
[10:42:47] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\OSD\IT.INF
[10:42:47] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\OSD\JP.INF
[10:42:47] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\OSD\NE.INF
[10:42:47] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\OSD\NO.INF
[10:42:47] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\OSD\SP.INF
[10:42:47] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\OSD\SV.INF
[10:42:48] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\OSD\US.INF
[10:42:48] - Advanced Output: Inf integrated ok: e:\Drivers\75VU08WW\ZOOM\TpScrEx.inf
[10:42:48] - Advanced Output: Inf integrated ok: e:\Drivers\AUDIO\SMWDMALI.INF
[10:42:48] - Advanced Output: Inf integrated ok: e:\Drivers\MODEM\AGRMDWXP.INF
[10:42:48] - Advanced Output: Inf integrated ok: e:\Drivers\NETWORK\AEIWLNIC.INF
[10:42:49] - Advanced Output: Inf integrated ok: e:\Drivers\NETWORK\WIN2K\B57W2K.INF
[10:42:49] - Advanced Output: Inf integrated ok: e:\Drivers\NETWORK\WINXP\B57XP32.INF
[10:42:49] - Advanced Output: Inf integrated ok: e:\Drivers\OTHER\BLUTOOTH.INF
[10:42:49] - Advanced Output: Inf integrated ok: e:\Drivers\OTHER\IBMPMDRV.INF
[10:42:50] - Advanced Output: Inf integrated ok: e:\Drivers\OTHER\IBMTPLCD.INF
[10:42:50] - Advanced Output: Inf integrated ok: e:\Drivers\OTHER\TP4WIN2K.INF
[10:42:50] - Advanced Output: Inf integrated ok: e:\Drivers\VIDEO\CX_06991.INF
[10:42:50] - Advanced Output: Inf integrated ok: e:\Drivers\VIDEO\CX_06992.INF
[10:42:50] - Advanced Output: Inf integrated ok: e:\Drivers\VIDEO\PHILDECN.INF
[10:42:51] - Advanced Output: Inf integrated ok: e:\Drivers\VIDEO\WIN2K\GARTNT.INF
[10:42:51] - Advanced Output: Inf integrated ok: e:\Drivers\VIDEO\WINXP\GARTNT.INF
[10:42:51] - Advanced Output: Inf integrated ok: e:\Drivers\1OMA23WW\nt4\agrmdnt4.inf
[10:42:51] - Advanced Output: Inf integrated ok: e:\Drivers\1OMA23WW\w2kxp\AGRMDwxp.inf
[10:42:51] - Advanced Output: Inf integrated ok: e:\Drivers\1OMA23WW\w98\AGRMDvxd.inf
[10:42:52] - Advanced Output: Inf integrated ok: e:\Drivers\1OMA23WW\wme\AGRMDMEE.inf
[10:42:52] - Advanced Output: Inf integrated ok: e:\Drivers\1OMA23WW\wme\AGRMDMEM.inf
[10:42:52] - Advanced Output: Inf integrated ok: e:\Drivers\1RD631WW\DRIVER\2KXP_INF\C2_21425.INF
[10:42:52] - Advanced Output: Inf integrated ok: e:\Drivers\1RD631WW\DRIVER\2KXP_INF\CX_21425.INF
[10:42:53] - Advanced Output: Inf integrated ok: e:\Drivers\1RD631WW\PHILDEC\WDM_2K\PHILDEC.INF
[10:42:53] - Advanced Output: Inf integrated ok: e:\Drivers\1RD631WW\PHILDEC\WDM_XP\PHILDECN.INF
[10:42:53] - TheENd

[MadBoy]

BOOL SetupUninstallOEMInf(

PCWSTR InfFileName,

DWORD Flags,

PVOID Reserved

);

Now since the SetupOemInf is working maybe SetupUninstall should be done too. Just not sure how the script should know what's the name of script to unninstall inf's. Maybe i should run it on all Oem.inf's and if those aren't used it would unninstall them?

[donjuan]

So the topic has gone far away from my scope:)) no prob..

Is there any new way of integrating those infs faster than setupcopyoeminf method????

[schalti]

Is there any new way of integrating those infs faster than setupcopyoeminf method????

No there isn't .

Both the AutoIt-Application from MadBoy and SetupCopyOEMInf.exe from Pyron use the very same API call and this API call is the one M$ wants you to use when integrating drivers in 2K/XP/2K3. Simply copying the files by script won't do the job correctly.

THANK YOU M$ again for this stupid driver signature stuff .

In NT 4.0 you could do whatever you wanted with the setup and the drivers.

In Vista 64Bit Version it isn't even possible anymore to install unsigned drivers!

The whole setup process (setupapi.dll) is a black box already and it will be even worse in the future. All you can do is to use the API calls and if it is slow you cannot do anything about it.

[RogueSpear]

Well I can tell you that my method works perfect and it's pretty simple. I went through my building at work this week rounding up every single USB/FireWire/PCMCIA device I could get my hands on and everything installed like a charm.

[schalti]

Well I can tell you that my method works perfect and it's pretty simple.

Of course . There are several methods to integrate drivers, DevicePath in the Registry is one way to do it, however since I work with a single XP Image for all Systems (Notebooks, Tablets, Desktops, POS etc.) I include all drivers which clearly has its limit when using DevicePath. Simply copying the INF/PNF/CAT will work however if you check %windir%\setupapi.log, it will tell a slightly different story. One thing is for sure, the API call SetupCopyOEMInf exists in Vista and Longhorn server in both 32 and 64 Bit version, so this method will still work while others will fail some day. In 64 Bit Vista for example it will not be possible anymore to just copy INF/PNF/CAT because copying those files breaks the signature and you cannot install unsigned drivers in 64 Bit Vista.

Things used to be so easy with NT 4.0.....

[RogueSpear]

Perhaps I didn't explain clearly enough. I perform a standard Method 2 during setup and then run my KtD script during RunOnceEx. I only mentioned how I used the KtD post setup on my wife's laptop because I thought it was a nice side benefit to be able to "retrofit" an existing install with added driver support.

As far as Vista goes.. I'll worry about that later. Much later in fact. At my main job and at all of my client sites, I plan to keep XP for years to come. It does absolutely everything needed and then some. I've played with Vista for a little while now and to me it's not a whole lot more than a cosmetic makeover.

[schalti]

As far as Vista goes.. I'll worry about that later. Much later in fact. At my main job and at all of my client sites, I plan to keep XP for years to come. It does absolutely everything needed and then some. I've played with Vista for a little while now and to me it's not a whole lot more than a cosmetic makeover.

It's more than a cosmetic makeover because it has additional prohibition in many areas. Digital Rights Management, the WinPE-only (!) imaging process, enforced Driver Signing on the 64Bit version and other things.

I'm not sure yet about the success of Vista. Problem #1 will be the support practice of M$. They did it with NT 4.0, they are doing it with W2K and they will do it with XP. One day they will just stop to develop security hotfixes. This will force business customers all over the world to upgrade, for legal reasons! I hope this will finally open the eyes of some important decisionmakers.

Home users will be happy about the new user interface and will buy Vista simply because the new PC will ship with Vista.

Personally I cannot see a single reason why to upgrade to Vista. The new user interface will not increase user productivity in a business environment, so what's the point with Vista? Even WinFS if supplied later in Vista SP1 would not be a reason to upgrade because it only works on local resources.

[donjuan]

Perhaps I didn't explain clearly enough. I perform a standard Method 2 during setup and then run my KtD script during RunOnceEx. I only mentioned how I used the KtD post setup on my wife's laptop because I thought it was a nice side benefit to be able to "retrofit" an existing install with added driver support.

As far as Vista goes.. I'll worry about that later. Much later in fact. At my main job and at all of my client sites, I plan to keep XP for years to come. It does absolutely everything needed and then some. I've played with Vista for a little while now and to me it's not a whole lot more than a cosmetic makeover.

Does setdevicepath.exe in your presetup.cmd have a character limit such as 4096 bytes or else? As I understand, setdevicepath.exe changes path to the uncompressed driver directory and searches the path recursively.And as I guess, setdevicepath.exe method is faster in terms of installation time.

And one more question, as I read in the forum, microsoft suggests to reset the devicepath to windows\inf by default.How does your mathod manage this issue? Which one is better in your opinion ? to reset or not to reset the path?

Thanks...

[schalti]

Does setdevicepath.exe in your presetup.cmd have a character limit such as 4096 bytes or else? As I understand, setdevicepath.exe changes path to the uncompressed driver directory and searches the path recursively.

The registry entry that is set by Setdevicepath.exe has a length limit of 4095 characters.

The tool searches recursively, but the resulting registry entry has a length limit.

[RogueSpear]

The registry entry that is set by Setdevicepath.exe has a length limit of 4095 characters.

The tool searches recursively, but the resulting registry entry has a length limit.

Actually the 4096 limit only applies to OemPnPDriversPath in WINNT.SIF, not to the registry entry created by SetDevicePath.exe. Instead of having a 4KB limit (WINNT.SIF), it has a 32KB limit. Also, SetDevicePath.exe prepends it's registry entry with %systemroot%\inf. So you're completely covered after it's use.

[donjuan]

The registry entry that is set by Setdevicepath.exe has a length limit of 4095 characters.

The tool searches recursively, but the resulting registry entry has a length limit.

Actually the 4096 limit only applies to OemPnPDriversPath in WINNT.SIF, not to the registry entry created by SetDevicePath.exe. Instead of having a 4KB limit (WINNT.SIF), it has a 32KB limit. Also, SetDevicePath.exe prepends it's registry entry with %systemroot%\inf. So you're completely covered after it's use.

So guess I've used all the driverpacks from Beshrat.Will all my drivers be recognized and added to the registry?

And as for my second question, is it better to reset the driverpack directory to windows/inf or not?

Thanks

[MadBoy]

If it realy has 32KB limit then i would suggest to use that method. And yes it's always better to reset the path to drivers, unless you keep them on your hdd (like C:\Drivers) then you could leave it as it is. The orginal path %systemroot%\inf is also in registry so you shouldn't worry.