i hav succesfully used my unattended/driverpacks dvd on 2 dell desktops. is there a reason why the drivers for video, modem, lan wouldnt get paicked up on a laptop d830? i have exclamation points in device manager. thanks

brute force wrote:
OverFlow wrote:

that should cause all the files to arrive in c:\
- yes i belive we tried this and it should work... wink

DOES it work when you run the tool / script from c:\OEM\ ?

(you can watch it run or use the "pause" technique - IE rem the finisher line in the script)

no, right now it is saying that dpinst deosnt exist in destination. im running it from C:\oem

this is getting ridiculous smile. i followed instructions in the original post. what is wrong here?

OverFlow wrote:

that should cause all the files to arrive in c:\
- yes i belive we tried this and it should work... wink

DOES it work when you run the tool / script from c:\OEM\ ?

(you can watch it run or use the "pause" technique - IE rem the finisher line in the script)

no, right now it is saying that dpinst deosnt exist in destination. im running it from C:\oem

OverFlow wrote:

now i know what is wrong!!! woo hoo...

run DP_Install_Tool.cmd from the CD/DVD and let the script copy the files to the HDD
or run the DP_Install_Tool.cmd from c:\OEM\DP_Install_Tool.cmd after your manual copy. ps this is not neccessary - to copy manualy to the HDD - but will work just fine...

that should cure your problems big_smile

didnt i do this already via your previous post? i copied manually the OEM folder from the DVD. then i ran the dp install tool from the oem folder on C:\

brute force wrote:
brute force wrote:
OverFlow wrote:

not all the files are being copied... hmmm

does OEM\DPINST.exe exist?

as i was responding i see the packs went to D folder but i went back to the command windows and nothing installed since it didnt find dpinst.exe

i copied the whole folder (OEM). why didnt dpinst go over. im investigatng

i just did it again. packs come over to C:\oem (where i copied the d:\oem folder) and i get the same dpinst.exe doesnt exist on destination error. but i look and dpinst.exe is in my c:\oem folder. what is going on here?

brute force wrote:
OverFlow wrote:

not all the files are being copied... hmmm

does OEM\DPINST.exe exist?

as i was responding i see the packs went to D folder but i went back to the command windows and nothing installed since it didnt find dpinst.exe

i copied the whole folder (OEM). why didnt dpinst go over. im investigatng

OverFlow wrote:

not all the files are being copied... hmmm

does OEM\DPINST.exe exist?

as i was responding i see the packs went to D folder but i went back to the command windows and nothing installed since it didnt find dpinst.exe

OverFlow wrote:

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

method 2
OEM 7zipped

the files are in the root of c:\  except for dpinst.exe. not there. i dont see it in c:\windows either

brute force wrote:
OverFlow wrote:

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

i did the REM and the D folder has many folders. but i dont see the files you are talking about in the root of \D. are they somewhere else?

to be clear, the packs are there but i dont see any executables for the finsher and devcon, unless they are in another folder.

10

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

OverFlow wrote:

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

i did the REM and the D folder has many folders. but i dont see the files you are talking about in the root of \D. are they somewhere else?

11

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

OverFlow wrote:

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

ok, i will try that.

ps you should know that i have always been running dpinst tool manually since it is a cd only drivers disk (i dont do this on my automated dvd disc). what other way were you thinking i was running it. just want to make sure you knew that because if there is another way, let me know and i will certain ly try it

12

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

OverFlow wrote:

if they are there ... hmm then it would seem that they are not being copied to the system drive
( C:\devcon  did not exist when the finisher ran)

but it looked like that dpinst.exe found all the packs and ran your hardware against them.

IE - the drivers should have been updated, even if the finisher was missing a file or two.

why wouldnt devcon exist? is it possible that my windows only install is the problem and because of the hardware, devcon is not coming over? i know i have 4 bit graphics on that and i had never seen it that low. maybe something is wrong there? maybe my windows only cd is not good?

13

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

OverFlow wrote:

well i have a clue already since it says that the devcon and the INI are missing i must assume that you didnt copy the OEM\bin\ folder to your disk.

you must have all files and folders from the OEM folder present, not just the packs.

we need the following files (at least)

-OEM
     -BIN
       7-zip32.dll
       DevPath.exe
       DPsFnshr.7z
       DPsFnshr.ini
       un7zip.exe
DriverPacks (One or All) 
DPINST.exe
DPInst.xml
DP_Install_Tool.cmd

thats  not it. all files there

14

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

brute force wrote:

hi overflow.

tried to email you and i still get the same error message about 64kb limit


OverFlow wrote:

an excellent observation... good eye, and nope, that is normal in both cases tongue

email me if you like (link in my signature) i will cut and paste anything pertinent here...

