Jump to content











Photo

Load (or integrate) new WLAN driver?

wlan driver

  • Please log in to reply
9 replies to this topic

#1 xerces8

xerces8

    Newbie


  • Members
  • 19 posts
  •  
    Slovenia

Posted 30 December 2012 - 04:47 PM

Hi!

 

My WLAN adapter is not supported by HBCD 15.2 mini XP

 

I start both the "Network Setup" and "Wireless Setup" icons on the desktop, but the WLAN adapter is not detected.

 

I checked the XpDrvWLAN.7z file and it seems, this device is not supported there.

 

I have the correct drivers (inf,cat and sys file) on my USB key. Is there a way to load them?

Normally I would use Device Manager for that, but it does not show the WLAN device at all.

The PCI32 from the "Device Drivers" menu lists it. Also the WLAN LED is lit.

 

Can I just add the driver files to the XpDrvWLAN.7z archive and it will be picked up the next time I boot it?

 

 

details:

 - Asus EEE 1025C netbook

 - WLAN: Atheros Azurewave AR9002WB-1NG , PCI ID: 168C 002B , subysytem ID 2c371a3b , subsystem vendor ID 1a3b

 - booting HBCD from USB key



#2 sbaeder

sbaeder

    Gold Member


  • .script developer
  • 1335 posts
  • Location:usa - massachusettes
  •  
    United States

Posted 30 December 2012 - 06:24 PM

Hi!
 
My WLAN adapter is not supported by HBCD 15.2 mini XP
 
I start both the "Network Setup" and "Wireless Setup" icons on the desktop, but the WLAN adapter is not detected.
 
I checked the XpDrvWLAN.7z file and it seems, this device is not supported there.


Not surprised, since even if some of the other tools were recently updated, I doubt that they are trying to put new HW drivers into such an OLD OS (i.e. XP, while still used a lot is rather "long in the tooth")  :wheelchair:

I have the correct drivers (inf,cat and sys file) on my USB key. Is there a way to load them?
Normally I would use Device Manager for that, but it does not show the WLAN device at all.
The PCI32 from the "Device Drivers" menu lists it. Also the WLAN LED is lit.
 
Can I just add the driver files to the XpDrvWLAN.7z archive and it will be picked up the next time I boot it?

Maybe...I haven't looked at them in a long time, but in looking at it quickly today, it looks like you should be able to add the files... But then you would also have to repack the iso, etc...

