Search options (Page 123 of 159)

Moved topic to BartPE section.
OK, I don't use BartPE, or UBCD4win so I don't know how to help you.  I moved the topic here.  Maybe someone versed in those utilities can help.
Can you decompress DriverPack Graphics A, removed the below entries from each header, then recompress and try again?

; BartPE Code
ms_count	 	= 1
ms_1_tag 	= "N1_nv4"
ms_1_sysfile 	= "nv4_mini.sys"
ms_1_exc_skipIfOS="wxp,w2k3"

I'm pretty sure that's what's screwing your integration.

You're welcome.

Considering I'm the main contributor to all the Graphics DriverPacks, I guess you have a problem with me.
So be it.

As Helmi said earlier, the decision to organize the three Graphics DriverPacks the way they are now WAS MY IDEA, but everyone in the DriverPacks team and the Testing team collaborated and voted on that layout.  I didn't 'strong-arm' anyone or force the decision.

The three DriverPacks are organized like this:
DriverPack Graphics A: (A)ctive.  The drivers for the most active, common cards (desktop/mobile).  Cutting-edge stuff.
DriverPack Graphics B: (B)usiness.  The drivers for most business workstations, and the other mainstream drivers.
DriverPack Graphics C: (C)atch-all.  Drivers for outdated/obsolete hardware, or drivers that will never be updated.

I've tried to balance the three DriverPacks so the download size is similar.  Because the DriverPack Graphics A is lighter weight (because of the separate Language DriverPacks), I may merge \I1\ into DriverPack Graphics A because (like you pointed out) it's mainstream, and increasingly common.  I won't do that without collaborating with the team though.

In my opinion, SIS is dead (same with VIA).  They don't have a compelling mainstream product, nor can they compete at the budget level.  Game over, and they're all out of quarters.
Your opinion may differ, you're entitled to your own opinion.

I'll agree partly with you.  The main players are ATI/Nvidia/Intel, all the others are 2nd rate.

As to our bandwidth, isn't that our problem, not yours?  BTW, SimpleCDN DONATES our UNLIMITED bandwidth.
Our policy with all DriverPacks is: Stability first, maximum coverage second.
If you don't like what we provide, feel free to prune them down to what you consider an appropriate size.  Otherwise, build them yourself.

I'm being very patient.  Your first post came off as very arrogant and pushy.  Helmi's response was pointed, but measured. 
We will listen, but not if you're going to act like a prick.

If you have a legitimate bug, then read this thread before you post, then use the site search function to answer your own question.  If you can't find the answer, post a new thread in the appropriate section and ask your question (ask, not demand an answer).
Be nice, make contributions now and then, and you'll be a welcome addition to the DriverPacks family.
Be careful how you word your responses or your visit here will be brief.

Yes, that tutorial is not up to date with the latest DriverPacks BASE.  I'm really falling behind, in many things.

Thank you!

That HWID is found in DriverPack Graphics B\I1\
B\D\G\I1\igxp32.inf    12/12/2008    6.14.10.5016    PCI\VEN_8086&DEV_2A43    Mobile Intel(R) 4 Series Express Chipset Family

Maybe you can test our nightly for us?
http://dev.driverpacks.thesneaky.com/dr … 2_901n1.7z

I know on my test systems, the &REV_** (and sometimes the SUBSYS) are ignored, the way they should be when a generic hwid is present.  I just installed on my HD3450 and everything was good.  I just don't understand why DriverPacks Finisher wouldn't pick this up.

Yes, try the new nightly 902n1 (catalyst 9.1) and let us know.  If CCC still fails to install then we absolutely need to see your DPsFnshr.log (it contains HWIDs and the DriverPacks Finisher errors).  You'll need two posts to get it all, or you could just email it to me and I'll post the relevant portions.

Also, check your disc source \OEM\ folder for ATICCC.ins.

Go get 'em tiger!!

If you used the default options in DriverPacks BASE, then your XP install only uses the drivers it needs, nothing more.  It's only if you select KTD (Keep The Drivers) that all the drivers are stored on your C:\ drive.

I'm really going to have to get off my ass and learn how to build those multimode installers!  They're awesome!

Fixed.
Also, I renamed DP_Modem_wnt5_x86-32_9.01.7z to DP_Modem_wnt5_x86-32_901.7z
There can not be any periods (.) in a filename.

Everyone I know who was running XP-64 jumped ship to Vista as soon as it was available (out of sheer frustration). 
I'm with JakeLD, as soon as Win7 is final, I'm onboard!  Vista is history.  XP-32 is still my recommended OS for older hardware though, and I still run it on my two notebooks.