3,626

(61 replies, posted in Feedback and Support - DriverPacks Base)

It is always the obvious stuff that takes forever to find wink

3,627

(12 replies, posted in Software)

well i found Pyrons original post and one version of the source code for setup
http://www.msfn.org/board/SOLVED-driver … ntry159358

#include "windows.h"
int APIENTRY WinMain(HINSTANCE hInstance,
                    HINSTANCE hPrevInstance,
                    LPSTR     lpCmdLine,
                    int       nCmdShow )
{

    SHELLEXECUTEINFO mySHELLEXECUTEINFO;

    mySHELLEXECUTEINFO.cbSize=sizeof(SHELLEXECUTEINFO);
    mySHELLEXECUTEINFO.fMask=SEE_MASK_NOCLOSEPROCESS;
    mySHELLEXECUTEINFO.hwnd=NULL;
    mySHELLEXECUTEINFO.lpVerb="Open";
    mySHELLEXECUTEINFO.lpFile="cmd.exe";
    mySHELLEXECUTEINFO.lpParameters="/C setup.cmd";
    mySHELLEXECUTEINFO.lpDirectory=".";
    mySHELLEXECUTEINFO.nShow=NULL; // or SW_SHOW;

    ShellExecuteEx(&mySHELLEXECUTEINFO);
    WaitForSingleObject(mySHELLEXECUTEINFO.hProcess,INFINITE);

    return 0;
}

I also noticed you added the last post to that thread... today in fact...

i guess you didnt read all of the 23 pages - and missed it on page 5 wink

thanks to your interest i now have the source and know who the author was... Yea!

3,628

(12 replies, posted in Software)

NP have a great day!

PS i would also like to have the source for that file... wink

Welcome to the forum dutchtraveller and bajargratis

thanks for your interest and taking the time to 'vote'.

Vista will absolutely have 64bit support.

It is only the XP platform we are discussing whether to support in 64 bit or not...

yes you are wink

(and they said you were untrainable... LOL)

3,631

(12 replies, posted in Software)

nope it never has been available to me - nor do i know who wrote it...

fake setup and presetup.cmd both run from %systemRoot%\system32\

Why in the world would i need the 'fake' setup program to return that value????
(i already have two variables that return that value...  SystemDrive and SystemRoot.)
[scratches head and is confused]


you said "Indeed, if there's a Hard Disk with a OEM folder/file at root, then identification is corrupted."

Um no if there is a folder at root named OEM then we have found the DriverPacks.
(we are the only ones who use this name
if you use it for something else then shame on you,
pick a different name) wink

3,632

(61 replies, posted in Feedback and Support - DriverPacks Base)

well this is a standard 845 chipset MB your list of devices are all supported.

845 chipset is supported is in DriverPack Chipset
Intel Pro\1000 is supported is in DriverPack LAN
Intel Extreme Graphics Driver is in DriverPack Graphics B

IDK why they would not be updated...

perhaps seeing your %SystemDrive%\DP_Install_Tool.log will shed some light on the problem.

  ( probably located at C:\DP_Install_Tool.log )

yes the tag must be 8.3 compliant

3,634

(61 replies, posted in Feedback and Support - DriverPacks Base)

HWID's tool is in my signature below wink

Welcome to the DriverPacks forum

please read "read BEFORE you post" in my signature.

Update the missing info in your title and post, and in your case we also need your HWID's

Looking forward to helping you... have a great day.

3,636

(210 replies, posted in Software)

I do apologize... i am a programer not a writer...

would you like to take a crack at making it clean and easy to read?

I would welcome the help!

jeff

3,637

(4 replies, posted in Other)

i second useing a sp3 slipstreamed source as a possable fix

3,638

(210 replies, posted in Software)

http://forum.driverpacks.net/viewtopic.php?id=2264

read teh first and last post and let me know if you have any questions

pay particular attention to the section titled DVD directions.

3,639

(210 replies, posted in Software)

yes the sad disk can be created without a source OS as long as you dont want cab compression.

if you require cab compression you will need 2k 2k3 or xp OS to trigger base into doing the cabbing
I will probably add the abblity to create a SAD disk from base as an option / platform. it seems to be a popular feature.

a sad disk will work on 2000 XP or 2003

well to be legal you should have a "licence" for each disk you burn

IE if i use a winxp source my cd burns one of my XP licenses (just like it was a PC)

so if licensing is the issue, that is addressable, just make sure you have a valid license for each PE disk you have.

If Galapo thinks you can use liveXP... i would certainly try it

thanks for you interest and kind words...  we will see where this leads  keep us 'posted' wink

the hwids tool works on vista... we ahve had reports form users with vista.

