if a file version is over 4 numbers then it is a test pack (A Nightly)...

90503 is Five numbers and is therefore a test pack   (905 or 905x would be a final / official)

test packs are not intended for deployment... testing only!

But I fear that mr_smartepants is right with his answer, that you will not need it. He could only have written this a little bit more friendly.

True, sorry about that.
The .ini is only needed for those drivers that require the use of a separate installer to be run.  99% of the wireless drivers use the Microsoft configuration tool for managing wireless connections, but only a handful use a separate control panel or utility that needs it's installer executed at the correct time, that's what the .ini is for.

Where can I download the wnt5_x86-32.ini file for WLAN?

Thank You

I sent you an email with the download address of the last Beta WLAN driverpack. This file contains the *.ini you are looking for. But I fear that mr_smartepants is right with his answer, that you will not need it. He could only have written this a little bit more friendly. And even if you need it for something it may not be as usefull as you need, since it is very rudimantary at this point.

Best

Thank You

As far as I can see all requests for new drivers since June 2008 have been processed.

There are still some clean ups needed which will be done soon. If this has been done a public release candidate will be published.

Please do but be warned that I can't spend as much time with DriverPacks as I would think a native member should do.

None of us ever have the time our DriverPacks membership deserves

But the more of us who share in splitting the load the more that gets done.

IE if 100 people donated 5 minutes that is 500 minutes
- that is over 8 hours work for JakeLD to do alone ATM

Ideally would like to see two or three people adopt a pack or two.

mr_smartepants has Graphics down to a science.
- I don't even want to think about anyone else for that task...
- Nobody can do the job he does with that - and XP would be dead before we could train someone

JakeLD has the Mass storage pack down to an art.
- I have trained a handful of people to do Mass. It is an exceedingly tough learning curve.

the rest of the packs become less difficult i would say in this order. (hard to easy)

Sound
Chipset
Lan
Wan
CPU

if we had a person kick in a few Hours a month on each of those then they could stay current.
Or if we had three people perhaps one of them would have time if the other two did not

as it is it takes about 3 hours to update properly, pre-test and then release to testing team.
That is per pack time the ten DriverPacks that equals 30+ hours a month.
That is a weeks worth of work per month for one guy...
or 3 hours each for ten people or 20 min each person if we had 100

My dream would be to have 30 or 40 people who could kick in two or three hours every few months
Individuals might share a pack with two or three others.
By specializing and gaining experience in a pack or two each
the sub-team members might then be able to reduce the required time to update down to maybe 60~90 min or so (cut in 1/2).

I hope you are starting a trend!

Welcome to the testing team...

Thanks!

Changed to DP_WLAN_wnt5_x86-32_90401.7z since its a new begin it also should fit the newest naming rules.

As far as I know the most WLAN drivers that have an own configuration application are also thought to be configurated by WZCSVC (Windows Zero Configuration Service), so these apps are optional.

Please do but be warned that I can't spend as much time with DriverPacks as I would think a native member should do.

Hazaaa!

You will find stickies with the info you need
They are in the the previously hidden team forum, that you can now access...

In your filemane the "b" is ignored / extranious...
DP_WLAN_wnt5_x86-32_90401.7z is the correct equivilent. 
however DP_WLAN_wnt5_x86-32_904b1.7z  would still work just fine

um... the INI is not required,
only if there are entries to be made in the file would it then be created.
again it won't hurt to have an empty one...
but it's just excess baggage if there are not entries
- it strikes me as odd that there are not any entries...
  i would think at least one wireless adapter would need its console or app installed???

Perhaps we can talk you into joining the packs team in the near future?

DP_WLAN_wnt5_x86-32_90503


Changes since DP_WLAN_wnt5_x86-32_806
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Fixes
~~~~~
Date       Vendor  InfName Subdir Comment
2009/04/17 Atheros net5211  [At1] removed, superseded by [AtT]
2009/04/17 Atheros net5211  [AtU] removed, was the same version as [AtT]
2009/04/20 Intel   netw4x32 [I5]  removed 3 files netw4x32.*, superseded by netw5x32.*
2009/04/24 AVM     -        [AV]  removed subdirectory "client" and files not in [SourceDiskfiles] of *.inf 
2009/04/24                  .     this files restructured
2009/05/06 Ralink  rt2500   [R]   kept old version 06/01/2006,3.02.00.0000 because new version is not signed 
2009/05/06 Ralink  rt2500usb[R1]  kept old version 11/08/2006,2.01.01.0000 because new version is not signed 
2009/05/06 Ralink  rt73     [R1]  kept old version 12/21/2006,1.02.00.0000 because in new version some hw ids dropped (Belkin)
2009/05/18 Broadcombcmwl5   [BR9] removed *64.* (64 Bit support)

