You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by FalconFour
Pages 1
Hm, forgot about this topic.
Just felt like stopping by to make brief mention of what this totally idiotic drooling/slobbering head/helmet bashing newbie cooked up.
I happened to be reminded of this topic while re-reading the description and credit I wrote for driverpacks.net... it's worth a read IMO.
...
Burned the exact same source files back to the DVD+RW, reformatted the HDD again, started from scratch as usual, and guess what? No error, extracts fine.
I don't think DP's software is to blame directly here, but... perhaps, it's doing something that causes the filesystem on the disc to flip out?
I'm going to take this to ImgBurn's support pages as well, it seems to be something relating to how ImgBurn burns CDs versus DVDs. I do know that nLite's direct-to-disc burn to DVD doesn't work properly (it "burns" but results in a corrupt/unreadable filesystem) but works fine with CDR/W media, so there's something different happening with how DVDs are burned versus CDs... that may be a clue.
UN7ZIP.EXE - Application Error
The application failed to initialize properly (0xc0000006). Click on OK to terminate the application.
The above has happened twice now on a physical computer I'm trying to build a super-ultra-multi-unattended WinXP disc for. (edit: should mention: Happens shortly after the blue background and cursor comes up for first GUI boot during Setup, cursor changes to hourglass and back, about 15 seconds, then error comes up. Click OK several times, and Windows Setup starts up.) It's frustrating the ever loving sh*t out of me, because I tried this exact-same installation under VMware, and it works fine. The system has 512mb RAM and I _think_ it may be related to the fact that 7-Zip is a _huge_ memory hog (may be running out of memory?). But many of the systems I'd be using this disc on will have even less than that... so I really hope that's not the problem.
(edit: After clicking OK to about 4 more of those same errors, I get another error:
C:\DSPdsblr.exe
Windows cannot find 'C:\DSPdsblr.exe'. Make sure you typed the name correctly, and then try again. To search for a file, click the Start button, and then click Search.
... then Windows Setup starts without extracting the DriverPacks.)
What stumps me is that this is so "Ungoogleable". I searched about this problem and found absolutely nobody else even referencing a similar problem.
Here is my method:
1) Original XP SP3 files copied to folder on desktop.
2) nLite with a _ton_ of integrations, updates, installers, batch operation, startup autoit script, etc...
3) DriverPacks BASE 8.12.4 slipstream to folder (Disc mode), Method 2 integration, Custom finisher (added w/ nLite in batch file & tested working fine), using CPU 8.04, Chipset 9.02, LAN 8.12.1, WLAN 8.06, MassStorage 9.01, and customized Sound A 8.05 and Graphics B 8.12.1 packs (removed Creative junk from Sound A, and ATI/nVidia pro drivers from Graphics B leaving only Intel) integrated using "3rd party driverpacks", no KTD, QSC enabled.
4) Burn to disc using ImgBurn, ISO9660 filesystem only (no Joliet or UDF, all filenames changed to uppercase).
Any tips? I might get it fixed but I'm really ticked that I wasted a CD-R on a disc that didn't work right! The weird thing is, it worked fine when I burned it on a DVD+RW and I can't see why it would fail now with a CD-R (also failed earlier with a CD-RW). All files on disc were verified against originals during burn, and nothing was changed... but I'll Shift+F10 it during Setup and see what it sees, why it failed!
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.
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.
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.)
furthermore the BartPE; Graphics, LAN and WLAN features are a RC features of DriverPacks BASE.
What does this even mean...
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.
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.
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.
my suggestion to you is
prune DriverPack Graphics C down to Intel only and use that
"my suggestion to you is
let me prune DriverPack Graphics C down to Intel only from the gui and use 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
Uh, you haven't even tried what I said, then. That's your fault for not even trying.
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?
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.
That worked a whole lot better. It went through A1, N1, and N5 and took a whole 5 minutes to process this time (can't... figure out why... but it did).
Now if only we could figure out why I don't have those control panel options from the tutorial...
What version of DriverPacks BASE are you using?
File version (Explorer) says 3.3.0.0 and the version in the title bar says "DriverPacks BASE 8.12.4 - wnt5_x86-32_bartpe". Screenshot with all available options: driverpacks.PNG
We have a tutorial, I wrote it. It's a little dated, but it will still answer about 90% of your questions. I suggest you read it. And yes, it spells out the Control Panel options clearly.
Yeah, that's pretty clearly laid out. Too bad my GUI doesn't seem to have almost any of those options.
IF you really want our help, AND you can read & follow instructions, THEN read this thread and tell us the info we need to know about this bug you keep referring to.
1. Check the FAQ forum
(Did.)
2. Use the search function
(Countless times.)
3. Choose a good topic title.
(Well, can't change that now...)
- Don't forget to MENTION the relevant DriverPack (or DriverPacks BASE) and its VERSION in the TITLE.
(Did that above.)
4. Don't forget to COPY/PASTE these files INSIDE CODE TAGS.
- DPs_BASE.ini (from the same directory as DPs_BASE.exe)
[General]
; preferred language
prefLang = "English"
; yes/no, enable or disable the wizard-style buttons, if not specified: yes
wizardButtons = "yes"
; yes/no, enable or disable the GUI, if not specified: yes
GUI = "yes"
[Settings]
; disc/bartpe/multibootDisc
instPlatform = "bartpe"
; trailing backslash is allowed, but not necessary
location = "Z:\UBCD4Win\plugin"
; none/all/select, if select, specify them below, if not specified: all
DriverPacks = "select"
; 1/2, method to install the DriverPacks, if not specified: 2
DPsMethod = "2"
; GUIRunOnce/RunOnceEx/custom, if not specified: GUIRunOnce
finisherMethod = "GUIRunOnce"
; this section is optional!
[OptionalSettings]
; none/all/select/paths/patterns, enable or disable Keep The Drivers (KTD) , if not specified: none
KTD = "false"
; <path>, to specify a custom KTD cache location, if not specified: default (%SystemRoot%\DriverPacks)
KTDlocation = "%SystemRoot%\DriverPacks"
; yes/no, enable or disable QuickStream Cache (QSC), if not specified: yes
QSC = "no"
; you should only add this section if you've set [Settings]\DriverPacks to "select"
[SelectDriverPacks]
DP_Chipset = "no"
DP_CPU = "no"
DP_Graphics_A = "no"
DP_Graphics_B = "no"
DP_Graphics_C = "no"
DP_LAN = "no"
DP_MassStorage = "yes"
DP_MassStorage_textmode = "no"(curiously, those weren't the checkboxes I checked)
- DPs_BASE.log (from the same directory as DPs_BASE.exe)
(This is with the official Graphics A pack selected only)
2009-02-08 14:36:14 : <INIT> DriverPacks BASE 8.12.4 initialized.
2009-02-08 14:36:14 : <INIT> Host environment: WIN_XP Service Pack 3 on X86 CPU.
2009-02-08 14:36:14 : <INIT> Old temporary working directory deleted.
2009-02-08 14:36:14 : <INIT> Created temporary working directory.
2009-02-08 14:36:14 : <INIT> Imported proxy settings from Internet Explorer.
2009-02-08 14:36:14 : <INIT> Start scanning for DriverPacks for the wnt5_x86-32 platform.
2009-02-08 14:36:14 : <INIT> Detected DriverPack Chipset 803!
2009-02-08 14:36:14 : <INIT> Detected DriverPack CPU 804!
2009-02-08 14:36:14 : <INIT> Detected DriverPack Graphics A 8121!
2009-02-08 14:36:14 : <INIT> Detected DriverPack Graphics B 8121!
2009-02-08 14:36:14 : <INIT> Detected DriverPack Graphics C 8121!
2009-02-08 14:36:14 : <INIT> Detected DriverPack LAN 8121!
2009-02-08 14:36:14 : <INIT> Detected DriverPack MassStorage 901!
2009-02-08 14:36:14 : <INIT> Could not detect any 3rd party DriverPacks for wnt5_x86-32.
2009-02-08 14:36:14 : <INIT> Finished scanning.
2009-02-08 14:36:14 : <INIT> Detected settings file "Z:\UBCD4Win\plugin\DriverPacks.net\BASE\DPs_BASE.ini".
2009-02-08 14:36:14 : <INIT> [Settings]\DPsMethod not specified: default (2) was set.
2009-02-08 14:36:14 : <INIT> [Settings]\finisherMethod not specified: default (GUIRunOnce) was set.
2009-02-08 14:36:14 : <INIT> [OptionalSettings]\KTD not specified: default (none) was set.
2009-02-08 14:36:14 : <INIT> [OptionalSettings]\QSC not specified: default (yes) was set.
2009-02-08 14:36:14 : <INIT> [OptionalSettingsOther]\ATI_cpl not specified: default (None) was set.
2009-02-08 14:36:14 : <INIT> [OptionalSettingsOther]\Nvidia_cpl not specified: default (None) was set.
2009-02-08 14:36:14 : <INIT> wnt5_x86-32_bartpe is the selected installation platform .
2009-02-08 14:36:14 : <INIT> Imported settings from settings file.
2009-02-08 14:36:14 : <INIT> [OptionalSettings]\QSC BartPE default (no) was set.
2009-02-08 14:36:14 : <GUI> Initialized GUI.
2009-02-08 14:36:14 : <GUI> Created a list of all available language files.
2009-02-08 14:36:14 : <GUI> Set the last used language, English, as the GUI language.
2009-02-08 14:36:27 : <GUI> Saved settings!
2009-02-08 14:36:27 : <GUI> Closed GUI.
2009-02-08 14:36:28 : <SEL> Selected module: mod_slip_wnt5_x86-32_bartpe.
2009-02-08 14:36:30 : <PREP> Z:\UBCD4Win\plugin\DriverPacks.net\Chipset was deleted.
2009-02-08 14:36:31 : <PREP> Z:\UBCD4Win\plugin\DriverPacks.net\CPU was deleted.
2009-02-08 14:36:31 : <PREP> Z:\UBCD4Win\plugin\DriverPacks.net\Graphics_A\Graphics_A.inf info written.
2009-02-08 14:36:31 : <PREP> Z:\UBCD4Win\plugin\DriverPacks.net\LAN was deleted.
2009-02-08 14:36:32 : <PREP> Z:\UBCD4Win\plugin\DriverPacks.net\MassStorage was deleted.
2009-02-08 14:36:32 : <PREP> Z:\UBCD4Win\plugin\DriverPacks.net\MassStorage\MassStorage.inf header info written.
2009-02-08 14:36:39 : <SLIP> Extracted DriverPack MassStorage to a temporary working directory.
2009-02-08 14:36:39 : <SLIP> Z:\UBCD4Win\plugin\DriverPacks.net\BASE\tmp\DPMtmp\DriverPack_MassStorage_wnt5_x86-32.ini
2009-02-08 14:36:40 : <SLIP> Processing the files now. This may take a minute.
2009-02-08 14:37:03 : <SLIP> Copied DriverPack MassStorage text mode driver files to BartPE Plugin folder.
2009-02-08 14:37:03 : <SLIP> Slipstreamed DriverPack MassStorage text mode driver files.
2009-02-08 14:37:09 : <SLIP> Updated the MassStorage.ini [SetValue] sections to support DP MassStorage text mode drivers.
2009-02-08 14:37:44 : <PLUGIN> Extracted DriverPack Graphics A.
2009-02-08 14:37:44 : <PLUGIN> Started CAB compressing DriverPack Graphics A (estimated 7.2 minutes).
2009-02-08 14:37:44 : <PLUGIN> Z:\UBCD4Win\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack Graphics A\DriverPack_Graphics_A_wnt5_x86-32.ini
2009-02-08 14:38:21 : <PLUGIN> Z:\UBCD4Win\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack Graphics A\D\G\A1\CPanel, \wnt5, LAYOUT.BI?
2009-02-08 14:38:21 : <PLUGIN> Finished CAB compressing DriverPack Graphics A.
2009-02-08 14:38:21 : <PLUGIN> Saved settings!
2009-02-08 14:38:21 : <PLUGIN> Slipstream finished in 1 minutes and 54 seconds.
2009-02-08 14:38:24 : <CLNP> Temporary working directory successfully deleted.
- = DriverPacks BASE ini settings used = -
[General]
; preferred language
prefLang = "English"
; yes/no, enable or disable the wizard-style buttons, if not specified: yes
wizardButtons = "yes"
; yes/no, enable or disable the GUI, if not specified: yes
GUI = "yes"
[Settings]
; disc/bartpe/multibootDisc
instPlatform = "bartpe"
; trailing backslash is allowed, but not necessary
location = "Z:\UBCD4Win\plugin"
; none/all/select, if select, specify them below, if not specified: all
DriverPacks = "select"
; 1/2, method to install the DriverPacks, if not specified: 2
DPsMethod = "2"
; GUIRunOnce/RunOnceEx/custom, if not specified: GUIRunOnce
finisherMethod = "GUIRunOnce"
; this section is optional!
[OptionalSettings]
; none/all/select/paths/patterns, enable or disable Keep The Drivers (KTD) , if not specified: none
KTD = "false"
; <path>, to specify a custom KTD cache location, if not specified: default (%SystemRoot%\DriverPacks)
KTDlocation = "%SystemRoot%\DriverPacks"
; yes/no, enable or disable QuickStream Cache (QSC), if not specified: yes
QSC = "no"
; you should only add this section if you've set [Settings]\DriverPacks to "select"
[SelectDriverPacks]
DP_Chipset = "no"
DP_CPU = "no"
DP_Graphics_A = "yes"
DP_Graphics_B = "no"
DP_Graphics_C = "no"
DP_LAN = "no"
DP_MassStorage = "no"
DP_MassStorage_textmode = "yes"
2009-02-08 14:38:24 : <CLNP> Create a DPs_Base.log backup @ Z:\UBCD4Win\plugin\DriverPacks.net\BASE\LogFiles\DPs_BASE_09-02-08_14-38.log
2009-02-08 14:38:24 : <CLNP> Program terminated.
2009-02-08 14:38:25 : <GUI> Closed GUI.
2009-02-08 14:38:25 : <GUI> Saved settings!
- = DriverPacks BASE ini settings used = -
[General]
; preferred language
prefLang = "English"
; yes/no, enable or disable the wizard-style buttons, if not specified: yes
wizardButtons = "yes"
; yes/no, enable or disable the GUI, if not specified: yes
GUI = "yes"
[Settings]
; disc/bartpe/multibootDisc
instPlatform = "bartpe"
; trailing backslash is allowed, but not necessary
location = "Z:\UBCD4Win\plugin"
; none/all/select, if select, specify them below, if not specified: all
DriverPacks = "select"
; 1/2, method to install the DriverPacks, if not specified: 2
DPsMethod = "2"
; GUIRunOnce/RunOnceEx/custom, if not specified: GUIRunOnce
finisherMethod = "GUIRunOnce"
; this section is optional!
[OptionalSettings]
; none/all/select/paths/patterns, enable or disable Keep The Drivers (KTD) , if not specified: none
KTD = "false"
; <path>, to specify a custom KTD cache location, if not specified: default (%SystemRoot%\DriverPacks)
KTDlocation = "%SystemRoot%\DriverPacks"
; yes/no, enable or disable QuickStream Cache (QSC), if not specified: yes
QSC = "no"
; you should only add this section if you've set [Settings]\DriverPacks to "select"
[SelectDriverPacks]
DP_Chipset = "no"
DP_CPU = "no"
DP_Graphics_A = "no"
DP_Graphics_B = "no"
DP_Graphics_C = "no"
DP_LAN = "no"
DP_MassStorage = "yes"
DP_MassStorage_textmode = "no"
2009-02-08 14:38:26 : <GUI> Create a DPs_Base.log backup @ Z:\UBCD4Win\plugin\DriverPacks.net\BASE\LogFiles\DPs_BASE_09-02-08_14-38-26.log
2009-02-08 14:38:26 : <GUI> Program terminated.5. Tell us what you did - Could we try to reproduce your issue ourselves just based on your first post?
I downloaded UBCD4Win, which included DriverPacks.net BASE and an old version of MassStorage. I updated MassStorage, then downloaded CPU, Chipset, LAN, and Graphics B (which had Intel). I cracked open Graphics B and took out everything but Intel drivers, then re7z'd it and renamed the original version to ".old" and put the modified version in its place. Then I hit "slipstream" and let it work, and it went fine. Then I downloaded Graphics A and let it work. As I watched the output Graphics A folder grow, I noticed that there were no nVidia drivers in that folder. Looking at the log, I found that it didn't even mention the "N" folders, and it finished processing very quickly with no errors. It was completely ignoring the "N" folders. I extracted the file, and started comparing against my Intel setup that worked (I had to remove a bunch of sections from the INI file that no longer existed, and was down to just the header info). I did the same for the Graphics A INI file, I just removed everything but the header with file/folder info. It still didn't work (if I remember correctly). Then I deleted the "setup" folders from the "A1" folder (AVIVO, CCC, CPanel), and tried again. One or the other (I can't remember which I did) worked, but now it only mentioned N1 and N5 folders in the log (and it took much longer). I recompressed to 7z after each modification. But it did include the files in the (now much larger) output folder. That's where I am now, but for sake of uniformity, I restored the original 7z's, and it still does the same thing.
6. Submit it to the bugtracker if it turns out to be a BUG. Attach the relevant files there as well.
Well, soon as it turns out to be a bug and not just part of BartPE integration's strange behavior (like not allowing "custom" driverpacks)...
On a related note, thanks for not just banning me outright... 
What I'm trying to contribute, if you'd both get off your high horse and quit acting like your "product" is 110% perfect and deserves every cent out of my bank account (all $11 of it)... is that it can be better if you'd just take the moment to think about it. I don't know what the "most people" in both of your replies are using DriverPacks for, but I use it for a BartPE setup that I want to burn once and use on any Windows XP class computer. I don't expect it to work with Win2k-class computers with old Matrox or 3dfx video drivers. I just want it to work on "Most" computers, and that's not a lot to ask given there are only 5 major graphics contributors - 2 "dedicated" (ATI, nVidia) and 3 "integrated" (Intel, VIA, SiS) providers. VIA and SiS may be dead now, but old (and even moderately recent) AMD systems used them extensively.
It would be nice to see the ability for the DriverPacks BASE to selectively install manufacturers (by folder, perhaps). It would not take a lot of effort to enumerate the folders in a .7z archive, put up a list with checkboxes, check to see if someone unchecked an item, then send a different command to the 7-zip decompressor that specifies what files to extract. That would save a h*ll of a lot of effort.
On the topic of customization, I still don't even know what the h*ll Helmi is talking about with the CP options thing. It's either checked or unchecked. There are no options in BASE for it. You didn't "explicitly shove it under [my] nose", you mentioned something that, as far as I can tell, doesn't even exist. I can tell you "McDonald's sells video cards" and it holds about as much sense as what you said.
And about that bug? Why the h*ll is the only response I've been "we don't want to hear about it, tell it to the bug tracker" instead of "could you elaborate on your setup"? Clearly you don't even care... why would I add it to the bug tracker? I'm not a developer, why would I go and add something to the bugtracker?
Helmi, get an attitude adjustment. At least mr_smartepants isn't such a huge douchebag about everything.
Looks like someone needs to get kicked in the knees to get off their high horse...
Just because you don't seem to grasp our concept of splitting up the drivers (which was elaborated and discussed comprehensively among the team and everyone agreed on it!)
Sounds like another case of the "i am everyone".
So you are using it in your repair shop - fine.
Our hard work saves you time AND money the like but all you do is come here and complain.
Very nice first post there, buddy...Ever considered to donate to the project or have you just come around to complain?
Your hard work has thus far wasted my time and hasn't saved me any money... as I haven't made a cent off my intern job and I haven't yet even been able to get the "hard work" to even "work" yet. It's just been a headache for the past several hours trying to piece apart the tangled and broken mess trying to make it into a coherant mass that I can get DriverPack Base to accept, then PEBuilder to build, within 700mb, along side a couple hundred megs of other combined BootCD's in one ISO.
Dead on, Sherlock!
And guess what, these are the most frequently update drivers, too, so it's only logical to have them in their own pack, because that saves bandwidth...
Why in god's name do they even need to be updated...? All I care about is that 95% of the computers on the workbench actually come up with a optimized video driver. If the video card just came out in the past 3 or 4 months, I kinda expect it to not work properly in a CD I burned 6 months ago anyway...
Boohoo!
Either you are totally incompetent or just simply too dumb.
So you had to waste time on that, huh?
Clearly, considering as though I've made it this far.
Someone's forcing you to use the DriverPacks?
Poor sod...
Yes, actually... seeing as though I can't create custom DriverPacks and enter them into a WinPE installation due to DriverPacks-Base's architecture that blocks custom DP's from being used... I'm kinda tied and chained to DriverPacks.
The packs are intended to and do work as such being used together.
There's no overlapping and they work just fine for everyone else...
(emphasis mine)
*cough* duplicate files in every folder *cough*
Apparently, you are too dense to notice the options in BASE.
Don't like the CCC, don't enable it, period.
Read the guide first, will ya!
There are so limited options in BASE that there isn't even a way to disable it. You either enable or disable the packs. That's it. That's all the option there is. And that doesn't solve the fact that it crashes out while building, with the defaults...
Oh, and bugs are to be reported at the bugtracker, kthnx!
Oh, so it is a bug after all.
Why are business class drivers unnecessary?
Lots of our users work as sys admin in big companies and those are exactly using aforementioned cards, you genius!
They don't belong along side the most common consumer class video drivers (Intel integrated video). I'd love to see you use your irrefutable logic to bend around that contradiction.
So, should we cater for the single needs of you very shop now or what?
And the next shop having other five-tops producers gets their own packs, as well, hum?
Do you even realize how ridiculous such a request is?
Uh... I dunno what planet you live on, but those are the top 5 on the entire planet, not "in my little shop".
Plus, BASE is auto-DLing the packs for you already, what kind of lazy bugger are you?
I guess you don't care about your own bandwidth. Smart move, why don't you tell that to your host.
Next, please... preferably someone that's not a total d*ck about it this time?
edit: Well, h*ll. Adding the graphics DriverPacks (even stripped down to their core) pushed me about 30mb over the CD capacity, and didn't even work properly. It's detected in WinPE's device manager, and I can activate the driver through Display Properties (and adjusting/setting the resolution), but it's not activated on startup. Since booting WinPE in the shop is a straight-through process in a busy environment, there's not even any benefit to it, since it requires extra steps to get the added acceleration of a proper video driver. So all that work for nothing, hooray.
edit edit: MassStorage, LAN, and Chipset are useful, though.
I think DriverPacks are great for my WinPE/BartPE (UBCD4Win) installation. I'm putting together a one-size-fits-all boot CD for a PC repair shop I'm interning at, and I've just about got it.
One thing's been having me bash my head against a wall, though. The driver packs for graphics are split up by some ridiculous criteria with no real-world purpose.
We've got nVidia and ATI (the two "dedicated GPU" manufacturers) grouped into "A" along with a bunch of unnecessary control panel installation trash on the ATI side (that, in fact, causes the driver pack to not slipstream properly - it "crashes out" silently after integrating A1 acting like it completed - that's the bug referenced in the title). Then we've got Intel drivers along with a bunch of unnecessary "business class" nVidia and ATI drivers. Then we've got VIA and SiS drivers, this time with a bunch of outdated manufacturers nobody cares about.
nVidia, ATI, Intel, VIA, and SiS are the five manufacturers that produce the graphics chips on about 95-98% of the computers in the shop - including laptops. So far I've had to waste hours of time and tons of bandwidth downloading - then repackaging and recompressing and bug-testing - those driver packs, trying to get all 3 installed with just the components that are actually relevant to me. How come the "Big 5" aren't packaged into "A" or maybe just A and B? Doesn't it seem a little excessive that I'd have to download all 3 to get the drivers I need? 
Pages 1
DriverPacks.net Forum » Posts by FalconFour
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.017 seconds, 8 queries executed ]