mr_smartepants wrote:That must be because of the BartPE plug-in you're using.
On your BartPE installs, does the DriverPacks Finisher run during GUIRunOnce or RunOnceEx? If so, then you can easily trigger the control panel install for ATI by adding an empty text file to your source OEM folder and rename it ATICCC.ins or ATICCP.ins.
Aye, but I don't want the control panel. That's what was pissing me off. It looks like parts of it were getting thrown in there anyway.
And oh boy, looks like I have another high-horse to kick in the knees. Anyone that "TY"'s Helmi has got their head in the wrong guy's ass.
OverFlow wrote:I am only going to add this... We are not on a high horse nor other lofty place.
Sure doesn't seem like "only", because you just tl;dr'd your keyboard off with a bunch of rambling and other incorrect information.
OverFlow wrote:So why is it - if we have Millions of users you are the ONLY one with a problem. ???
Clearly, given that there's an entire forum of people here with problems and questions. (edit: also, you seem to forget the silent majority factor. 100,000 people will pass by and use your site, 10,000 people will have a problem with it and leave, while only 1 of those people with a problem will post something about it.)
OverFlow wrote:furthermore the BartPE; Graphics, LAN and WLAN features are a RC features of DriverPacks BASE.
What does this even mean...
OverFlow wrote: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).
Oh! Oh! Here it goes again! I'm the noob! Yeah, that's it, I'm the noob. Can't come up with a better insult than "noob"? Even if it's not even true? How's about this for noob... you saying PE only uses VESA support (and yes you dolt, I know full well what VESA/VBE is). It works just like Windows. You give it a video driver after it's loaded VgaSave, and it'll run the video using that driver the next time you change resolutions. Same thing happened when I loaded the Graphics pack onto a PE disc and started it up. It started with the crap VgaSave driver, but when I went to the display control panel and changed resolutions, it started up the appropriate driver that was already loaded but not initialized. I'm gonna go out on a limb and guess you didn't know that either.
OverFlow wrote: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.
Uh, combining nVidia, ATI, Intel, SiS, and VIA drivers is something that does need to be looked at. IMO, DriverPacks A could be the dedicated graphics (ATI, nVidia) that get updated a lot, B could be the integrated GPU drivers (Intel, SiS, VIA), and C could be the "exotic" drivers like business class ATI/nVidia, and the old cards. Is that too obscure to ask? No, it's not... and it's something that should be done.
OverFlow wrote: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.
Which is why I'm here. The "ONLY" graphics driver I need is intel, yet your little DriverPacks BASE forces me to install ALL THE DRIVERS from the Graphics B set in order to get them. Similarly, the only drivers I need from C are SiS and VIA, yet I would otherwise have had to install TONS OF OTHER GARBAGE on my already packed disc. I just went ahead and burned the disc without any support. On a related note, if I did install the Intel drivers on my PE disc, they wouldn't be of any use anyway, because the VBE drivers are loaded by Windows and start up first... I'd end up having to make that extra trip to the Display Control Panel to set the resolution and initialize the driver anyway. There are so many flaws with this statement I could go on for pages.
OverFlow wrote:my suggestion to you is
prune DriverPack Graphics C down to Intel only and use that ![big_smile](http://forum.driverpacks.net/img/smilies/big_smile.png)
"my suggestion to you is
let me prune DriverPack Graphics C down to Intel only from the gui and use that
"
OverFlow wrote: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
Uh, you haven't even tried what I said, then. That's your fault for not even trying.
OverFlow wrote: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.
Uh, I didn't install WLAN. Also, if I have to remove \drivers\net from the folder, then why the h*ll doesn't DriverPacks BASE take care of that for me instead of leaving me in the dark about it - or even providing any useful information at all to hint at it? Seems like a rather ridiculous arbitrary request to delete a folder, don't 'ya think?
OverFlow wrote: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...)
Yeah, given that I wasn't even presented with the option, I was looking for a way to ensure they were not included.
You assuming I'm a n00b has set you up with so many false assumptions in your reply it's almost 95% chest-beating and 5% useful information. You know what it's called when you spend 95% of your post beating your chest? Being on a high horse. Hopefully now you're off your high horse.