perhaps you need to use "run as" to get the proper permission

3,642

(61 replies, posted in Feedback and Support - DriverPacks Base)

if there is a dpinst.log then it did run... how big is the log like 800k or so? (typical for all packs)

since you devices are not installing it might be nice to see the HWIDS perhaps they are not in the packs...

i am begining to suspect that one of our installers that is called by the finisher is still running after teh finisher completes
(running in the background) causeing a file in use error for the delete.

this issue should be resolvved when i fix the backup delete routine with the next release of base...

3,644

(61 replies, posted in Feedback and Support - DriverPacks Base)

were the all of the logs created? (meaning that the exe's all ran)

they should all be date stamped for the time of the run.

mass storage support for ERD is based on you provideing a driver with the oemtext file
we dont use those as we integrate the drivers directly...
so it looks like the mass storage option is out...

it looks as though you could add the network drivers - one at a time.
that doesnt sound like any fun...j

it probably could be done but it will require some more digging around to see exactly what must be done.

the ubcd4win option is easier wink lol

Welcome to DriverPacks SomeGuy

I Dont Know... i got results on googleing "DriverPacks Microsoft ERD"

Most of us use BartPE or UBCD4Win I like UBCD4Win myself it is everything you need in a ERD and more.

http://www.ubcd4win.com/

have a great day

PS i just noticed it had a free download version so ill look at it when i have a sec...

3,647

(61 replies, posted in Feedback and Support - DriverPacks Base)

PS yes there are four log files that are available to you

%SystemDrive%\DP_Install_Tool.log
%SystemRoot%\DPINST.LOG
%SystemRoot%\DPsFnshr.log
%SystemRoot%\setupapi.log

but i am not sure what you would be looking for...

do you have a device taht is not getting installed ???

3,648

(61 replies, posted in Feedback and Support - DriverPacks Base)

first you should see a popup when the packs extract

then
dpinst.exe runs and it logs to the screen (in the blue window several thousand lines and takes a few minutes) .
it will list stuff like:

INFO:   RETURN: DriverPackagePreinstallW  (0xE000020B)
INFO:   Preinstalling 'e:\\d\c\i\xp\e727505.inf' ...
INFO:   ENTER:  DriverPackagePreinstallW
INFO:   Looking for Model Section [INTEL_SYS]...
INFO:   No matching devices found in INF "e:\\d\c\i\xp\e727505.inf"

if you see lines like the above scrolling by it is working !

if the dpinst file wasn't found it would have paused and put a message up like          DPINST.exe doesn't exist
since it did not pause and give an error i can only assume it worked correctly

jeff

Thank you for your interest... and kind words

have a great day and i hope we see you around!

3,650

(61 replies, posted in Feedback and Support - DriverPacks Base)

the finisher deletes the files and creates a runonce entry to delete itself after you reboot - that is normal.

dpinst should have run just before the finisher did... there whould have been a window visible while it ran for a few moments...

i added two debug lines to the cmd file to help you... please use the code below in your DP_Install_Tool.cmd for a test run

DP_Install_Tool.cmd code

@Echo off
REM Written by Jeff Herre AKA OverFlow rev08.04.21
REM A Script to use MicroSofts DPinst.exe with the DriverPacks.
REM Help and Support available at http://forum.DriverPacks.net  
Color 9f

Echo.
Echo Searching current drive for the DriverPacks...
Rem fast detect. (is it the current drive?)
FOR /f "delims=: tokens=1" %%i in ("%~dp0") do SET CDDRIVE=%%i:
IF exist %CDDRIVE%\$OEM$\$1\D goto M1Found
IF exist %CDDRIVE%\OEM\bin\un7zip.exe GoTo M2Found

Echo.
Echo Searching all drives now...
Rem alternate detection. (is it any available drive?)
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST "%%i:\$OEM$\$1\D" SET CDDRIVE=%%i:& GoTo M1Found 
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST "%%i:\OEM\bin\un7zip.exe" SET CDDRIVE=%%i:& GoTo M2Found

Echo.
Echo The DriverPacks were not found ???
Pause
GoTo Done


: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%\

if not exist DPINST.exe echo DPINST.exe doesn't exist on source! & pause

COPY DPINST.exe %SystemDrive%
COPY DPInst.xml %SystemDrive%
GoTo Main


: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!

if not exist %SystemDrive%\DPINST.exe echo DPINST.exe doesn't exist on destination! & pause

%SystemDrive%\DPINST.exe /c /s
Echo.
Echo Running the DriverPacks.net Finisher now!
%SystemDrive%\DPsFnshr.exe



:Done
EXIT