Search options (Page 145 of 213)

nope you should find them in the root folder of the OS drive (typicaly C:\) after running DP_Install_Tool.cmd

IE after running the tool you should have (assumeing C: is %SystemDrive%)

c:\D\
c:\devcon
c:\dpinst.exe
ect...

Which method are you useing? 
$OEM$ extracted / cab compressed
or
OEM   7zipped DriverPacks

please see the tutorial in my signature and read the SAD disk topic in our Frequently Asked Questions (FAQ) forum.
also see the "read BEFORE you post" in my signature.

we do not support products by manufacturer and model. We provide all inclusive packs.
by using our method (nearly) all hardware is supported. if after you use DriverPacks if you find a device that is not included YOU must submit that device (name) with its HWID (tool in my sig), and a link to a known good (working) driver is considered polite.

We do not support the type of request you have made... (I need a driver for a ____...)
please familiarize yourself with the DriverPacks (and use them) and i think you will find your problems are solved
this forum is primarily for support of the DriverPacks - IE if your not useing DriverPacks, no support available.

well the two i was refering to were...

1 Double click on DP_Install_Tool.cmd on the ODD   (Optical Disk Drive ie CD / DVD) {could be your local HDD too}
   - this works with the extracted or cabbed drivers if they are in \$OEM$\$1\D
      (obviously including the OEM\bin\*.* folder  and OEM\dpinst.* and  OEM\DP_Install_Tool.cmd, as listed above)
  - this works with the DriverPacks as downloaded if they are in the OEM folder
     (obviously including the OEM\bin\*.* folder  and OEM\dpinst.* and  OEM\DP_Install_Tool.cmd, as listed above)

2 Double click on the DPINST.exe
    ***NOTE*** this only works if the drivers are extracted to a folder called \D\
    IE  If our ODD (or HDD) is D:\ and has the following layout

    -D:\D\{extracted or cab compressed driverpacks}
     D:\DPINST.exe   
     D:\DPInst.xml

the script looks for either OEM\bin\7zip or $OEM$\$1\D\
if it finds neither it fails and exits. anouncing;

" The DriverPacks were not found ??? "   
   -      implied, can not continue...  -

the finisher does all the cleanup as part of it's function
- if you run it, it will remove all traces of the DriverPacks
and the finisher itself gets removed after your first reboot.

the finisher uses the INI's to identify drivers that have software to be (Co)installed
IE the graphics INI has an entry that runs the ATI control panel
(but only if an ATI card is installed in the machine)

INIU has convienient office hours to review any course related material, even the basics 

it appears to have stalled at adding the mass storage driver entries to the dosnet and txtsetup files.

the only thing that i can think of is that the DriverPack MassStorage ini is corrupted... just my best guess ATM

try this...

edit your  DP_Install_Tool.cmd  near the end of the file add "REM " in front of the finisher line

IE

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

that will keep the finisher from cleaning up (deleteing) the files from C:\
then you could look and see if devcon and DriverPacks Finisher are there
(the packs should also be there in the C:\D\ folder)

PS you can also run the DPINST tool manually by double clicking on it
- after you REMark the finisher line in the script and have run it one time -

we might just get a FAQ for the finisher out of this thread...

my thanks to you since INIU is nothing without its student body...

tutorial in my signature...

you might also take a look at the FAQ section?

7yler...

What can I say
that  is a very strong first post... step up and offer a completed pack to another user.

VERY well done!

Welcome to DriverPacks we are very glad your here and thanks for giving back to the community.

have an awesome day!  and,  Welcome to the forum!

jeff

Good teamwork guys... That is the spirit that "drives" us

LOL    (sorry...) Rofl...

there is a rumor over in 3rd party DriverPack forum that the blue-tooth have multiple standards and were tempermental
and were abandoned as eligeble for a pack...

you should be able to get a single driver in a custom pack though... hmmm

are you sure the exe is getting called?

did you try it without the command line switches?  IE "%DPSROOT%\D\3\BT\setup.exe"
to see if it launched in attended mode?

did you try running      "c:\D\3\BT\setup.exe" /S /v/qn        from a command line?
did you try "%DPSROOT%\D\3\BT\setup.exe" /S /v/qn       from the finisher?
or """%DPSROOT%\D\3\BT\setup.exe"" /S /v/qn" ?
or ""%DPSROOT%\D\3\BT\setup.exe" /S /v/qn" ?
or """%DPSROOT%\D\3\BT\setup.exe"" /S /v/qn" ?

you might add the log switch 
           Logging Options 
                /le <LogFile>
    e - All error messages

IE "%DPSROOT%\D\3\BT\setup.exe" /S /v/qn /le %SystemRoot%\BTinst.log ?

you can run the finisher over and over - simply use the directions for a SAD disk and only put your BT 3rd party DriverPack in the OEM folder instead of all the packs

IE copy your OEM folder to the Local HDD (creating C:\OEM\) delete the main packs... except your BT Pack
and run the DP_Install_Tool.cmd as many times as neccessary till you got it workin

how about that for a shortcut to test the finisher ?

INI University - classes starting daily!

Me three...