Huh? I've never heard of reinstalling Windos through "the Update function". Where and how do you do this?
Are you trying to UPGRADE a previous Windows? That is NOT supported. Nor is it recommended: it leaves you with a messed up Windows.
You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by Wim Leers
Huh? I've never heard of reinstalling Windos through "the Update function". Where and how do you do this?
Are you trying to UPGRADE a previous Windows? That is NOT supported. Nor is it recommended: it leaves you with a messed up Windows.
That means the KB888111 hotfix isn't slipstreamed properly. Could you please post the contents of your svcpack.inf files?
Are you using a proxy? Proxies are not yet supported!
OK. Now make a custom DriverPack with ONLY the driver I linked to in my previous post. If you don't know how to make your own DriverPack, check the tutorial in the 3rd party DriverPacks forum.
You've done something very odd. fnsh_log.cmd was used in version 6.05 and later, but is no longer in use since version 6.08 or later.
Please post your DPs_BASE.log.
Must have been very temporary, it's working here.
Yes, that's what I meant. It should be installed by cmdlines.txt. Note that you should use backslashes (\) instead of the slashes (/) you're using in your example.
Bâshrat the Sneaky wrote:Already downloaded
Don't forget to include the WDMs this time!
![]()
I only forgot the WDM driver in the old Catalyst 6.5 driver in DriverPack Graphics B! And no, I won't forget it again.
I agree that the obligated Knowledge Base concept sucks when you just want to download drivers. It's not as straightforward as it should be, too.
Only the DPsFnshr.ini must be edited. A quick example for what you will need to add:
[wnt5-x86-32__1000__D]
tagFiles = 0
+hwids = 1
+hwid1 = "<the HWID of your GPU>"
-hwids = 0
+infFiles = 0
-infFiles = 0
commands = 1
command1 = "<the command that will start the Omega 6.5 silent installation>"
That's it.
Hi, sorry to bother you, but i have the same problem since july and just saw this thread. I can only download the driverpack base, i think my download manager was the problem with too many connection.
I actually disable it but the problem still remain.
Sorry for the excessive connectionWhat can i do for be able to download the driverpack again?
Thx for the amazing work and sorry for my english
Your IP was blocked too. Unblocked it now.
Your IP also showed a truly excessive amount of download requests. Please shift to another download accelerator. 5 simultaneous download requests won't hurt, but >20 is painful.
Already downloaded
RunOnceEx is executed AFTER GUIRunOnce, so the .NET FW will be installed AFTER the CCC (because the Finisher is started through GUIRunOnce and thus it executes first). There's the culprit then... Install the .NET FW at T-12 (cmdlines.txt) and the problem will be solved.
Bâshrat the Sneaky wrote:I cannot find it on the internet, most sites refer to the ATI.com download, which is no longer operational.
That is strange, it still worked for me yesterday...
*puzzled*6.5 *complete* driver:
http://support.ati.com/ics/support/defa … onID=222646.8 *complete* driver:
https://support.ati.com/ics/support/KBA … tionID=640Just make sure not to follow direct links as they have an anti-hotlinking script in place.
I swore that page existed, but I just could not find it somehow! Thanks, Helmi!
Then this problem remains somewhat a mystery... I'm afraid I won't be able to find the true cause until I've got the system in my own hands... which is a problem when you know you live in Italy and I live in Belgium. My only suggestion is that you always install the Omega 6.5 drivers manually on this specific system. You could automate that through the finisher: use the hwid as a +hwid requirement for the setup to be executed.
Get Catalyst 6.5 + Control Panel here : http://rapidshare.de/files/33821736/ATI-CP65.rar.html
Thanks!
English please!
The issue with the file not found for the driver in D\G\A\6 is solved in the new DriverPack Graphics B, which is yet to be released.
The problem with the driver itself though remains a mystery, and even more due to the fact that the two of you decided to discuss it in Italian! Could you please post transcripts?
I've just retried on my own system and it seems to work just fine. I must say that I improved the installation process for the ATI Catalyst Control Center in DriverPacks BASE 6.09, but it has always worked for me.
Please test again when DriverPack Sound B 6.09 is released and then let me know if the problem persists or if it's solved.
I've updated the D\G\A\1\mobility.inf file to support this device. It will be supported in the next version of DriverPack Graphics A.
I've created what you could describe as 'the ultimate Driver Signing Policy Disabler', but I've just named it 'Driver Signing Policy Disabler'. It will be included in version 6.09 and those who were unfortunate with the KTD feature, will no longer have to manually click every time a Driver Signing Policy popup appears.
It's currently being beta tested... Just a bit more patience...
Can somebody send me the 6.05 FULL driver package or the 6.05 WDM package? It seems I only have the DRIVER package
I cannot find it on the internet, most sites refer to the ATI.com download, which is no longer operational. Other sites require authentication.
Changelog
updated
- VIA Hyperion drivers from 5.09a to 5.10a (null update)
Known issues
- system lockup when used on a Dell GX520
Remarks
- none
Rogier, sorry for the extremely late reply! I've been working very hard on the next version of the DriverPacks BASE and totally forgot about this post. It's solved in DriverPack Chipset 6.09.1, which is available right now!
This is the original chipset driver for the Dell Optiplex GX520. As you can see, it's version 7.0.0.1019.
The driver in DriverPack Chipset that supports this chipset, is in particular the driver in D\C\I\xp\ich7core.inf, which is version 7.0.0.1020. I can only guess, but I'm confident that this driver works fine.
The only way to isolate the issue is to gradually add and leave drivers. First only use the Chipset drivers. If the problem persists, then that's where we need to look for the cause. As soon as I have the test results of such a test from either of you, I can continue to eliminate possible causes.
DriverPacks.net Forum » Posts by Wim Leers
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.069 seconds, 5 queries executed ]