Search options (Page 146 of 213)

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

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

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...

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)

yes the tag must be 8.3 compliant

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.

i second useing a sp3 slipstreamed source as a possable fix

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

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

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...

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 lol

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 ???

Thank you for your interest... and kind words

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