Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7) (Page 19 of 22)

Hello!

[OT] Noting that the MassStorage DP you mentioned earlier is from 2013.
http://forum.driverpacks.net/viewtopic. … 591#p57591
Does DP_MassStorage_wnt5_x86-32_1405176.7z not work for you symbios24?

Also, DP_CPU is included in DP_Chipset and is therefore outdated and unnecessary.

Find all latest [Nightlies] via the following Search:  http://forum.driverpacks.net/search.php … =381370028  [/OT]

I advise only integrating the essentials, then utilizing SAD3 for a post-Setup install for the remainder.
This avoids potential problems with path-length.

From the list you posted earlier,

Avoid DP_Bluetooth_MS-Misc_wnt5_x86-32_1408061.7z for now.
I found a detection bug in DP_Fnshr that hangs on MS' XP-included bth.inf (solved - yet to upload though)

DP_Misc_wnt5_x86-32_1308272.7z goes hand-in-hand with Chipset, MS, etc.

The following are likely best installed post-Setup by SAD3:

DP_Biometric_wnt5_x86-32_1403281
DP_Displays_wnt5_x86-32_1109081
DP_Graphics_USB_wnt5_x86-32_1409231
DP_HID_wnt5_x86-32_1209b1
DP_Phone-Mobile_wnt5_x86-32_1409121
DP_SmartCard_wnt5_x86-32_1403281
DP_Sound_USB-FireWire_wnt5_x86-32_1406021
DP_TVcard_wnt5_x86-32_1410071
DP_WebCam_wnt5_x86-32_1410041
DP_wHCI_wnt5_x86-32_1303b1

The following should be installed post-Setup with SAD3 after DP_Bluetooth_MS-Misc_wnt5_x86-32_1408131:
   (see:  http://forum.driverpacks.net/viewtopic.php?id=10848)

DP_Bluetooth_Atheros-Qualcomm_wnt5_x86-32_1408141
DP_Bluetooth_Broadcom-Widcomm_wnt5_x86-32_1408141
DP_Bluetooth_IVT_wnt5_x86-32_1409231
DP_Bluetooth_Motorola-Intel_wnt5_x86-32_1408132
DP_Bluetooth_Toshiba_wnt5_x86-32_1409231

Uploading is horrendously slow here.
It reminds me of my Grandmother's analogy for giving birth.  That is squeezing something the size of a watermelon through an opening the size of a tennis ball.  (ouch!)

Last edited by TechDud (2014-10-08 17:09:15)

Forum Rules & Guidelines   HWID's tool   Unknown Devices (Win7-max) LatencyMon - NT6.x
MemTest86+    Video Memory Stress Test    D-P-C Driver Latency Tester (Win7-max)

i want to put a complete collection of updated driverpacks which ones should i put? and i must use sad3 or the old driverpacks program will do?

its difficult to find new drivers here since i have to search in every post,is it possible to make only one post for new drivers only for any device ?? instead of many different posts?
the link for all latest [Nightlies] its not working can you fix it?

Last edited by symbios24 (2014-10-09 03:50:19)

DP_MassStorage_wnt5_x86-32_1405176.7z is not going to work??

my install finds always a harddrive achi or ide so i just replace the old masstorage pack with the new in this case?? its just the pack  that is over 2 years old

NO!!!
This has already been explained to you several times now.
Don't touch dpms.
The ONLY way to update dpms in your XP install image is to rebuild the entire image from scratch and integrate the new dpms with DriverPacks BASE.
Did you build your own image or was it built by someone else?

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!

Not all heroes wear capes, some wear Kevlar!

symbios24, I suspect the frustration from those trying to help you is because you are not getting the message on how complex the integration of the mass storage pack is and therefore what its doing to your install image. 

Overflow is clearly saying do it one way only....

your way is wrong.

I'm guessing just because you updated it "your way" and seems OK for you doesn't mean your way "works".  Its probably that you have been very lucky and working on really old hardware where its not needed anyway, so you haven't noticed you now have a dodgy image that will crash out if you ever use on other systems/hardware

Last edited by botus (2014-10-12 21:08:14)

Two points,

1) Overflow suggests you probably don't need to update mass storage...  As you say your current image works on yours and other systems.  So for the kit you are working on you don't need to do anything. The only need to update mass storage would be to work with much newer / current hardware.

2) To update mass storage anyway (and from mr_smartepants last post I think he adds clearer advice, and the way I'd do it) you can have a modified image (e.g. where you have added service packs / updates etc.) its just that you should always start from this point and then add driver packs last... and for your project, you will not have full success unless you add mass storage to a previously unmodified by driver packs image

Last edited by botus (2014-10-12 21:17:13)

No.
The whole point of integrating dpms into the XP image with DriverPacks BASE is so that the system can "see" the hard drive at the beginning of the install (known as "textmode").  If dpms wasn't installed properly, the blue install screen of XP would say something like "No hard drives found to install onto".
Simply replacing the dpms archive on the image with a newer one will only provide updated drivers to the system once the XP installer has already began the install process.  Just because you haven't had any errors doesn't mean that it's a bug-free image, it just means that you were lucky.
SAD3 cannot replace DriverPacks BASE for what you need.  SAD3 can only upgrade the drivers AFTER the install has taken place.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!

Not all heroes wear capes, some wear Kevlar!

I told you before ... dp_install_tool has NOTHING to do with installing drivers DURING windows setup. You could REMOVE dp_install_tool.cmd and windows would install the exact same way... <-read that again [no really read it] We put it on there as a convenience to tech's, they can drop in the install disk and update and older machine by running that script. It's an after thought, a freebee, extra, a perk, Icing on the cake, independent, unrelated, unique, never to be used during windows setup ever. It IS to be used on a RUNNING WORKING system.

You are trying to put a square peg in a round hole. Doesn't work that way.

you said you followed all the directions for SAD... And you probably did them perfect.
but since you updated a POST install tool it did not affect your INSTALL.
You did not update your install, and, I know it is hard to belive, BUT it is not updated. Because you never updated it. It's that simple.
I am sure you worked really hard, but you worked on the wrong thing.
Forget what you know, it does not apply to your current task. (second time i told you this)
I would expect nothing different if you did that correctly one thousand times over...
You built a really nice screen door, NO you can not install it on a submarine. Sorry.

Did you download this image off the net?

Until you understand that integrating drivers into an installation is different than updating drivers on a working system we are not going to be able to go any further in your education.

your failure to understand this simple fact is why your windows 7 lite image fails.

pay attention. Stay on point. (we are not talking about Win7 ATM)

I can't cram ten years driverpacks experience into a post, you need to accept that I have 6000 more posts and Admin status for a reason. Been there done that got the t-shirt. I can bet money on your next mistake and nobody would take that bet .

you are doing fairly well so far you got the first half right. answering questions, asking fair questions, you are polite.

the second half of the process here is; now you need to listen, carefully, apply what is given (test advised action) and report back. (Do NOT deviate from specifically given instructions, at least not until I have granted you "the right to run with scissors"... or you are successful)

first half good, second half bad... work on that second half

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

@mr_smartepants You missed an awesome opportunity at a quote pyramid... aaaagh!

I was trying to keep the length down... and gave up. LOL.

after thought... I'm admin, I could still add the pyramid to your post rofl

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

well there's one of your problems!

try a simple search...  Description: TUProgSt.exe is not essential for Windows and will often cause problems

Last edited by botus (2014-10-15 09:04:28)