DriverPacks.net Forum - DP work geat when run at t-39, but not when called from WPI

Re: DP work geat when run at t-39, but not when called from WPI

null@example.com (Stoner) — Tue, 16 Dec 2008 06:11:49 +0000

Not to sure if this will help you or not but heres to trying!

I have run the driverpacks from WPI with no problems by doing the following...

1. Slipstream the driverpacks as you normally would do (for me method 2)
2. Tell it you want to manually run the finsher so it can copy it to the clipboard.
3. Run WPI.hta
4. Under Tools (I think) tell it to run a script/cmd/whatver before the rest of the WPI is run by ticking the check box.
5. Press Ctrl+V and it will copy the finisher from your clipboard.

Sorry if this aint what you are after just trying to help.

Stoner.

Re: DP work geat when run at t-39, but not when called from WPI

null@example.com (OverFlow) — Sat, 08 Nov 2008 01:53:09 +0000

That was Bâshrat the Sneaky's idea of a joke...

You would be surprized how many people don't get it.
But for those of us who do... LMAO 2

I don't think i will change that lineever - at least not in the forseeable future

Re: DP work geat when run at t-39, but not when called from WPI

null@example.com (gospeed.racer) — Sat, 08 Nov 2008 01:41:49 +0000

No problem, I especially like the updater..."where did you get that?" LMAO

Re: DP work geat when run at t-39, but not when called from WPI

null@example.com (OverFlow) — Fri, 07 Nov 2008 00:24:11 +0000

nope you can have a m1 searchable ODD if you want most people go with the standard compressed packs but you dont have to

thanks for the feedback it is always aprecieated!

Re: DP work geat when run at t-39, but not when called from WPI

null@example.com (gospeed.racer) — Thu, 06 Nov 2008 19:13:16 +0000

I had to switch to driverforge to be able to get this working. Its working great now with WPI. Thank you for all your help

BTW, in that beta you had me try- when you choose on "stand alone disc" it still asks for slipstream method. Maybe I am missing something?

Re: DP work geat when run at t-39, but not when called from WPI

null@example.com (OverFlow) — Mon, 03 Nov 2008 12:01:14 +0000

we may have to wait for MS to improve DPInst.exe for that to happen

it may be neccessary to run it twice with a reboot inbetween...

Re: DP work geat when run at t-39, but not when called from WPI

null@example.com (gospeed.racer) — Mon, 03 Nov 2008 11:38:44 +0000

I R an idiot:) The method I am using is the presetup, I guess it loads before t-39, not at t-39. Anyway, that variation works 95% of the time, once in a while there will be a odd device not found or a audio driver with issues, but running the driverpacks after first boot seems to bring more errors and fewer found devices. Just as a test, I tried DriverForge with a usb drive and the same driverpacks, it found everything. I dont like the interface though, I want to stick with this if I can get it to be happier

Currently on my DVD, I have a LOT of different versions of XP- if I can get the driverpacks to install via wpi, then I can cut out half of the version and it will take half the time to rebuild every time I update

Re: DP work geat when run at t-39, but not when called from WPI

null@example.com (OverFlow) — Mon, 03 Nov 2008 10:46:25 +0000

the normal M2 method is the best...

the t-39 method is flawed
- detached program runs parallel to setup.exe
not detached program first then setup afterwards they both run at the same time
that is why we use presetup
- it prevents setup from running until were ready
IE if setup runs before we are done extracting all the drivers it can't search all of them???

i still like the idea of useing wpi to update an existing system.
jsut not for UWXP

Re: DP work geat when run at t-39, but not when called from WPI

null@example.com (gospeed.racer) — Mon, 03 Nov 2008 09:50:22 +0000

I tried the "/c /s /sh /lm /el" first, it slowed the install down to a crawl. Took a long time and kept halting on errors about not being signed. Still didnt find all the drivers like it does at t-39.

I then tried the new DPbase, and it acts the same way, cant find the drivers and painfully slow in comparison to the t-39 method

Thank you for giving it a shot, if you think this is a method worth looking into more I am happy to test whatever you throw at me

Re: DP work geat when run at t-39, but not when called from WPI

