You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by mr_smartepants
Helmi's right. The main reason I decided against adding the hotfix at this time was because AMD/ATI doesn't officially support it themselves.
It only added increased performance/stability in some games. That's it.
http://support.ati.com/ics/support/defa … onID=29837
Note: This driver is provided as is and is not supported by AMD. It has not completed full AMD testing, and is only recommended for users experiencing the particular issue described above
I'll look into it. Our .ini edits were supposed to fix that since the wildcards aren't used anymore.
Exactly which DP versions are you using? "The latest" just isn't descriptive enough (they got updated a few days ago).
Can you post your finisher log for us?
God! There's gotta be an easier way than that!
Jaak's been working on a cmd script (I'm toying with one now) that automates the process using the DriverPacks finisher itself.
Not making much progress though. 
Open your source\i386\winnt.sif file
Add the following:
[Unattended]
DriverSigningPolicy=Ignore
NonDriverSigningPolicy=IgnoreSorry, I've been swamped with real-life issues lately.
I haven't forgotten this request. I've looked into the multi-language installer request and ATI hasn't made it easy. I'm still working on a solution, but for now, we may have different ATICCC installers just for certain languages (swapped out in the DP prior to slipstreaming.)
I'm looking into rewriting the installer .ini files to support multiple languages (something ATI should have done in the first place!
Us2002, I'll remake the G_B DP using the 6.11 cats again...just for you. 
Be patient.
Thanks Helmi, but I grabbed it two days ago! 
1000 posts, wow!
Hi, welcome to Driverpacks.net!
That idea is already on our "to-do list".
We can only work with what ATI provides on their website. If you know of a language specific installer (or multi-language installer), let me know and I'll see what I can do.
I was under the impression the ATI package included multiple languages.
I verified the drivers in the latest nightly are identical to the ones in the 6.11 release Us2002 refers to.
What's weird is that the driver version referenced in the .infs in the 6.11 release AND the latest nightly are 8.252, not 8.31 as in the release notes.
Why in DPG_B for ATI pre 9500 is Catalist 6.5, not 6.11? Is it problem with driver version 8.31 (Cat 6.11)?
I'll look into it. I'm sure it's just that the tracker wasn't updated with the correct info.
If you're right, it was a huge oversight on my part.
what are SOE's?
Maybe "Standard Operating Environment"?
We use the term "Standard Desktop Configuration", SDC
Jaak's talking about an intel microcode update. I can't remember where I saw it either, but it's included in Ryan's update pack.
First, your log file indicates you're not using the .ini file you posted. The settings just don't add up.
The DPBase is using the ini file here:
Detected settings file "\\sc-it-net2\c$\DriverPacks\DPs_BASE.ini"
I'm guessing that's the wrong settings file...right?
I don't use BartPE, so someone with experience should be able to help you.
OK, OK, can you post your log and .ini file?
I'm not sure a broken 'donate' button would be considered 'fatal' (this works fine in my English XP).
The error is because the DPbase is trying to open Internet Explorer with the link: http://driverpacks.net/DriverPacks/donate.php
Do you have an alternate browser (Opera?) set as default?
Does ANY function of the DPbase work?
If not, delete all files (ini, exe, & folders except for your driverpacks.7z files), redownload the DPbase program and try again.
What's weird is the "any_any_any" in the title bar of DPbase instead of 'wnt5_x86-32_disc'.
I'm on the case!
Will upload a test DP tonight if I'm lucky. Tomorrow morning at the latest.
Sounds like a corrupted CD burn.
First, verify that file exists in your source.
Then, if it's there, recreate the ISO and test in VM (saves from burning CDs)
If everything worked, burn at a slower speed (slower the better).
Well ask yourself this question. Would it be quicker to copy 100MB or 1000MB? With compression, the file-copy process is much quicker then decompressed. The decompression process after the file-copy takes less time than copying the decompressed files.
Although, to be honest, I haven't taken any timings to confirm that. So take my ramblings with a grain of salt.
That's easy. You are already using nlite...use it for what it was built for. Remove all the stuff you'll never use/need (languages, keyboards, MSN Explorer, .NET 1.0, etc.).
You can easily save yourself up to 300 MB of space.
I found this driver on driverguide (don't get me started!) which claims it's for XP, but the .inf doesn't mention XP. You could try it and see.
Doing a google search for "trident VEN_1023&DEV_9850&SUBSYS_98501023" brings up the same link to driverguide.
Looks like only half of the file got uploaded (9.1 MB).
That's the cause of the corruption and MD5 mismatch.
You downloaded the correct Driverpack if you plan to integrate those drivers into your WinXP source. Follow this tutorial here.
If you just want to install the updated drivers in an existing XP install, then just download the Desktop ATI drivers and follow the instructions for the DriverHeaven Mobility Modtool here:
You're welcome.
Good mornig..i've got an acer aspire 1604lc....i'd like to update drivers...i already tried omega driver but system freeze every time i use a video player...any solution??..thanks...
Sure, use the DriverPacks!
Seriously though, if you're getting freezes with the omega drivers, your system may be slightly different. First, ensure you completely uninstall anything "ATI" as well as your omega drivers.
Then, unzip both the Graphics_A & B driverpacks to your hard drive.
Restart your computer and point the 'add hardware wizard' to the D\G\A\5 folder (for drivers).
When finished, double click either the D\G\A\1\ATICCC.exe (for the control center) or the ATICCP.exe (for control panel). Or install the ATI Tray tool (use google).
Note, the ATICCC requires .NET 2 or higher.
Can you look on your existing machines for the driverfiles in use? Go to your Device manager, double-click on the Trident card, select the 'Driver' tab, click the 'Driver Details' button.
Look for files called "trid3d.dll" or similar. I'm guessing the drivers you need are already included in WinXP_SP2 driver.cab.
I agree, but the vendors don't make it easy. Many of those drivers use .cat files for driver signing. The HWIDs are embeded in those .cat files. If we make the HWIDs too strict (&SUBSYS_), they won't catch all the appropriate hardware.
I'm not sure how to handle them. My gut instinct is to split them off into Modem_A and Modem_B (or C&D) so the user can choose and they won't conflict with others.
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.108 seconds, 5 queries executed ]