where i can find WINDOWS 7 tool , and for free plz , link me

Right here (2nd post): http://forum.driverpacks.net/viewtopic.php?id=4954

Windows XP users must install Service Pack 1, the minimum, before attempting to install the package. Failure to do so will result in failure to support USB 2.0. Also required to install the DirectX 9.0 or higher is required to use NVMixer.

Yes, I totally agree with your point that Windows XP users must install Service Pack 1.It will help you.

DPinst:

after discussion with colleague which possibilitys we have and which one we should choose, we decided to run the dpinst every boot as a service. we think we can seal the machine (if we want) based on returncodes from dpinst. (we hope there are some - not yet researched)

to conclude:
i realised it with a service with no error logging (no messages) which runs on start up with configured xml file.
services starts and will end after 1-2 secounds. We think this is the best and most professional workaround.

New Hardware Found Wizard:
there were two seperated things i mixed unfortunatly.

the hardware wizard as it self and the dialog box which asks for found driver but searches for specific files. (like "install from disk message box".) (our windows i localised, i don't know the real wording)

1. the hardware wizard pop up / searching for files get's fixed with SetDevicePath.exe as it should. (NICE!)
2. the "searching for file/install from disk" box isn't fixed with SetDevicePath. It's only fixable with another entrie in registry (i don't remeber the right one right now) (Install Source, ServicePack Source or something in \Windows\CurrentVersion). (easy for everyone to proof)

thanks

did you read my last post ? ? ?

No, i was writing in this time

He has been willing to go a little more in depth with me VIA email / PM . So that is not a show stopper .

RE the USB dongle...
try putting the drivers on the disk image.
Say at %SystemRoot%\MyDrivers\USB 
Then add the path to the windows registry "DevicePath"
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DevicePath
IE update the value to  "%SystemRoot%\Inf;%SystemRoot%\MyDrivers\USB"

for a normal install with DriverPacks BASE this method is referred to as "KTD" and will work with certain drivers like a USB dongle or an external modem, monitor etc. It is likely to fail at higher level drivers like sound and graphics . It also has a path limit that can be exceeded if you are to greedy .

yesterday i tried to work with
SetDevicePath.exe and SetupCopyOEMInf.exe.

SetDevicePath seemed to be a good choice.
I bundled a package: X:\Drivers
it included 2 folders with drivers and in root SetDevicePath and dpinst.
i run it both. and the behavior was the same. (you all know that SetDevicePath set's the values you mention.)
Windows seems to look only in "Installation Sources"
The path of DevicePath was not recommended/given in Hardware Wizard.
But my i did some mistake. I will proof in the next hours. (or is Windows really looking without showing the path in Hardware wizard?!)

So far thanks to all... (with small expection ^^)

I don't see the need for secrecy, setting up systems to boot and/or reinstall via pxe is somewhat rare but it isn't secret by any means.

But whatever you think is necessary..........

Man, i don't know why you thump about the real project. The description that it's like PXE streaming boot is pretty close on the real projekt with one difference. Think about that PXE has no ability for individual settings, but I have the ability. But this has risks for security reasons. If i open this possibility, than the user can also do changes which i want to avoid. This all has to do with security restrictions.

Concept 0: Installing drivers on first boot with dpinst without restart.
* Again: I understand that the method like installing display drivers without reboot on system start isn't possible.
- fail

Concept 1: Install drivers on several machines to integrate them fully functional.
* This is to specific. So only the selected devices on the real machine are integrated and no other pid vid devices.
- fail

Concept 2: Installing drivers with dpinst while first start. Wait some time. SAVE. Restart. Use.
* The normal way, but because of the security restirctions. it's difficult to handle.
- ~

Concept 3: Installing drivers with dpinst. seal. | image boots up, Card should be detected. SAVE. Restart. Use.
* Doesn't work. - The driver isn't installed fine. yelllow exclamation mark and the annoying found new hardware wizard.
* Because of the security restirctions. it's difficult to handle.
- would be nice, but doesn't work well.

Concept 4: Installing drivers with dpinst. seal. | image boots up, dpinst runs again (much faster). SAVE. Restart. Use.
* The only difference to concept 2 are the preinstalled drivers which saves time while the dpinst process.
* Because of the security restirctions. it's difficult to handle.
* This is a process which runs every time once. - Process should be avoided.
- seems to work. But i this it's not a real good deal.

So now we may can try to figure out the dpinst behavior i described here and in short in my previous post?
(Pay attation to the bold keywords.)

And may you can give some recommendation you would prefer

RE the USB dongle...
try putting the drivers on the disk image.
Say at %SystemRoot%\MyDrivers\USB 
Then add the path to the windows registry "DevicePath"
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DevicePath
IE update the value to  "%SystemRoot%\Inf;%SystemRoot%\MyDrivers\USB"

for a normal install with DriverPacks BASE this method is referred to as "KTD" and will work with certain drivers like a USB dongle or an external modem, monitor etc. It is likely to fail at higher level drivers like sound and graphics . It also has a path limit that can be exceeded if you are to greedy .

But whatever you think is necessary..........

i understand / accept that no reboot doesn't seem possible. but for now, as i described i don't understand the behaviour i about dpinst and restart (new hardware found wizard).

i'm willing to create a workaround, but this one has to be clean and nice. i personaly don't like quick and dirty solutions in/at/for work.

I will write the error's i found, if i gonna remember my testing szenario . last i remeber is, that there was an inf (normal dpinst found) and your programm didn't found and showed the dpinst switches in a big gray dialogwindow. And there was referring an error in line xxxxx (i don't remember).

Try and remember to get the path that it's screwing up on. That'll help me hone in on what is causing the issue.