2,151

(12 replies, posted in News)

Well done to everyone involved.  It's been a long dusty road, but worth the trip!

Well, I don't know where that file came from because I went back through all our DriverPack WLAN archives and that file doesn't exist going back all the way to the 8.05 release.  It must have been added by someone else, not by the DriverPacks team.
That .inf is for x64 builds.  You should remove it from where ever you found it.

chumbo wrote:

I wondered about the one ending in X, i.e., ATHWX.SYS and the INF file seems to indicate it's for AMD processors.

I don't know where you are finding the athwx.sys because we have never included it.  It's for Win9x systems. wink

;Abstract:
;    INF file for installing Atheros AR5008 Wireless Network Adapter
;
;    Installs athw.sys (NDIS 5/5.1 driver) on NT platforms (2000, XP and greater)
;    Installs athwx.sys (NDIS 5 driver) on 9x platforms

I'm updating the wlan atheros drivers today.

Looks to me like ATI is only supporting that chip in Win7 only.  Not XP.
If we did support it, it would be a hack, and probably not stable at all.
I'll see what I can do.
Looking in the catalyst 10.6 beta, your HWID is supported.

Got it.  I'll have a look later.

Can you upload your %windir%\setupapi.log also please?

Special test pack just for you! wink

http://tppc-support.nl/driverpacks/Test%20Pack/DP_Graphics_A_wnt5_x86-32_1006t1.7z

Don't use any other graphics DriverPacks or Third Party DriverPacks in conjunction with this test pack.

I'm in the process of upgrading our DriverPack Graphics A nightly to catalyst 10.5.  Would you be willing to test?

DriverPack Sound B \I20\ is a very close match to your HWID.  You should extract folder \I20\ from the pack, modify the \D\S\I20\STHDA.INF to match your HWID then use the "Have disk" method to install the driver.
Change this line:
%ST.DeviceDesc%=STHDA,HDAUDIO\FUNC_01&VEN_111D&DEV_7605&SUBSYS_1028044F
to read
%ST.DeviceDesc%=STHDA,HDAUDIO\FUNC_01&VEN_111D&DEV_7605&SUBSYS_10280447

Please report back if this is successful on your hardware.

Read Before you post

2,161

(4 replies, posted in Feedback and Support - DriverPacks Base)

Try testing your .iso in VirtualBox.  If you get errors in that, it's a bad build.  But if it works from the .iso, and not the disc, it's a bad burn.

2,162

(7 replies, posted in 3rd Party DriverPacks)

Thanks SamLab.  Always a pleasure to have you back.

2,163

(14 replies, posted in DriverPack Mass Storage)

The .txt file is normal for our testing DriverPacks.  You can delete it manually or with a batch file.
The dspdsblr.exe should be deleted after the first restart, if not, you can delete it manually and it will cause no problems.
Thank you for confirming our fixes.  The final release is VERY close now.

2,164

(103 replies, posted in 3rd Party DriverPacks)

Well, I built the installer blind.  I don't have the hardware to test on and guessed at the switches based on what I saw in the .ini. 
Ah well, it is beta. wink
Thanks for the feedback, I'll try to fix it if someone else doesn't come along and fix it first.

Yes, that's very interesting.  I'll have a look later.

slckmstr wrote:

Any report on this fixing the problem? I hope to build a new disc and give it a go later in the week, I'll report back.

Well yeah.
This should already be fixed in 10.05.2.  Please let us know if it is not.

2,167

(7 replies, posted in 3rd Party DriverPacks)

I'm finalizing sound now.  I'll work on this later.

2,168

(1 replies, posted in DriverPack Graphics)

Welcome to DriverPacks!
Excellent first post.

What you didn't mention though was if you've tried any of the DriverPacks. wink
Because your HWID is supported through the current release DriverPack Graphics A\D\G\N1\NV4_GO.INF

Now if you've tried DriverPacks and they don't work, then that's something to go on, but I'll need to see your setupapi.log from the failed system.

Well, we'll just have to work on that won't we. sad

2,170

(22 replies, posted in 3rd Party DriverPacks)

SamLab wrote:

\LS
Logitech Setpoint V4.82.4 [20090617]

This http://slil.ru/29272020
Logitech Setpoint V4.90.49.0 - 10.11.2009

http://forum.driverpacks.net/viewtopic. … 468#p30468
RogueSpear gave up on Setpoint a while ago.  I'll have a look but I wouldn't take any bets on me succeeding where he failed.  Unless you're betting against me. wink
BTW, I couldn't find an official link for setpoint 4.9, but I did find version 6.0.
#  Title: SetPoint 6.00
# Software Version: 6.00.68
# Post Date: 02/25/2010
# Platform: Windows XP
# File Size: Approximately 25 Mb
http://www.logitech.com/en-gb/433/140?s … =downloads

2,171

(103 replies, posted in 3rd Party DriverPacks)

Excellent!  Keep us posted!

2,172

(103 replies, posted in 3rd Party DriverPacks)

That's what I figured would happen.
Let's delete the whole BT\D\ folder and .ini sections.
@compstuff, let me know what you find out in your testing and I'll work something out in the .ini.

2,173

(103 replies, posted in 3rd Party DriverPacks)

None of my machines use bluetooth, so I didn't know that.  Bummer.
So this Third Party DriverPack has limited usefulness.

2,174

(20 replies, posted in DriverPack Sound)

Soon.  Very soon.

2,175

(103 replies, posted in 3rd Party DriverPacks)

Moved from testing thread:

compstuff wrote:

I made the changes you referenced here: http://forum.driverpacks.net/viewtopic. … 651#p38651

I did the install 2x to check what was going on because it was rather odd. During the install I get two failure messages regarding the blue tooth install... so I ignore them to proceed. Then during the finisher the bluetooth starts to install but gets caught in an endless loop asking me to hit FN+F11 or turn the radio switch on. I tried the FN (no switch) but it never worked so I eventually hit cancel and then finished the install and rebooted.

After the system comes up the Bluetooth and wireless is working and their are no setup or device manager errors.

After doing some reading on this issue their seems to be some problems with other dell systems when downgrading their Bluetooth modules to XP. They recommended running this before installing the software/driver because the Bluetooth is actually OFF hence the problem http://ftp.us.dell.com/network/R159805.EXE which extracts Btw_on.exe

http://www.mediafire.com/file/e4iknoe2zty/DPsFnshr.log

Let me know your thoughts

Installed Optiplex 160L, Optiplex GX520 and IBM ThinkCentre Lenovo with NO PROBLEMS

Ack! It's trying to install both bt\d\ and bt\t\

2010-06-02 16:52:34 : <EXEC> Executing all commands (1) for exception [D].
2010-06-02 16:52:34 : <EXEC> 	Executing command 1 of 1: "%DPSROOT%\D\3\BT\D\BT60111.exe"
2010-06-02 16:59:39 : <EXEC> Executing all commands (1) for exception [T].
2010-06-02 16:59:39 : <EXEC> 	Executing command 1 of 1: "%DPSROOT%\D\3\BT\T\BT71012.exe"

I'll have to work on that. 
\T\ is both newer and encompasses more HWIDs than the older Dell driver \D\.  Have you tried deleting the entire \BT\D\ folder and trying it that way?
If \T\ doesn't work at all, then \D\ will have to stay, but it was a quick and dirty test that needs more refinement.  I'd really prefer NOT to have the Dell drivers in there since they're duplicated by the much newer \T\ section.
Does the Btw_on.exe have any switches?  Or is it switchless?
Can you check the version of the installed driver?  Was it 04/08/2010,6.0.2808.0  or 06/27/2008,6.0.627.0