Search options (Page 35 of 213)

I think you are missing the point...

Somthing during setup (at t-13 /svcpack.inf) is calling your script... you either need to find what is calling your script and fix it OR

rename your install.cmd... which seems to be the easier thing to do.

if you don't fix this then all the installs in install.cmd will occur twice. Once during Preinstallation (at t-13) and again during Gui mode setup. if you move the finisher the other programs will still run at the wrong time. Not only that but wahtever program that svcpack.inf is calling to run will NEVER be run... so you have two major issues. all the programs in your script run twice and the one that is supposed to be run at t-13 from svcpack.inf never does. 

RENAME YOUR SCRIPT!

you don't need SAD or KTD to install drivers with your multiboot disk...

both of these tools are for dealing with somone adding hardware after the machine is done. Ie shipped to a customers home... or if you add somthing weeks or months after the install... I don't use either... not ever. Hardware doesn't change after you are done installing.

Although it is not impossible... mr_smartepants is 100% correct (again), 

the Finisher does NOT run at t-13, nor any other DriverPacks function, and they absoutely should not be modified / customized to do so.

svcpack.inf executes at the T-13 minute stage do you have a call to the finisher in SvcPack.inf by mistake?

No part of DriverPacks is set to run from service pack INF, PERIOD. (At least not by DriverPacks BASE. Nor is it recomended by any instructions found on this site)

The extraction of the DriverPacks is done WELL before this stage of setup and the finisher is not ever SUPPOSED to run till after the reboot. It is POSSIBLE that there is a mistake (made by you or others) in your setup... IE there is a call to the DriverPacks Finisher buried in your svcpack.inf or one of the functions, routines or scripts that is called from svcpack.inf. (if you put in a blank svcpack.inf does the issue go away?)

I am going to make a bet here... I bet a dollar that there is a direct or indirect call to "install" or "install.cmd" in your SvcPack.INF.
-If you change the name of your script to Customiz.cmd does your issue go away?

