You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by mr_smartepants
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.
Sigh...
OK, let me spell it out for you, because I honestly want to help make DriverPacks a better experience.
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.
What version of DriverPacks BASE are you using?
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.
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.
ELSE, any response other than to answer my above question will result in your account being locked (and prove Helmi was right about you).
FYI,
I never mentioned the bugtracker.
I never said our "product" was perfect. Do you think I'd spend as much of my free time trying to fix it if it were?
You have some good ideas, and we will listen, if you treat us (yes, all of us) with respect.
Choose your words in your next post very carefully.
I think DriverPacks are great
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.
LOL, you're confused. But it's OK.
That PhysX installer was built by dumpydooby (in RogueSpear's style). The DriverPacks Finisher doesn't care if the installers are switchless or require 15 switches, we just load those into the .ini.
To be honest, I haven't played that much with dumpydooby's PhysX installer. I wish I could make my own, but I just can't find the time to learn that awesome method. I hope I will soon.
If you want to try that installer, just replace my PhysX installer with dumpydooby's and change an entry in the DriverPack Graphics A .ini N1 section from this:
exc_2_command1 = "%DPSROOT%\D\G\N1\PhysX.exe /qb"to this:
exc_2_command1 = "%DPSROOT%\D\G\N1\PhysX.exe -ai"Easy! 
Yes, that tutorial is not up to date with the latest DriverPacks BASE. I'm really falling behind, in many things.
Did you try DriverPack Chipset in an integration yet? Did you verify it didn't work? I'm fairly certain it's already in there, even if it isn't listed.
2. copy in the eg1032v3.inf, eg1032v3.cat, eg1032v3.sys files into the D\L\1 directory.
That's over-simplified. Here's a simplified approach.
You need to look in each .inf that you're adding and scan for dependencies. First place to look is under [SourceDisksFiles], any file listed MUST be in the folder. If there's a section [SourceDisksNames], that will show your directory tree. You also need to scan the other .inf sections for other files not listed in the above section.
Don't worry about the DriverPacks .ini unless you want the DriverPacks Finisher to run extra installers later.
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
Thanks for your post, and welcome to DriverPacks!
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.
2009-02-04 20:46:33 : <FLTR> ! Could not match +infFile"C:\D\G\A1\CX_72271.inf" through the HWID "PCI\VEN_1002&DEV_9610&SUBSYS_D0001458" (original HWID: "PCI\VEN_1002&DEV_9610&SUBSYS_D0001458&REV_00") (1 of 3 +infFiles).
2009-02-04 20:46:33 : <FLTR> ! Could not match +infFile"C:\D\G\A1\CX_72271.inf" through the HWID "PCI\VEN_1002&DEV_9610&REV_00" (original HWID: "PCI\VEN_1002&DEV_9610&SUBSYS_D0001458&REV_00") (1 of 3 +infFiles).
2009-02-04 20:46:33 : <FLTR> ! Could not match +infFile"C:\D\G\A1\CX_72271.inf" through the HWID "PCI\VEN_1002&DEV_9610" (original HWID: "PCI\VEN_1002&DEV_9610&SUBSYS_D0001458&REV_00") (1 of 3 +infFiles).WTF!!! 
Damn it it's right THERE, how can the DriverPacks Finisher NOT find it!
Maybe the new DriverPacks Finisher is getting confused by the &REV_00 ??
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.
i need help on how to add the windows media center stuff to my windows xp pro pack 3.
i have already installed the xp pro 3.. any help
Irrelevant to the topic. Bordering on warez discussion. Watch it.
Not good for a first post.
You know, it really hurts my feelings knowing our hard work is being used to break the law.
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.
mr_smartepants you will add these drivers in next DP?
Thank you
If I can find some time, I'll add it in.
For future reference for everyone else, adding a new driver isn't as simple as just adding a folder. We need to compare the added HWIDs to every other HWID in all the DriverPacks to make sure we aren't duplicating anything or causing conflicts. That takes time...
I'm really going to have to get off my ass and learn how to build those multimode installers! They're awesome!
This months packs will be uploaded 15th -16th jan
Really? Are you going to do them? 
And the latest Misc pack appears to have been moved to the old folder so there isn't one of it there. Someone accidently move the wrong file?
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.
Added to DriverPack Sound B 901n3 (not online yet)
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.
Sorry, I couldn't find much info on that laptop. Do you have the original discs that came with the laptop? If you find a driver that works, we'll add it.
OK, I'll fix the driver signing for 93.71.
DriverPacks.net Forum » Posts by mr_smartepants
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.104 seconds, 5 queries executed ]