Updates
~~~~~~~
Date       Vendor  InfName Subdir Old Version                 New Version                 Comment
2009/04/17 Atheros netathw  [AtT] 07/26/2007,5.3.0.67         10/07/2008,7.6.1.160        tested succcesfully by JSe
2009/04/20 Intel   netw5x32 [I5]  03/13/2008,11.5.1.15        11/17/2008,12.2.0.11        updated 5 Files netw5*.*, tested succcesfully by JSe
2009/04/24 Realtek net8185  [RE2] 02/01/2007,5.1097.0201.2007 03/21/2008,5.1105.0321.2008
2009/04/24 Realtek netrtuw  [RE3] 01/11/2007,5.1273.0111.2007 06/13/2008,5.1313.0613.2008
2009/04/24 Realtek net8187b [RE4] 02/08/2007,5.1063.0208.2007 06/25/2008,5.1135.0625.2008 and now with valid *.cat file 
2009/04/24 AVM     fwlan    [AV]  07/31/2006,2.0.4.1482       12/28/2006,2.0.6.1647
2009/04/29 Ralink  rt2400   [R]   02/24/2004,2.01.00.0001     02/12/2009,2.01.00.0004     generic ID PCI\VEN_1814&DEV_0101 added
2009/04/29 Ralink  rt73     [R2]  12/21/2006,1.02.00.0000     10/21/2008,1.03.02.0000
2009/04/29 Ralink  rt2500usb[R2]  11/08/2006,2.01.01.0000     02/12/2009,2.01.01.0015     no signature but new IDs
2009/04/29 Ralink  rt61     [R3]  05/04/2006,1.01.01.0000     11/24/2008,1.02.06.0000
2009/04/29 Ralink  rt2500   [R3]  06/01/2006,3.02.00.0000     02/09/2009,3.02.00.0010     no signature but new IDs
2009/05/06 Ralink  rt2860   [R5]  07/28/2007,1.00.04.0000     03/24/2009,1.04.02.0000
2009/05/06 Atheros netathw  [AtT] 10/07/2008,7.6.1.160        12/29/2008,7.6.1.221        generic IDs PCI\VEN_168C&DEV_0013-001D,0023,0024,FF19,FF1C,FF1D
2009/05/15 Atheros net5211  [AtF] 05/25/2005,4.1.2.56         06/29/2006,5.0.0.107        generic ID PCI\VEN_168C&DEV_0012
2009/05/18 Broadcombcmwl5   [BR9] 07/11/2007,4.150.29.0       10/22/2008,5.10.38.26

New
~~~
Date       Vendor  InfName Subdir Version                     Comment 
2009/04/24 AVM     fwusbn   [AV]  08/20/2008,4.0.0.65         added FRITZ!WLAN USB Stick N
2009/05/06 Ralink  rt2870   [R6]  03/04/2009,1.04.01.0000     added Ralink 802.11n
2009/05/15 Toshiba net8187b [TO]  12/26/2007,5.1116.1226.2007 added Toshiba branding of Realtek net8187b
2009/05/15 Linksys rt73     [L1]  01/12/2006,1.00.04.0000     added Linksys WUSB54GCv1  
2009/05/15 Linksys net8187b [L1]  06/25/2008,5.1135.0625.2008 added Linksys WUSB54GCv2 another branding of Realtek net8187b 
2009/05/18 WNC     eu3nic   [WNC] 11/01/2001,2.00.09

I also created a DriverPack_WLAN_wnt5_x86-32.ini (the DPWLAN did not have an *.ini until now):

[DriverPack]
platform= "wnt5_x86-32"
name= "WLAN"
; version 9.04
classes= "net"
rootDir= "D\W"
driverCount=
decompSize=
compSize=

what is the minimum for that to be extended later.

Is there a possibility to upload this DP_WLAN_wnt5_x86-32_90401.7z to the beta site of the DriverPacks forum?
If there is any interrest I will try to make all changes requested since the last relaese DP_WLAN_wnt5_x86-32_806.7z to "my" beta version and upload it for future testing.

Edit:
2009/04/20 Changed name from DP_WLAN_wnt5_x86-32_904b1.7z to DP_WLAN_wnt5_x86-32_90401.7z
2009/04/25 Updated to DP_WLAN_wnt5_x86-32_90402.7z
2009/05/18 Updated to DP_WLAN_wnt5_x86-32_90503.7z