Search options (Page 1 of 2)

Also on a side note. I did just verify again that you do have to have the KB835221.exe installed before this will work.
Is there any harm in integrating that into machines that don't need it?

I have kinda done this a bit. basically you could do the first steps to a copy of xp (slipstream SP's, intergrate hotfixes, use nlite, and tweaks etc) then just install that copy of xp that you tweaked from the hard drive, to do that you would need to boot into bartpe copy over the windows install from usb to the hdd and run this command.
winnt32.exe /syspart:c: /tempdrive:c: /noreboot /makelocalsource
Seems easy peasy to me.

If you have questions just ask.

I am not really sure about seeding the chipset driver, never done that.
Anyway i just wanted you to know the hang that i get from the DP_Graphics_B_wnt5_x86-32_90701 is reproducable via SAD. after the reboot though everything is dandy.

Guess i don't ever do that
My use for driver packs are just using SAD though.
If you want me to test something just let me know, i will.

I will test what ever you want.
I guess i don't really understand the driver signing. I just run the DP_Install_Tool.cmd from SAD. Didn't know that if there was driving signing issues they wouldn't install.

Gotcha. Although since i just got my setup working nicely i will probably steer clear for a while.

On a side note if you guys ever need help testing something i would be more then happy to help just let me know.

While i did not follow the instructions in this tutorial
http://forum.driverpacks.net/viewtopic.php?id=1682
I might go through it just for experience.
I am using the GuiRunOnce but call DP_Install_Tool.cmd via a batch file that is called from the GuiRunOnce.
I am not having any issue with the desktop.ini bug ducumented here.
http://forum.driverpacks.net/viewtopic.php?id=1208
Everything seems to be working for me.

Ok, i wrote a little autoit that searches for found new hardware and presses esc. I call this from a batch file before i run DP_Install_Tool.cmd. I do all this from the GuiRunOnce. I tried the RunOnceEX jazz and while i got it working it just didnt seem to flow like i wanted it to. So far it seem to be working. I looked around but am not seeing the issues with the GuiRunOnce.
If you want to see my autoit script and or my batch file i will be happy to post it.

So i tried using

@echo off

SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx

REG ADD %KEY%\001 /VE /D "Installing Drivers" /f
REG ADD %KEY%\001 /V 1 /D "%systemdrive%\windows\system32\DP_Install_Tool.cmd" /f

And i still get the pop up Found New Hardware Wizard.
Which in turn makes the DP_Install_Tool say PnP manager busy.
I did not try this after a sysprep but just added it to reg and rebooted. I would assume i would have the same results whether it is being syspreped or not.
Ideas?

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.

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

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