Search options (Page 52 of 213)

nope MD5/CRC are not a function of un7zip that is why we post the MD5 hashes

the nightly version of DriverPacks BASE will check the MD5 if a pack is downloaded with DriverPacks BASE...

I suppose it is possible to run an MD5 hash on the packs that are already downloaded but it would still have to be done as a function of the update checker and an Internet connection would be required.

This would have no effect on packs after they were slipstreamed... IE if the packs were corrupted when copied to an ISO or ODD... nor during extraction when DriverPacks is installing

I am not sure if this is worth the extra time to invest given that ultimately the final stages can't be verified (during install).

thoughts / Ideas?

hmm that is strange all that should be gone... the last part of the DPsFnshr.log should tell us what happened...

http://www.sapphiretech.com/presentatio … x?psn=0006

please tell us which one works for you IE ATLANTIS SAPPHIRE 9600

access granted... new forum is now visable to you

Welcome to the team!

Jeff

PS please remember nightly packs are not for production / release - testing only please

I hope DriverPacks solution does likewise for you

did you make sure that the first entry in the DevPath registry entry was %SystemRoot%\inf?
I have seen cases where that entry was missing... that could cause strangeness
are the rest of the DriverPacks folders present? that could be an issue too.

did you use M1 as i suggested? extracting rather than cabbing them all?

One of your fellow "crazy SysPrep guys" may have some insight on this too

tutorial linked in signature

Yes you missed something... You forgot to mention which version of BASE you were using... Looks like 10.04.01

This issue is related to upgrading from DPInst 2.01 to DPInst 2.1 the error was recently reported and the fix has not yet been found...
Please only use official releases for production applications, nightly versions are for testing only

It is very important to provide good details if you want good support .
Please refer to "Read BEFORE you post" in my signature.
IE 4. Choose a good topic title. - Don't forget to MENTION the relevant DriverPack (or DriverPacks BASE) and its VERSION in the TITLE.

If you use BASE 8.12.5 you won't have this issue
Remember you can't use mass 10.x with BASE 8.12.5... Use Mass 9.01 first
- Only if DriverPack MassStorage 9.01 won't work then try 9.09.r6 (in / from the 'old' folder) It is the last nightly that will still work with BASE 8.12.5
- If you are using OLSP then it may not matter... but to be safe, even with OLSP, I recommend sticking to 909r6 or less

well there is a docs link on the home page... did you try that?
every one of the team members has a link to a tutorial in their signature...
We do have a FAQ's section too
and a Feature Requests, and here (Feedback and Support - DriverPacks Base)
all good places to start / look.
Since we have been doing this for 7 years it is doubtful if you will find something that is not already covered... in great detail.

AutoImage by RogueSpear does DriverPacks with network installs... So support for that is in place already

DriverPacks BASE includes a platform we call SAD (Stand alone Drivers) which uses dpinst.exe...
(a normal DriverPacks BASE slipstream does not use dpinst.exe - only SAD does)

never run nLite (or anything else) after DriverPacks - That is plastered everywhere.

Looks like you did everything the hard way...
but hey, it's a good learning experience.
I am impressed and that doesn't happen often.

There have been a dozen or more releases of BASE since 8.12.5, just not public releases.
So technically no, you are not up to date. (From my perspective)
Um dutch... good thinking, but not the problem. The window was simply to small for the text, NBD.
Much of our work is never released. Only 100% fully tested bug free work ever gets published.
We have a huge testing team, all work must pass our team testing first.
thanks for your offer to teach me and provide details... IDK how I managed to get by before you got here LOL.

Off topic is no prob... we love off topic .

why do you remove method 2 if you only slipstream mass storage... you must really be screwing things up.
Because if you only slipstream mass storage textmode then M2 will NOT be installed... WTF are you really doing?
(If you read "Read BEFORE you post" AKA Rule #0 linked in my signature you would have known to include your DPs_BASE.log and would have answered that last question...)

you inject the drivers? you mean with nLite? ROFL

You avoided rewriteing... every step listed is a rewrite (confused).

MSFN ROCKS!

M1 retired forget it
M2 only way to go.
SAD - Stand Alone Drivers (Is for software first installs only. BUT it is added during slipstream to your source, just in case you need to use your disc to update a machine at any time... say during a service, or if you add a device to an existing system. It is not used during an install. it is only there to add functionality to your disc, IE you want to update drivers on a running system.)
BARTPE... self explanatory

recommended method.

RVMI or Hfslip, since you use dutch please consider Serebys. Add SP, Hot-Fixes, and updates. (Backup source)
nLIte automate setup - slim down is not recommended, it's going to end up on a DVD anyway CD's are dead. NEVER REMOVE DRIVERS.
leave nLite open at create ISO page (Backup source)
Run DriverPacks BASE M2 with all desired main packs and 3rd party DriverPack for Physx, language and .net runtime if you desire them.
after DriverPacks BASE exits then return to nLite which is still open at create ISO page and... your done (backup source)

If you want a network install or to simply script all the above steps this can be done with RogueSpears AutoImage. Done.

You already found MSFN... that is the best source of info for a beginner that there is .

Please submit the update to the bugtracker either the current translator will pick it up or i will - Thanks for the offer and the kind words

Jeff

PS can you test the nightly? (do you still have the notebook?)

haven't had a chance yet... normally JakeLD does Mass and he has been too busy... I only did mass last time to fix a bug that was reported in DriverPacks BASE. It was neccessary to correct a flaw in mass to achieve the fix.... Since most people can update mass and only I can update DriverPacks BASE i try to spend my limited amount of free time on the DriverPacks BASE code.

There is a nightly version of chipset up... sometimes conflicts in chipset will affect mass storage especially with those POS nvidia MB drivers.

We used to like this routine... screenshot a desktop and then set it as the desktop background. Then move all the desktop shortcuts to a temp folder, and move the taskbar to the top or right hand side then minimize it and turn on auto-hide. None of the "shortcuts" will work and neither will the "start button". especialy if the keyboard does not have a windows key or if it is disabled.  This was always good for a laugh... the best part is even if they power it off and back on the problem persists .

shell=progman.exe is also a nice gag

mulgie reported that the latest packs fixed his issue...
- If you use the latest nightly mass storage pack then you MUST also use the nightly version of DriverPacks BASE with it.
- - you will notice the 10.x link I posted is to the nighly packs location
    - those packs are intentionaly not linked from the home page or out in the open.
      They are always embeded in code tags or URL tags,
      While the nightlies are not a secret they are not for everyone,
      they may (probably) have issues and we prefer that only advance users who are capable at trouble shooting use them.

can you tell us if the new chipset pack fixes yours too?

If not please see 'read before you post' linked in my signature and provide the required minimum details.
If you hurry I am between DriverPacks BASE updates and have a little time to fool with mass storage (a rare opportunity).

PS These users are reporting a 6b chipset error... which has been reported above as fixed with the new chipset pack.

You seem to be reporting a 7b or related error which is mass storage, these are not the same thing at all... If I followed you correctly.
(Silly mulgie put a chipset issue in the wrong forum )

Please test and report,
Smart questions (like yours) are always welcome.

Welcome to DriverPacks.

Jeff

PSS I noticed in your other post that you are using SAD M1 on a network share.
Please only use M2 on network shares, otherwise chipset and network drivers will fail.
(sucks when you get disconnected from the network in the middle of updateing your network driver, and the rest of the driver which is on the network is no longer accessble. M2 makes a temporary local copy )