You know, by-the-way, that your saying in one hand that both GUIrunoce & RunOceEx, conflicts with the WPI.. and the other hand, your saying that I should leave it to default.. zero problems...

Actually what I said was that GUIRunOnce and RunOnceEx execute at the same time.
Read...
http://unattended.msfn.org/unattended.xp/print/web/13/

So if you have abc.exe run during GUIRunOnce, and xyz.exe run during RunOnceEx; then both abc.exe and xyz.exe will execute SIMULTANEOUSLY!!
This will cause problems!

so your saying that I need to leave it just the way it is & it will be O.K?

Err, have you actually tried it already?

Ususally, the problem solution works that way, you try something, it doesn't work, oyu come here, report and we'll see if we can find a solution.

It does not help much to ask about problems that you may expect to happen when you have not already given it a try.
If you do not have a spare machine to do a test run, use a VM - it won't install any drivers per se, but the Finisher et al will run through regardless.

if both apps use ROE and they use different IDs, you WILL BE FINE.
Don't break your head (and ours) about something that actually doesn't pose a problem IRL

You know, by-the-way, that your saying in one hand that both GUIrunoce & RunOceEx, conflicts with the WPI.. and the other hand, your saying that I should leave it to default.. zero problems...

The only tiny thing that your forgetting about is, that the default of DrivePacks is RUNONCEEX.... funny huuu?...

The DriverPacks runonceex defaults are fine with WPI, I do it all the time.

Also, chosing a number < than WPI will make it run before, > will make it run after (I presume, never done that myself, yet, LOL).

the WPI is designed to load before windows logging on, and the DrivesPack design to install them-self at the same time..

can anyone help me out with this one?

There is an option called: "RunOnceEx - Custom ID", (default is: 937) any I.D will be O.K?

thanks!!!