here is the link. you can download it from here

http://www.esnips.com/doc/2f816151-9d76 … ST_dell260

15

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

OverFlow wrote:

an excellent observation... good eye, and nope, that is normal in both cases tongue

email me if you like (link in my signature) i will cut and paste anything pertinent here...

here you go overflow. it will take a few posts

2008-08-08 08:27:25 : <INIT> DriverPacks Finisher 8.05 initialized.
2008-08-08 08:27:25 : <INIT> Splash screen initialized.
2008-08-08 08:27:25 : <INIT> Detected platform wnt5_x86-32.
2008-08-08 08:27:25 : <INIT> Start logging of system variables available for use by the exceptions:
2008-08-08 08:27:25 : <INIT>     %finisherdir% = C:
2008-08-08 08:27:25 : <INIT>     %systemdrive% = C:
2008-08-08 08:27:25 : <INIT>     %systemroot% = C:\WINDOWS
2008-08-08 08:27:25 : <INIT>     %windir% = C:\WINDOWS
2008-08-08 08:27:25 : <INIT>     %programfiles% = C:\Program Files
2008-08-08 08:27:25 : <INIT>     %dpsroot% =
2008-08-08 08:27:25 : <INIT>     %dpstmp% = C:\tmp
2008-08-08 08:27:25 : <INIT> Start logging of the HWIDs for relevant devices present in this system.
2008-08-08 08:27:25 : <INIT> devcon.exe not present: no HWIDs can be logged.
2008-08-08 08:27:25 : <CRIT> Could not find settings file!
2008-08-08 08:27:27 : <CLNP> Added new value to the RunOnce key in the registry: the DriverPacks Finisher itself will get deleted after the next reboot.
2008-08-08 08:27:27 : Program terminated.
===================================

16

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

ok, Helmi

i didnt want to flood the forum with these type of posts

i guess there is no way for me to attach these ini files?

Helmi wrote:

Yeah, emailing will not make that error vanish.
It's not so much an error, btw, but more a forum limitation.

You can try splitting up the file to smaller pieces and posting each in a new post to make it fit.
Just use a proper editor (Notepad++ or Notepad 2) and keep the character count below 64000 [^=64KB].

17

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

hi overflow.

tried to email you and i still get the same error message about 64kb limit


OverFlow wrote:

an excellent observation... good eye, and nope, that is normal in both cases tongue

email me if you like (link in my signature) i will cut and paste anything pertinent here...

18

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

i just realized that the finisher starts after a reboot on my unattended dvd. on my cd version, i never see a reboot. anything helpful here?

19

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

i figured i'd send you these two files. there doesnt seem to be a way to attach files in this forum i went to paste the files here.

but driverpacks.net is telling me that posts can't be longer than 64kb. how do i get these files to you

dpinst.log and dpsfnshr.log files

20

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

ok. there is no DP_Install_Tool.log

goes thru the motions and then nothing

21

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

ok, thats what i thought. it doesnt make sense. i must be doing something wrong. probably something obvious

i will get you the DP_Install_Tool.log


OverFlow wrote:

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 )

22

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

here you go. thanks again. i ran this on the troubled computer we are talking about

this is really frustrating. this whole thing doesnt make sense. i hope you can figure out what im doing wrong


===========
PCI Devices
===========
PCI\VEN_8086&DEV_100E&SUBSYS_002E1028&REV_02\4&3B1CAF2B&0&60F0: Ethernet Controller
PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_81\3&172E68DD&0&F0: Intel(R) 82801 PCI Bridge - 244E
PCI\VEN_8086&DEV_24C0&SUBSYS_00000000&REV_01\3&172E68DD&0&F8: Intel(R) 82801DB LPC Interface Controller - 24C0
PCI\VEN_8086&DEV_24C2&SUBSYS_01261028&REV_01\3&172E68DD&0&E8: Intel(R) 82801DB/DBM USB Universal Host Controller - 24C2
PCI\VEN_8086&DEV_24C3&SUBSYS_01261028&REV_01\3&172E68DD&0&FB: Intel(R) 82801DB/DBM SMBus Controller - 24C3
PCI\VEN_8086&DEV_24C4&SUBSYS_01261028&REV_01\3&172E68DD&0&E9: Intel(R) 82801DB/DBM USB Universal Host Controller - 24C4
PCI\VEN_8086&DEV_24C5&SUBSYS_01261028&REV_01\3&172E68DD&0&FD: Multimedia Audio Controller
PCI\VEN_8086&DEV_24C7&SUBSYS_01261028&REV_01\3&172E68DD&0&EA: Intel(R) 82801DB/DBM USB Universal Host Controller - 24C7
PCI\VEN_8086&DEV_24CB&SUBSYS_01261028&REV_01\3&172E68DD&0&F9: Intel(R) 82801DB Ultra ATA Storage Controller - 24CB
PCI\VEN_8086&DEV_24CD&SUBSYS_01261028&REV_01\3&172E68DD&0&EF: Intel(R) 82801DB/DBM USB 2.0 Enhanced Host Controller - 24CD
PCI\VEN_8086&DEV_2560&SUBSYS_00000000&REV_01\3&172E68DD&0&00: Intel(R) 82845G/GL/GE/PE/GV/E Processor to I/O Controller - 2560
PCI\VEN_8086&DEV_2562&SUBSYS_01261028&REV_01\3&172E68DD&0&10: Video Controller (VGA Compatible)
12 matching device(s) found.

