If you mean IEEE-1394 adapter, that's FireWire.  While it is listed in the Network Connections window, you can't really use it for a network connection (possible, but not recommended).
We're guessing that you didn't even try DriverPacks (yet).
Read the "read before you post" linked in both our signatures.
Read the tutorial, build your source, then test, THEN report problems here.

In English please!

2,153

(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,163

(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,164

(7 replies, posted in 3rd Party DriverPacks)

Thanks SamLab.  Always a pleasure to have you back.

2,165

(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,166

(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,169

(7 replies, posted in 3rd Party DriverPacks)

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

2,170

(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,172

(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,173

(103 replies, posted in 3rd Party DriverPacks)

Excellent!  Keep us posted!

2,174

(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,175

(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.