Search options (Page 48 of 213)

Rather than createing a second post here... Which is a no no (crossposting is frowned on here) perhaps you should link to the other post on the UBCD4Win forum

At least if we are going to allow you a crosspost lets put this one in the Mass Storage forum instead of a second one in the PE forum .

Moved

ODD (Optical Disk Drives) Are very slow... the only thing that a ODD is slower at than coping a large file off is copying thousands of small files...

WE have done extensive testing on this... it is actually much faster to extract the archives to the HDD than to copy the uncompressed files off the ODD... Belive it or not we also have recently discovered it is even faster to first copy the archives to the HDD and then extract them.

Try it yourself

extract all the files and burn them to DVD then time a copy to HDD. Compare that to extracting the archives from the HDD. then compare that to copying the archives first to the HDD then extracting them...

We have been doing this for seven years if there were a faster way we would be doing it.

BTW we are going to be making copy the archives to HDD then extract an option (M3)

If you goal is to increase speed? then copying thousands of tiny files off an ODD is not the answer, that is / would be MUCH slower than the current method.
related post / discussion is here http://forum.driverpacks.net/viewtopic.php?id=3323

Again please test for yourself... Post your results if you like

if you run nLite after DriverPacks then you will blow up the DriverPacks drivers - period - don't do that (you realize this already thanks for reading the documentation!)

Yes there is a "fix" however i would like to pint out that DriverPacks does not support "Attended Installations" Repair is an attended install...

there is quite a lot if info on the site if you search for "repair"

let me link you to what you seek

Here is the request to make this a DriverPacks BASE feature... http://forum.driverpacks.net/viewtopic.php?id=2733
the thread that started it and has the "fix"  is here http://forum.driverpacks.net/viewtopic. … 821#p20821
You can read the whole thread if you like but i linked you directly to the pertinent info...

Welcome to DriverPacks

regards Jeff

PS Doing a repair is the worst possable thing you can do to a windows install.
- I would advise you to NEVER do a repair. if your only option is to do a repair, then it is time to backup all the user data and reload clean and reload the user data. the mess that is left behind by a repair is just monumental. think of it as putting a bandaid on a wound that needs 20 stiches.

I used to use rewritables for that but they tend to fail frequently... I just burn DVD's each time now especially since they are like $20 for 100. At the cost of 2 cents each who cares if it ends up as a coaster .

Nvidia nforce drivers have always sucked... some things don't change. See if you can find a RIS driver for it those will generally work well in PE. That is the best suggestion i have until cdob or Hilander999 stops by or until i can sit down with the mass pack and see if i can puzzle it out. again Nforce / nvidia drivers are just the worst POS to deal with. No other drivers are any where near as much of a PITA. They are just very poorly written.

I could guess that in winbuilder the HWID must be associated with the driver in the txtsetup... Just like for windows...
with a DriverPacks slipstream this is accomplished with the mass storage INI file . Often times the list of HWIDs in our INI is very different than the list that is actually contained in the drivers inf... Perhaps that helps you? - In other words you may be able to manually ad the entry to the txtsetup and make it work

from what i can tell PCI\VEN_8086&DEV_27C1&CC_0106 is supported in DriverPack MassStorage 9.01 In folder I3 and should work... ?
More... the specific entries for text mode (what i'll assume is used for winbuilder's Mass support) are referenced / contained in txtsetup (and not in the drivers infs). we populate the txtsetup based on the info contained in the Mass Storage DriverPacks INI file... The drivers  INFs are only used by Plug n Play... BartPE and like kind software (perhaps winbuilder) don't use the drivers inf at all but rely completely on the info in txtsetup alone.

Drivers are installed by HWID. is that devices HWID included in that drivers inf?

IDK how winbuilder works... so i can't tell you how to deal with that issue. They do have a forum for that

code ten means hardware failure (physical)... that may not be the case... but that is what it means.

In other words code ten is not helpful info. more helpful info would be does it work if you use M2 that would indicate that M1 failed. and certain drivers will absolutely fail at M1. Method one extracts and cab compresses the drivers... this may cause errors in certain drivers and since there is absolutely no valid reason to waste the time doing it. Dont do it... (you have given us no valid reason for you to use m1)

Why do you insist on useing M1?

M2 was designed and implemented to replace M1 and it has... M1 was only kept around for backward compatability. since we have been using m2 successfully for over 5 years that makes m1 pretty much retired...

to repeat myself just use m2 and call it a day, unless you have some specific reason to use m1 that you have not revealed to us, as far as you have told us there is absolutely no reason for you to use M1 and since it may cause issues don't do it. simple. Not only that but the extraction and cab compression can take forever to run. (needlessly)

It is a no no to post the link out in the open... Ususally we will enclose it in code tags or in [ URL= link ] packname [ /url ] tags... Since any post here shows up in google in about 30 seconds we don't direct link them. People who are resourceful enough to actually read the forum we figure can handle issues related to alpha/beta releases. Nightly packs are not for the inexperienced - we are not a noob friendly site . I posted a hint in response to his other post / request  "/Nightlies/NT5/".  soporific seems bright enough to connect the dots . This was not done as a security measure there was just too much confusion. people were just accidentally grabbing the wrong nightlies, LOL, so we split them into seperate folders by type (NT5 and NT6) to make it easier. nothing secretive or covert, just a simple matter of re-organization as a result of our growth.

you can PM a link if you like you can even post it here in code tags if you like. Just don't 'Hot link' to them .

PS i was amused that soporific already knows where the nightlies are but could not find the latest mass pack... he's going to smack himself on the forehead when he gets there... DOH!

PSS We want to release DriverPack MassStorage it is just so dificult to get right and so disasterous if wrong... It takes lots of testing and lots of work to get it right it is 10 (maybe 100) times more difficult than any other pack

@tU LOL... noob? you have been here over three years ROFL... Welcome back

That is GOOD! that is what you should see on the plugins page...

I will let you try a nightly pack to see if that works better.

1. Open DPs_BASE.exe and download LAN and WLAN, if you want them, from the updatechecker page.

2. Then add this mass pack mass 9.09.rc6. to the Driverpacks folder (Same place as the LAN and WLAN packs you just downloaded from DriverPacks BASE)

3. Then from pebulder highlight NO # driverpacks.net - BASE. Hit the config button and that will update your plugins, then rebuild, and burn a new iso, and then test and report back. TIA

XP Pro SP2 is the prefered source to use... Excellent! Retail and Corp are mutually exclusive... you have retail...

Tell me this, if you open PE builder and hit the Plugins button (see the tutorial in my signature for pics and details).
Do you see this line?

'Yes # DriverPacks.net - Mass Storage'

Note if you add drivers to the  SCSI folder  you have to disable DriverPacks.net mass storage on the plugins page or your drivers will fail!
This is stated in reverse in the tutorial. IE you have to disable / remove the SCSI folder to enable DriverPacks.net mass storage...

you can't use mass 10.x without using DriverPacks BASE 10.x as well. the last version of DriverPack MassStorage that works with DriverPacks BASE 8.12.x is the 9.07 release candidate