null@example.com (gospeed.racer) — Sun, 02 Nov 2008 08:41:37 +0000

I have been having so many problems with install/restart timing lately, I cant seem to get everything happy- so that was my answer.

I will try that, thank you again!

Re: DP work geat when run at t-39, but not when called from WPI

null@example.com (OverFlow) — Sun, 02 Nov 2008 08:10:33 +0000

try this instead...

http://driverpacks.sytes.net/driverpack … 1102RC.exe

it should be all fixed and ready for you to use in that RC

[thinking to self] call DriverPacks install tool from WPI... why didn't i think of that yet... i'm getting old...

Re: DP work geat when run at t-39, but not when called from WPI

null@example.com (gospeed.racer) — Sun, 02 Nov 2008 08:08:51 +0000

Will I only need to change the occurrence in "main"? I notice "m1found" has one as well

:M1Found
Echo.
Echo If you wish you may update drivers directly from the located M1 source
Echo Or you can use the DriverPacks and DP_Finisher with "Keep The Driver" option.
Echo If you choose Finisher and KTD then DriverPacks will be copied to "SystemDrive" 
Echo.
SET /p TPP=Only DriverPacks or Finisher and DriverPacks? (O or F) 
IF /I %TPP%==O "%CDDRIVE%\$OEM$\$1\DPINST.exe" /c /s & GoTo Done 
XCOPY /S %CDDRIVE%\$OEM$\$1\. %SystemDrive%


:Main
Echo.
Echo Running MicroSoft DPinst.exe now!
%SystemDrive%\DPINST.exe /c /s /sh /lm /el
Echo.
Echo Running the DriverPacks.net Finisher now!
%SystemDrive%\DPsFnshr.exe



:Done
EXIT

Re: DP work geat when run at t-39, but not when called from WPI

null@example.com (gospeed.racer) — Sun, 02 Nov 2008 08:01:50 +0000

I will edit the file and test in the morning, thanks for the very speedy reply! Keep up the great work!

Re: DP work geat when run at t-39, but not when called from WPI

null@example.com (OverFlow) — Sun, 02 Nov 2008 07:52:41 +0000

try dpinst /c /s /sh /lm /el

currently is dpinst /c /s

in the .cmd file

we have found a handful of bugs with dpinst...
it wont work at the root of a drive and it selectively ignores certain xml file entries

this will be fixed in teh next RC...

the path fix is already in the current RC 8.10.rc3

please report back to confirm or deny this fix... TIA

Welcome to DriverPacks and have a great day

DP work geat when run at t-39, but not when called from WPI

null@example.com (gospeed.racer) — Sun, 02 Nov 2008 07:44:33 +0000

I am having a bit of trouble, first off I have a multiboot DVD with DP working perfectly DURING install.
The problem is, I also use the DVD as an install DVD for software and as such I figured why not use the DPINST.exe since is already there. I call it from WPI and have tried before and after thew desktop loads. I quickly figured out that I needed to modify my DP_Install_Tool.cmd and now DP appear to be working. Here is the section I needed to modify (cant remember the user that reported this, I "borrowed" it:) )

:M2Found
Echo.
Echo Extracting the DriverPacks now...
%CDDRIVE%\OEM\bin\un7zip.exe %CDDRIVE%\OEM\DP*.7z %SystemDrive%\
%CDDRIVE%\OEM\bin\un7zip.exe %CDDRIVE%\OEM\bin\*.7z %SystemDrive%\
COPY /Y %CDDRIVE%\OEM\bin\DPsFnshr.ini %SystemDrive%\
IF EXIST %CDDRIVE%\OEM\*.ins COPY /Y %CDDRIVE%\OEM\*.ins %SystemDrive%\

:: Current entries
:: COPY DPINST.exe %SystemDrive%
:: COPY DPInst.xml %SystemDrive%

:: My edit
COPY /Y %CDDRIVE%\OEM\DPINST.* %SystemDrive%\

GoTo Main

Well, it looks like it is installing just fine but I end up with many components with asterisks next to them (before the DP install they are unknown devices) and this does not occur when they are installed at t-39. Any ideas?