DriverPacks.net Forum - How to call DP_Install_Tool.cmd after sysprep.

Re: How to call DP_Install_Tool.cmd after sysprep.

null@example.com (JustusIV) — Tue, 07 Jul 2009 13:38:29 +0000

Appears to work accept i needed a title in there.

start /wait "Insert title here" "%SystemRoot%\system32\DP_Install_Tool.cmd"

Although i don't really know if i need this because of the issue of "Found New Hardware Wizard".

see post
http://forum.driverpacks.net/viewtopic.php?id=3859

Re: How to call DP_Install_Tool.cmd after sysprep.

null@example.com (OverFlow) — Tue, 07 Jul 2009 02:09:00 +0000

about a gig of disc space more required for M1 however you can use devpath for KTD like features...

However since after the install the drivers are not needed and should be deleted it really doesn't matter where you put them since you will delete them... I would not put anything i was going to delete in system32... just in case

Re: How to call DP_Install_Tool.cmd after sysprep.

null@example.com (JustusIV) — Mon, 06 Jul 2009 23:04:15 +0000

Once again i will have to give this a whirl tomorrow as i am not at work. I admit hard coding C:\windows is a bad idea but....
Whats the big deal on the system32 dir? I have started a habit of throwing a bunch of stuff in there, very handy for cmd tools etc
BTW m1. i dont really understand the difference between the two for SAD.

Re: How to call DP_Install_Tool.cmd after sysprep.

null@example.com (OverFlow) — Mon, 06 Jul 2009 22:50:02 +0000

Try this alternate...

Start /wait "%SystemRoot%\system32\DP_Install_Tool.cmd"

You did not really put the driverpacks in System32 did you? Oh my... M1 or M2?

PS always use %SystemRoot% instead of hardcoding C:\Windows - That is a very bad habit to get yourself into .

Re: How to call DP_Install_Tool.cmd after sysprep.

null@example.com (JustusIV) — Mon, 06 Jul 2009 13:29:53 +0000

OverFlow wrote:

use the command "Call" to run the script from a batchfile
Call %SystemDrive%/DriverPacks.net/DP_Install_Tool.cmd
that way it will return to your batchfile after the script exits.

This did not appear to work. Here is what i have. My file simply just ran the DP_Install_Tool and never ran the rest of my code. I have been using the file without the first call for a long time with no issues. Any ideas on what i am doing wrong?

firstboot.cmd

Call C:\WINDOWS\system32\DP_Install_Tool.cmd
@Echo off
c:\windows\system32\wsname /N:$SERIALNUM
reg add "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Runonce" /V runforme /d c:\windows\system32\secondboot.cmd
c:\windows\system32\shutgui /l /y /t:60 /r

Re: How to call DP_Install_Tool.cmd after sysprep.

null@example.com (JustusIV) — Sat, 04 Jul 2009 14:11:56 +0000

Perfect, that's what i did not do. I will give it a whirl. Thank you!!!!

Re: How to call DP_Install_Tool.cmd after sysprep.

null@example.com (OverFlow) — Sat, 04 Jul 2009 02:59:13 +0000

use the command "Call" to run the script from a batchfile

Call %SystemDrive%/DriverPacks.net/DP_Install_Tool.cmd

that way it will return to your batchfile after the script exits.

Re: How to call DP_Install_Tool.cmd after sysprep.

null@example.com (JustusIV) — Sat, 04 Jul 2009 01:14:31 +0000

How about calling DP_Install_Tool from a different batch file?
I would like to run DP_Install_Tool then do some things via batch after it completes but it seemed to just take over the batch file and the rest would never run
Maybe i as doing something silly i dont know.

P.S.
Thanks for all the help you have sent my way.
Maybe i should tell you guys how i am trying to run my universal image and you can tell me if there is better ways to do it.

Re: How to call DP_Install_Tool.cmd after sysprep.

null@example.com (OverFlow) — Fri, 03 Jul 2009 22:20:57 +0000

RunOnceEx is probably better and how I coded it in the alpha of BASE

Re: How to call DP_Install_Tool.cmd after sysprep.

null@example.com (JustusIV) — Fri, 03 Jul 2009 18:54:15 +0000

When i did this, i had to hit cancel on all the driver found new hardware prompts before it would proceed.
Still looking for tips.

How to call DP_Install_Tool.cmd after sysprep.

null@example.com (JustusIV) — Thu, 02 Jul 2009 20:10:38 +0000

I am just curious how other people are doing this.
what i have done is entered into
sysprep.inf

[GUIRUNONCE]
    command0="C:\SAD\DriverPacks.net\DP_Install_Tool.cmd"

Is there a better way?