Just a reminder that depending on the rules of you particular country, this may be an "illegal" file (i.e. the "mini-XP", since it contains unlicensed MS intellectual property. But you probably knew that already... :nuke:

 

:cheers:

Scott



#3 xerces8

xerces8

    Newbie


  • Members
  • 19 posts
  •  
    Slovenia

Posted 30 December 2012 - 09:57 PM

The wikipedia article (http://en.wikipedia..../Hiren's_BootCD) mentions some rumors that Windows 7 was added, but I don't see it...

 

Anyway, I added a newer atheros driver (10.0.0.54) to XpDrvWLAN.7z and it now kind of works.

 

When I start "Wireless Setup", the WLAN adapter appears in Device Manager with an exclamation mark, and there I can then Reinstall the driver.

I takes the one from its own system32 folder, so I wonder, why doesn't it just work the first time...

 

But anyway, after reinstalling it from DM, the adapter works, so I guess problem solved.

 

Maybe is is somehow in conflict with the old athw.sys file (the one already shipped in HBCD).

 

PS: After installing the driver (just click next, when ask for location, select X:\I386\System32\drivers , it should be already in the drop down menu), it ask for a reboot, but it works fine without a reboot.


Edited by xerces8, 30 December 2012 - 10:00 PM.


#4 Sha0

Sha0

    WinVBlock Dev




  • Amount:

    Developer
  • 1682 posts
  • Location:reboot.pro Forums
  • Interests:Booting
  •  
    Canada

Posted 30 December 2012 - 11:24 PM

Maybe is is somehow in conflict with the old athw.sys file (the one already shipped in HBCD).

It is likely because the OEMxxxx.INF file inside the X:\Windows\Inf\ directory does not contain the PCI IDs, so does not associate the device with the driver.



#5 xerces8

xerces8

    Newbie


  • Members
  • 19 posts
  •  
    Slovenia

Posted 31 December 2012 - 04:32 AM

So is there anyone (or some document) who knows what the correct way to add a driver is?



#6 Agent47

Agent47

    Frequent Member


  • Advanced user
  • 164 posts
  •  
    India

Posted 01 January 2013 - 04:16 AM

There are two Ways to do this.

 

(1)Use Penetwork's Drvcopy function:

 

to use this feature obtain the correct unpacked wlan driver(preferably backed up by using some driver backup tool from installes os),then add this driver to "HBCD\XP\Drivers" folder.When HBCD boots startup cmd will automatically search this location and add any LAN or Wlan driver it founds.

 

(2) Use Driver import PE 1.3 free version

 

DIPE is an excellent tool to add drivers to a XP based PE.You can extract DIPE 1.3 package from Live XP script.Detailed instructions can be seen on the following link.

 

http://reboot.pro/in...?showtopic=5213



#7 reboot12

reboot12

    Frequent Member


  • Advanced user
  • 215 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, Coreboot
  •  
    European Union

Posted 29 April 2013 - 03:19 PM

In HBCD 14 file XpDrvWLAN.uha have my wifi driver (athw.sys & netathw.inf). For this use need:

  • Uncomment line REM call Wireless in XpCustomise.cmd

     

    or to load only one Wifi driver

     

  • not uncomment, make folder HBCD/XP/Drivers and copy to him *.sys and *.inf files my wifi card winxp driver. Tested with other drivers: ar5211.sys & net5211.inf - oryginal from Drivers CD Wifi card

But in both way have Ethernet Controller in Device Manager with exclaim. Now if manually install driver from HBCD/XP/Drivers folder this works good.

 

This is problem only with Atheros chipset wifi card. With other e.g. Intel 4965 Wifi auto-installation driver working good.

 

P.S. How auto config WLAN - WEP or WPA ? Maybe autoimport xml file but how?


Edited by reboot12, 29 April 2013 - 03:22 PM.


#8 reboot12

reboot12

    Frequent Member


  • Advanced user
  • 215 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, Coreboot
  •  
    European Union

Posted 07 May 2013 - 12:16 PM

It is likely because the OEMxxxx.INF file inside the X:\Windows\Inf\ directory does not contain the PCI IDs, so does not associate the device with the driver.

I check Device Instance Id PCI\VEN_168C&DEV_001A&SUBSYS_1052168C in WinXP installed driver and the same string - inclusive SUBBSYS_ is present in .inf file. After WinPE boot in device manager is like this:

4004655500_1367929610_thumb.jpg

Now if try manually install drivers appears these messages:

8034565200_1367929610_thumb.jpg

4660347700_1367929609_thumb.jpg

Why WinPE prompt for path?


Edited by reboot12, 07 May 2013 - 12:36 PM.


#9 reboot12

reboot12

    Frequent Member


  • Advanced user
  • 215 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, Coreboot
  •  
    European Union

Posted 31 July 2013 - 08:23 AM

To resolve autoinstall driver problem need edit net5211.inf file and delete some lines:

In the sections of the inf file:
[ATHER_DEV_001A.ndi.NT]
and
[ATHER_DEV_1052.ndi.NT]

delete these 2 lines:
DelFiles        = ATHER.DelIniFiles
DelReg          = 5211.DelReg

But now have other problem. No autostart Wireless Zero Config service :-(. As a result, the wifi connection is not working.

4207127.png


Edited by reboot12, 31 July 2013 - 08:55 AM.


#10 reboot12

reboot12

    Frequent Member


  • Advanced user
  • 215 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, Coreboot
  •  
    European Union

Posted 05 August 2013 - 05:19 PM

OK, I found solution :-). Need make PENetwork.ini like this:

[PENetwork]
ProfileDefault=My
UseProfileSelect=No
UseProfileCountdown=No
ProfileCountdown=5
AutoStart=Yes
FocusNo=No
UseStartCountdown=No
StartCountdown=10
StartMode=1
UseProfiles=Yes

[NetProfiles]
My=

[My]
Computername=MINI-XP
Workgroup=GRUPA_ROBOCZA
NetAdapter1.UseDHCP=1
NetAdapter1.IP=
NetAdapter1.SM=
NetAdapter1.DG=
NetAdapter1.DNS=
NetAdapter1.WINS=
NetAdapter1.MAC=
NetAdapter1.Filter=
StartSharing=
ShareAll=
NetPath=
Desc.Line1=Use DHCP for IP
WiFiProfile.SSID1=name_ssid
WiFiProfile.Key1=key
WiFiProfile.Auth1=WPA2-PSK
WiFiProfile.Enc1=AES
WiFiProfile.Auto1=Yes
WiFiProfile.Hidden1=No
WiFiProfile.Adhoc1=No

It works even when the system is two cards: LAN & WLAN - both config from DHCP OK

 

No need config NetAdapter2






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users