Never EVER do KTD  "ALL" ...
It won't work and it will probably cause NONE of the DriverPacks to work as KTD is intended to... KTD means you intend for the DriverPacks to be available post install (read "available FOREVER"). The path length long ago exceeded the max size of a single registry entry ( I have forgotten but i belive it's one MB in XP ). Best case scenario it will truncate the path and you will get a partial path, most of the time it will simply be left as a blank path (not even the default of %systemroot%\inf will exist... Extremely Bad!). Worst case scenario this will render ALL  drivers unavailable (meaning even the included with windows drivers), or best case scenario most of the drivers unavailable (about three gig of driver files on the HDD that are invisible to windows). if you insist on KTD (not recomended ... Use SAD instead) Then ONLY KTD the monitor pack, modem pack and HID pack or other Third Party DriverPacks (things that a user might plugin post install {ps the Printer Pack WON'T work since it requires the DriverPacks Finisher}). Chipset, Mass and Graphics are not going to change ... and if they do change your not going to want drivers that are outdated nor have the mess in the registry. I am going to assume that your not going to update the MB and Graphics card the first week ... and if you do it's probably a good idea just to do a clean reload ... especialy since you have an unattended install .

KTD never did, and never will, do what it was intended to do. Any driver that requires "finishing" IE reg files added or setup run or any additional tweaking (stuff normally done by the DriverPacks Finisher) WILL fail to install. IE graphics cards, printers, sound cards... will all fail to install properly... so don't include them with KTD. In fact if you are smart you won't use KTD at all.   

If you do install a printer or sound card or video card then run SAD! It works 1000% better and does not burn a bunch of HDD space needlessly.

KTD was replaced and made completely obsolete by SAD.

Having said all that, I must also admit that KTD with the Monitor, HID and modem packs might make sense in special cases... like for a PC repair shop where the end user's monitor, modem, keyboard or mouse are not at the shop with the PC. Please note that these are very simple drivers and very small packs.

Yes it is possable... but it is not simple, unless you have your original DPs_BASE.log.

If you have an OEM Folder (Different from $OEM$) then you used M2.
If you have txtsetup.org then you added mass storage text mode.
If you have *.ins files then you selected Graphics Control panels.
Winnt.sif will tell if you used GUIRunonce. "[GUIRunonce]" (or not)
$OEM$\cmdlines.txt will tell if you used RunOnce "ROE.exe" (or not)

that should get you started

Mr_Smartepants wrote a script to make XP a preactivated copy (Like an OEM restore CD). I don't remember where he put it. MSFN.org i think... Ill ask him to chime in here . My guess is it only works for Installs and not for images though.

Never use a copy downloaded from the net. You have no idea what you are going to get. Mostly / usually a headache.

Only use an Original Hologramed disc as your source. (no hash required)

Warez and Pirating are not supported... Go Legit or go home.

Closed.

You will need to manually add the usb driver to your PE disc.

I might be able to fix this... i disabled a module in base that would copy chipset drivers to the INF folder in windows. At that time there was no benifit. Perhaps now with USB3 out there is now a good reason to RE-enable that routine...

I'm going to add ou to the testing team so you can access the new BASE... you will have to wait a minute for me to punch out a new version with that module re-enabled

Jeff

Thanks for including your logs and for providing such excellent details. It is not often we get a first post with almost everything we ask for in "Read BEFORE you post". So I sincerely want to thank you for 'helping us to help you'! That is a very nice treat and it makes answering your question MUCH easier.

"slipstream finished in 2 minutes and 58 seconds."

Perhaps this statement is a little vague or understated... but I never thought so. DriverPacks BASE slipstreams the DriverPacks into your installation media. The popup indicates that BASE has completed that task in slightly less than three minutes. That is to say "Done!", "Complete", "Accomplished", "End of task" or we could (and do) say "Finished"

Put another way this indicates normal termination of the task, BASE waits for you to acknowledge that it did complete successfully. Once you click 'Yes' DriverPacks BASE exits because there is nothing else to do, We are finished.

I can see how that might seem odd... since we don't return to the GUI. But there is absolutely no reason to return to the GUI since we are finished.

Thanks for reporting with such excellent details!

Welcome to DriverPacks.net

Jeff

PS I added "code tags" to your post to make it more readable. You can edit your post to look to see how that is done . I also removed the INI settings from the top since the DriverPacks BASE log includes the INI settings at the bottom so they were redundant. I would rather get them twice than not at all.

That is it, just follow the guide.

... and it is a Stand Alone Driver installer too.
Yes it's a universal drivers disc, and you don't have to read anything else.

Please note that the guide does not tell you that you can ALSO run SAD to update any computer at any time making it a fully complete "universal drivers disc".

check out OffLineSysPrep by Galapo...

it uses BartPE to do just that (no partition required for BartPE use a thumb drive or CD)

can you use the link to the HWID's tool in my signature to get the HWIDs please...

yup... look here
http://forum.driverpacks.net/viewtopic.php?id=3638

Certain drivers require registry entries... during an install the registry is not created yet . The initial registry is created from "hive" files. By editing the hive files one may seed the registry. I refer to this as the "PnP Interface Fix". It is on my to do list.
http://forum.driverpacks.net/viewtopic.php?id=4943

Jeff

PS For Universal Imaging you can simply add the registry entries to the local registry instead of editing the hive files .

IE:

reg.exe add "HKLM\loaded_SYSTEM\ControlSet001\Services\nvgts\Parameters\PnpInterface" /f /t REG_DWORD /v "5" /d 1 
reg.exe add "HKLM\loaded_SYSTEM\ControlSet001\Services\nvgts5\Parameters\PnpInterface" /f /t REG_DWORD /v "5" /d 1 
reg.exe add "HKLM\loaded_SYSTEM\ControlSet001\Services\nvgts6\Parameters\PnpInterface" /f /t REG_DWORD /v "5" /d 1 
reg.exe add "HKLM\loaded_SYSTEM\ControlSet001\Services\nvgts7\Parameters\PnpInterface" /f /t REG_DWORD /v "5" /d 1

Skip loading and unloading the hive as described in that thread. That is only required for clean installs. Please note that the above is an example for Nvidia, other drivers may also require the fix. The drivers inf file will tell you if it is one of these. Search for a line that contains an entry similar to

Parameters\PnpInterface", "5",

"5" is the problem... it means the device is a PnP driver ONLY and will not work in legacy mode. (That is to say it is a poorly written driver).