Search options (Page 34 of 213)

HWIDs for specific Card that is failing please.

Because we have extensively tested it. Please remember this driver is used for text mode only and is replaced during PE stage with the final PnP driver . (Text mode drivers are used during the PE stage itself.)

Yes BartPE is based on and is very similar to WinPE. That would be the very best place to start. However It is always a good idea to compare it to a Slipstreamed I386 source. We know that our slipstreamed source is 99.9% perfect. if ther are differences (please report them) then the slipstreamed version is more likely to contain the best example.

Answer: Both... lol .

Jeff

DPs_BASE 10.06 Should (and does for me and mr_smartepants) report the local versions and server versions and will offer to update to any latest version available. However if you click "update Selected" you should very quickly get an error message that the download is unavailable (a popup for each pack selected).

If that is not your expereince then you either have a corrupted BASE install or an issue with your machines config... I am guessing a courrupt BASE install.

Hint: Don't click Update Selected - it won't work (at least not until we start getting more than 800 a month in donations, and we have never gotten more than 800 a year in donations... soooo never)

We are working on a two tiered solution:
Tier one Torrents and manual downloads - free
Tier two CDN and automated downloads as has been in the past - donation required.

We simply can not afford to offer CDN to everyone anymore... the ROI for our sponsors is almost nonexistent and we get no donations. Sorry. Everybody wants something for nothing and nobody appreciates what we do and have offered in the past. I must include you in this group here... Not one kind word in your posts, No offer to help, no donation, only a gripe. You wish to complain that the services that we have slaved over for over 8 years and have always provided for free and that you have been using for months has an issue, and don't even say thanks for all our hard work... or mention how much work we saved you. Well I for one am now extreeeeeemely motivated to get right to work on that. 

There is a Beta of BASE out... but feedback from the testing team has been almost non existent, ususally this means it is working fine, but with no feedback there is no release. (people usually only take time to write if there is a problem - hey, weren't we just talking about that...)

The beta version still checks for updates ... all versions do so... but the new version simply opens an IE window to the download page when update selected is pressed and then waits for the file to finish downloading then MD5 checks it. This has more error checking and fail checking code needed now that torrents have been added. because people do silly stuff... like clicking on the download selected button when they already know that downloads have been discontinued...

the problem is that the DriverPacks driver replaces three drivers that windows includes...

each of the three drivers has a unique set of HWIDs... all of the HWIDs are included in a newer driver... so all three drivers must be eliminated from txtsetup so that the newer one can be added. The script you described that you are running will leave two of the drivers behind so all of the HWIDs that are included in those two drivers will be duplicated. If you run into one of the affected controllers it will find the HWIDs in txtsetup twice... That will be disaster...

Yes if you remove the entire section then the primary problem will not occur. However you will be running very old drivers for that hardware... those drivers are for what were at the time high end controllers. If you try to run outdated drivers that MAY also lead to issues. The best thing to do is to have the script properly deal with "a single updated driver that repalces multiple included drivers" Which is what i did in DriverPacks BASE.

Jeff

PS i wrote a very detailed description of the problem above describing it three different ways and citing a specific example.

BartPE may be outdated but it seems like it it miles ahead in mass storage support. that is to say it will not suffer from this issue if you use DriverPacks plugins (currently suporting Mass LAN WLAN and Graphics)

PE2 yeah you got me there ... Give me a minute
But with Dism it is almost a waste of my time to mess with it

Which program?

PE 1 or PE 2?

Restore the backed up copy of the txtsetup file... the program did make a backup of the files it modified didn't it? or at least you did right? If not you will have to start over... The undo would take a lot more time than starting over, no doubt about that.

Always make a backup at each stage of a build .

suggestion:

slipstream DriverPacks into a source, use that txtsetup file and overwrite the corrupt unit. or cut and paste the good sections into your corrupt sections of txtsetup.

The best way to do this is to use a DriverPacks slipstreamed source for your PE build...

Can you tell us more about what you're doing and why... (I just use BartPE / UBCD4Win with my DriverPacks Mass storage plugin, why not do that?)

http://forum.driverpacks.net/viewtopic.php?id=4305

-----snip-----  from testing team forum ... me last year  ----- snip -----

Mass 10.01.24 nightly Jeff aka OverFlow (Jan 24 2010)
Link Retired

updates appplied to JakeLD's 909r6 (1 September 2009)

updated
Replacement drivers that were missing HWIDs
(If a driver is a replacement it MUST replace all HWIDs supported by the previous driver .

dpti2o  [AD4]
- verified

adpu160m [AD5]
- restored hwid
PCI\VEN_9005&DEV_0081

symc8xx [C] ms_1
- need special case for a single driver that replaces two or more native drivers...
- Fixed, simply assign no HWIDs to one or more (ms_X) section(s)
- combined old ms_2 and ms_3 into ms_1
symc810 [C] ms_2
- see above. replaced.
sym_hi  [C] ms_3
- ms_2 is also replaced
-- see section for example!

------- snip ----------  ------------ snip ----------

the replacement driver with NO HWID needs removed becuase it is included with another driver... by adding a driver with no HWID BASE will instead of replacing a native driver, will remove it. This was neccessary because ONE of our DriverPacks drivers replaces THREE windows included (native) drivers. Again... That section replaces three native drivers with one replacement. IE The three windows included drivers symc8xx, symc810, sym_hi were all replaced by CPQ32FS2 and the first section contains all the HWIDS for all three drivers (because they are all supported by the one driver now)

Don't try to figure it out ... let us do that .  I'm not surprized it stumped you... I had a really fun time coming up with a workaround / fix for that.

Thanks for paying attention!

Jeff

UBCD4Win has trouble with some wireless cards ... there are a posts about it on thier forum.

You neglected to tell us this was BartPE related... (please see read before you post linked in my signature) It is critical[ that you tell us what the problem is in order for us to help you effectively. "It works with DriverPacks in windows but not in BartPE" Should have been the very first thing you told us in your first post... [Grrrrr ].

We have a saying around here "Help us to Help you".

Most of the UBCD4Win issues are related to not "Enable"ing the WLAN Pack in the PEBuilder Plugin section

Make sure you have:

Yes   #DriverPacks.net - WLAN, Version# here

on your PE Builder plugins page

Editing your title to correctly reflect your issue

----------edit--------

I now see that the last line in your first post does say not working in BartPE

OOOPS! Sorry! But you did forget to mention it worked in windows

you cant change the folder or the finisher will fail...

End users will have to select a folder other than \D for their stuff if they don't want it deleted with the DriverPacks. We have been using %SystemRoot%\D for almost ten years. This is a LONG established procedure / location. The DriverPacks have always been an unattended solution... adding a user input dialoge is contrary to our goal "unattended" IE no user input. It will be much easier for an end user to select an alternate folder than for us to rewrite the DriverPacks Finisher and DriverPacks BASE and SAD.

Alternate solution 1 is to set the DPsRootDel  = "false" flag. Note:The DriverPacks will not be removed.
Alternate solution 2 is to use SAD with Method 1 (either compressed or extracted) This will install the DriverPacks from an alternate location... Again the DriverPacks will not be deleted or copied. This is an excellent solution for network or USB SAD locations.

FOG the cloneing tool?

Worse than nvidia... WOW that is harsh!

Good find jinkazama

I try to reuse already translated text when i can