Search options (Page 110 of 213)

OK since Helmi to care of most of my issues with this guy (TY Helmi)

I am only going to add this... We are not on a high horse nor other lofty place.
We do average 32,000 downloads a day. (Yes that is Thirty Two Thousand)
(not counting the downloads that are included with UBCD4Win)
So why is it - if we have Millions of users you are the ONLY one with a problem. ???
You are welcome to go through all of our posts dating back over 5 years here and on MSFN.
Please notice that you are alone on your perch and we have millions of supporters (a month)...
which of us is on that high horse? I assure you the attitude problem is on your side...

furthermore the BartPE; Graphics, LAN and WLAN features are a RC features of DriverPacks BASE.

If you were not such a PE noob it would not have taken you so long to fight this issue.
Anyone who has any experience with UBCD4Win at all knows PE uses VESA support for graphics drivers.
- I suspect you are young and unfamiliar with VESA (and manners). 

Just because DriverPacks BASE will do something does not mean you should do it...
You went off on a tangent trying to fix something that does not need to be fixed.
You then failed, because of your lack of experience and failure to do the neccessary research.
Then you thought it would be a good idea to blame us.
Then you attack the two most likely candidates to offer you help.
Your failings and lack of experience are not our fault.
   or  Guns don't kill people / Someone has to pull the trigger )

The bottom line is the only card manufacturer who does not support the VESA standard is Intel.
The ONLY video card drivers you need to complete your UBCD4Win build are Intel... the others are optional.
There will be an intel only button in a future release of DriverPacks BASE... as I stated all but mass are RC features of BASE for BartPE.
In the near future you will be able to just select a box for 'Intel Only' as an option in DriverPacks BASE.
Again it is not our fault that you did not know that all video cards support VESA directly (Except Intel) and therefore don't need drivers for UBCD4Win.

So you are mad at us because you chose to waste your own time and you did so without doing the proper research first.
I just don't have words for that depth of ignorance. Unlike my gracious friends I don't give second warnings - be nice or be gone.

my suggestion to you is
prune DriverPack Graphics C down to Intel only and use that

Had you been Clear (detailed) and Nice we could have just told you that
As I wrote * 5. Tell us what you did - Could we try to reproduce your issue ourselves just based on your first post?
Clearly the answer to number five is no... is that also our fault
or another glareing example of your failure to do the proper research or provide Clear and Detailed Info?
(IE what version of UBCD4Win)
Truely it is better that my freinds got here first, I would not have been so gracious.

Jeff

PS I assume (since you don't seem to be big on research and finding things on your own) that you did not know that you need to remove the \drivers\Net folder from your UBCD4Win folder if you add LAN and WLAN with DriverPacks BASE.

PSS No control panels in UBCD4win...
You can't run an installer on a ROM and is why the finisher and related control panels are disabled, they won't run successfuly.
Please remember BartPE is a sideline here, our main user base is Unattended installations. the files you thought were unneccessary are quite neccessary for a normal install. They are not copied to your plugin either. (Oh and while I am thinking about it, just because two files have the same name does not mean they are identical...)

if you use driverpacks the repair option is disabled... because if we don't then you will not have an unnattended installation.

We do not support Attended installation (Repair is an attended installation)
There is a way to enable the repair option, and it is well documented in many places on our site...

You MUST be aware that makeing the changes that enable a repair will cause your Unnattended Install to Hang...
Thus making it an attended installation... One or the other - you can't have both.
You will either have an attended install with repair option... or... an unattended install without the repair option

Either or not both! (I hope this is VERY clear!)

in order to enable the Repair option you must remove the entire [Unattended] section from the Winnt.sif file
if the unattended section (even if it is only the [Unattended] line itself) you will NOT be prompted for repair.

If you remove the [Unattended] section some drivers will hang your install with driver signing warnings... sorry about your luck. This is by Microsoft design and is not a flaw in either nLite or DriverPacks.

As I stated One or the other not both either Unnattended or Attended
- Repair is an attended install, nothing we can do about it so if you remove the unattended section don't come back crying that it now stops for user input for certain drivers... We already know that it will, and it is supposed to.

furthermore Attended installs are not supported by DriverPacks... (You're on your own if you do this)

DO NOT USE nLite AFTER DriverPacks. This WILL Corrupt your Source PERIOD.
To be clear running nLite AFTER DriverPacks absolutely will destroy your source!

Remove the [Unattended] section manualy!  Use notepad or whatever and burn the disc, No other changes!

Still unable to reproduce the error... except once when you first reported it...

I can't fix it if I can't reproduce the error...
But I Know it does exist since I have seen it myself! (although only once)

Try redownloading everything and see if it goes away

If you create a new folder and redownload all the packs and it still does it post your DPs_BASE.log TIA

we don't know... you tell us.

Please read "Read BEFORE you post" in my signature below, and the BASE tutorial.

Then submit a properly detailed post. TIA

PS downloading the packs is now an option in the BASE program itself eliminating the need to do this manually

if it helps a handful of people then it is worth it and it is easy enough to do...

Is the tool copied even if the error is reported?

it may be that disc caching is delaying the write

IE the check to see if the copy is successful occurs before write caching finishes the actual disk write

The code is like this

write file...
Check to see if file was written

it may need a pause...

write file
pause
check to see if file was written

I was able to reproduce the problem when he reported it and have not been able to do since...

There is a bug... but it is difficult to fix it when i have only been able to reproduce it once

As a side note you can simply put the 3rd party DriverPack in the OEM folder with a 8.3 compliant name for the moment!

Got it.
That hilander999 Dude rocks!

HWPNP by paraglider! www.paraglidernc.com

also needs a device manager
http://www.paraglidernc.com/plugins/updatedevices.htm or
http://www.911cd.net/forums//index.php? … mp;hl=mmc*

For wireless you will also need this...
http://www.drowaelder.de/winpe/PEIndex.htm
http://www.drowaelder.de/winpe/Wireless … reless.cab

My Thanks to John!

I just put in a call to highlander for the names of the required plugins
I'll respond here when he calls me back... Be sure to 'subscribe' to this post for the answer!

PS only the Intel graphics drivers are required (Which means you could prune DriverPack Graphics C down to just intel)
Because all the other graphics cards support VESA and don't actually require drivers
Although there may be benifits to useing PnP graphics drivers in certain cases...
It was recomended by the UBCD4Win team to include an 'option' in BASE to build the Graphics plugin with only Intel for this reason... I intend to make this a BASE feature in an upcomeing release

Thank you for posting...

Please read before you post in my signature...
You failed to mention which DriverPacks BASE version and sound pack version you used...
You failed to mention the HWID of the device that did not install.
You failed to post your DPs_BASE.log in code tags.

and we will not use drivers from rapid share or the like.
A link to the driver directly on the OEM providers site is required
(toshiba in your case, or the chipset providers site is also acceptable).

Welcome to DriverPacks, we look forward to assisting you.