Search options (Page 53 of 213)

Fixed in DriverPacks BASE 10.x or higher

Hey DD did you ever test my nightly DriverPacks BASE?

We have a testing team, two packs teams, a Main team, a Code team, Etc... and many hidden forums...

Not all Beta / Alpha DriverPacks become releases (we refer to our test DriverPacks as "nightlies").
Many or most of our packs go through hundreds of changes over several months...
Only after a Nightly DriverPack has passed through rigorous testing by several dozen team members and perhaps hundreds or thousands of machines with no reported issues will it become a release. Most nightlies are never released. We only release proven to be stable and working DriverPacks, most packs never pass muster, and are not released

You can't just dump a bunch of drivers into an archive and post it on the web, at least not if you want the drivers to install properly. Adding Drivers to a Pack is a tedious and very time consuming process, and no pack is harder to update properly than Mass Storage .

Since Mulgie is a Donor he automatically gains testing team access... There is Much that goes on behind the scenes that is not visible to regular members, as a matter of fact most of our posts are in the hidden team forums. So I pointed Mulgie to that pack knowing he also has access to the thread in the team forum that corresponds to it... So I could get some feedback .

Short answer... Mass storage is not ready for release yet, and that update is not important to what we are working on with DriverPack MassStorage ATM .

Good question.

3rd party DriverPack is a good server

Dude!!! Wazzzaaapppp!

I think the corrupted pack was the issue this time...

MD5 check-sum verification is 99.99% done in my local copy (head revision)..., at least for downloads done directly from DriverPacks BASE
mr_smartepants got a sneak preview yesterday .
IDK if i will even attempt to implement MD5 further checks...
IE for selected packs that are already on the local machine.
That is possible, but IDK if it is worth the effort to code... (Jeff scratches his head and shrugs)
Bad DLs are not an issue that is reported very often. Simple CDN has eliminated most of those issues for us !

I think he means my link to the other thread,
the one where I cleaned up this thread and moved all the unrealated "hijack" posts too
But I could be wrong...
Perhaps he meant he is grateful that we share our forum with wonderful people like you .

again you should not need to update any DriverPacks... it should work without any updates...

What versions did you use to update DriverPacks with?

the log may have to be split into two or three posts... or you could just snip the relevent part out and post that...

As stated in that thread you pointed to...

cd %systemroot%\system32
DEL /F setupold.exe

hitting <Shift> <F10> should bring up a CMD window

DriverPacks can be updated... as long as it was the LAST step in your process. (no changes after DriverPacks )

you said yourself that it worked

this is a built in function of DriverPacks BASE

that should work right out of the box..

clean  source with default ubcd4win settings

please visit the Frequently Asked Questions section of our forum. Take a look at SAD (Stand Alone Drivers) a feature of DriverPacks BASE and the DriverPacks.