===========
USB Devices
===========
USB\ROOT_HUB\4&28FEF180&0                                   : USB Root Hub
USB\ROOT_HUB\4&389651E0&0                                   : USB Root Hub
USB\ROOT_HUB\4&5E88044&0                                    : USB Root Hub
USB\ROOT_HUB20\4&36326108&0                                 : USB Root Hub
USB\VID_0461&PID_4D15\5&2F6F8AF0&0&2                        : USB Human Interface Device
USB\VID_0951&PID_1607\5B8517000F2C                          : USB Mass Storage Device
USB\VID_09AE&PID_0002\USB_COMPOSITE_DEVICE                  : USB Composite Device
USB\VID_09AE&PID_0002&MI_00\6&8FA055B&0&0000                : USB Human Interface Device
USB\VID_09AE&PID_0002&MI_01\6&8FA055B&0&0001                : USB Human Interface Device
USBSTOR\DISK&VEN_KINGSTON&PROD_DATATRAVELER_2.0&REV_PMAP\5B8517000F2C&0: Kingston DataTraveler 2.0 USB Device
10 matching device(s) found.

=============
Input Devices
=============
HID\VID_0461&PID_4D15\6&2557F44&0&0000                      : HID-compliant mouse
HID\VID_09AE&PID_0002&MI_00\7&38484CD1&0&0000               : HID Keyboard Device
HID\VID_09AE&PID_0002&MI_01\7&FDD9F08&0&0000                : HID-compliant mouse
3 matching device(s) found.

============
ACPI Devices
============
ACPI\FIXEDBUTTON\2&DABA3FF&0                                : ACPI Fixed Feature Button
ACPI\GENUINEINTEL_-_X86_FAMILY_15_MODEL_2\_0                : Intel(R) Pentium(R) 4 CPU 1.80GHz
ACPI\PNP0000\4&11876118&0                                   : Programmable interrupt controller
ACPI\PNP0100\4&11876118&0                                   : System timer
ACPI\PNP0200\4&11876118&0                                   : Direct memory access controller
ACPI\PNP0303\4&11876118&0                                   : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
ACPI\PNP0401\4&11876118&0                                   : ECP Printer Port (LPT1)
ACPI\PNP0501\1                                              : Communications Port (COM1)
ACPI\PNP0700\4&11876118&0                                   : Standard floppy disk controller
ACPI\PNP0800\4&11876118&0                                   : System speaker
ACPI\PNP0A03\4                                              : PCI bus
ACPI\PNP0B00\4&11876118&0                                   : System CMOS/real time clock
ACPI\PNP0C01\1                                              : System board
ACPI\PNP0C01\B                                              : System board
ACPI\PNP0C04\4&11876118&0                                   : Numeric data processor
ACPI\PNP0C0C\2&DABA3FF&0                                    : ACPI Power Button
ACPI_HAL\PNP0C08\0                                          : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000                                          : ACPI Uniprocessor PC
18 matching device(s) found.



Helmi wrote:
brute force wrote:

besides pointing to the link in your signature, if i had to do something with the HWID tool, you didnt elaborate on what to do with the tool. i know it gives me the HWID's, but what then

Then you post 'em here so we can check 'em out! wink

23

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

yes i saw that. but that doesnt answer/explain my question:  why wouldnt the HWIDS be in the packs. my dvd works fine and i just copied the files from my xp source folder and followed the directions in the sticky.

besides pointing to the link in your signature, if i had to do something with the HWID tool, you didnt elaborate on what to do with the tool. i know it gives me the HWID's, but what then

thanks


OverFlow wrote:

HWID's tool is in my signature below wink

24

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

ok, but why wouldnt the HWIDS be in the packs. my dvd works fine and i just copied the files from my xp source folder.


OverFlow wrote:

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

25

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

sorry. setupapi.log is there.

the only one not there is the first on on your list

OverFlow wrote:

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.