Search options (Page 149 of 213)

RE:  it downloads them and installs them with dpinst

um if chipset and LAN drivers are not installed hoiw will you access the net?

you could have searched for - S.A.D. makes us happy

but here is the description / how to...

http://forum.driverpacks.net/viewtopic. … 159#p20159

Have a great day and welcome to the forum

PS (it is stickied in the FAQ forum... please at least attempt to find stuff on your own)

It is not looking like a land-slide yet...

according to the news page we get 32 thousand downloads a day - on average
Less than a handful of people interested enough to post.
I do realize those votes could represent hundreds or thousands of other users
but if they wont even say hello, like this idea, and thanks for being here... shame on them

So it's enough interest to make it on the list, just not as a priority item -
they do say good things come to those who wait...

re: (Why a plugin and not as a driver? )

remember ubcd4win and all bartpe projects are running off of a read only media. we cant update those files on the fly like we can in windows. so all of the files that reference the driver files must be updated in advance. this is done by pebuilder during the build process. if there is no plugin inf how is pebuilder to know it has something to get done?

think of teh plugin as a to do list for pebuilder - if you want a driver added you have to create a todo list for it.

so the answer is The plugin IS the driver.

as far as why the tape doesnt show up is ther is no PnP in BartPE the devices are detected on boot (setup (PnP) never runs) so it detects the controler because it is reported by bios and referenced in the correct windows files.
since we are not runing windows install a second pass is not made to detect child devices that are connected to primary devices.

if you want to detect child devices you must manually click on search for hardware ( There are a couple of shortcuts to do this from the start menu in UBCD4Win ) perhaps you could put a shortcut to the search for hardware in teh "all programs\startup" folder ;) taht would force a second detection.

Looks like you have been doing youir homework - very impressive - good job

have a great day and thanks for keeping us 'posted'  :D

PS oemtext files are for support of Bootable mass storage controlers and since you can't boot from DLT...  ;)

it is not unusual for a device to look strange in device manager in bartpe.

the only thing that truely matters is "does it work?"

PE is not a replacement for windows we dont need it to be pretty, just functional

could you check my signature for some helpful links.

I couldnt find any info about what pack versions and DriverPacks base version you had used in the post above.
the HWID's are quite helpful Thank You for those! yay.

if you havent used DriverPacks perhaps you could search our forum for "SAD disk" and read the posts at the end of teh stickied topic about our script and updateing a machine post install with DriverPacks

it is a simple update so i think we can add it...

and it would speed up the process too

please read the tutorial both included in base and linked in my signature especially titles and bold print

there is also a forum here just for BartPE. Please at least glance at the Stickied threads for some highlights.
I am also moving this topic to that forum.

Check out the sticky in the feature requests "To Do list" and the recent news on our home page.
the search feature works great and almost any question you may have is already answered here probably in great detail. please take a moment to look around and familiarize yourself with the basics and let us know if you have any more questions.

Thanks so much for stopping by an letting us know it is working for you and asking a good question and provideing good details about what your doing. It always makes it easier to help.

also please check out the sticky i link to in my post called 'read before you post'

Have a Great Day and Welcome to DriverPacks

cross posting and double posting are not allowed this is also in the wrong forum as was the other post i moved already.

Thank you... 

other post  http://forum.driverpacks.net/viewtopic.php?id=2912

First post updated

edited the Title wording and added [BUG] 
I clarified the first line of the post to reflect the issue clearly.

no...

He is right there is a bug in the code. (haven't seen one of those in a long time )

But there is something odd about it. The finisher deletes the files before the reboot, however, it does place a runonce entry to double check that the D\ did get deleted and if it finds that it was not it then attempts remove it a second time. This happens at the same time as the finisher itself is deleted from runonce.

so to find this bug the finisher must fail to delete the files before the reboot and the backup removal must be needed. Since the error is related to a backup system it would indeed rarely surface, but is still a bug. This make me ponder the 'why' of the primary delete from the finisher failing. that is what relly intrigues me is WHY did the primary system fail that led us to the bug in the backup system?

I think this will probably get added to 8.06 and make it 8.07...