They should...theoretically. Not strictly Alfa 036h drivers, but also working on Kasens G9000 RTL8187L here too which is what I'm mainly using at the moment. As long as the device is supported in hardware ID list in the .inf. If it's not, it's a 5 min job to add it respectively. To my knowledge from testing all sources of info, USB NETGEAR WG111v2 (RTL8187L) v4.0 drivers also work the opposite way on Alfa as long as you take the wg111v2.sys file and rename it to RTL8187.sys, and tack on your own .inf. And those Netgear RTL8187L drivers were compiled much later in April 2010, have a strange versioning system, and are even newer for Windows 7 available than what Realtek puts out on their website which only goes up to 2009 releases for Windows 7 officially. I didn't include those later versions in the drivers, because it's only applicable to use these newer drivers for Windows 7 and not XP or Vista, so I'll leave that as an exercise for the reader... So it appears that all RTL8187 driver main kernel files are interchangeable, regardless of the device... --- Double Post Merged, 2 Dec 2013 --- Update At the moment folks, having finished my mod of the RTL8187L drivers... I'm now delving deeper into extending the driver options and control available for my Alfa AWUS036NH, or any other RaLink 3070L adapter a la signal king etc... So far, I've managed to unlock some useful stuff, like selection of wireless modes (forcing 802.11b), RTS and frag thresholds, and mac address spoofing. Nevertheless, it's going to take some time. It's looking hopeful however, because the default driver options that exist by default for 036NH/Ralink drivers are very small, and give hardly no control over the adapters useful functions in any case on almost all driver's I've tried....
well at last it runs on win 7 as win 7 drivers 3.1. I did a factory reset on a cloned disk back to initial status and removed macafee which is OEM installed but did not install free avg or zonealarm again. I switched to Comodo Firewall and A/V So fa no drop outs and Comodo handles the install well with no fuss. Now I have NHR and 036H installed on win 7 So thumbs up job well done on drivers I didnt try v3 drivers but I will just to see if they install as well but I will image the disk before I play. I think I had corrupted registry which had some entrys for RTL that were not allowed to delete even on changing permissions ect. about 3 years since I had win 7 newly installed which I read average time before win 7 gets reinstalled is 18months. RegeditX is very good for removing entrys en mass in a jiffy using RegeditCrawler in the menu. I have some questions later about some of the features you unlocked but I need to look back on the utility and experiment. --- Double Post Merged, 8 Dec 2013 --- Are drivers (3.1) forced xp sp3 in win 7 working better than the win 7 standard 3.1 install? Because it feels like they are better I will have to do test with screen shoots ect for comparison with notes when I have some time. Now the homebrew runs on win 7 finally thanks to you I have a new issue but it might not be caused by the drivers 3.1 after installing. I have a network drive a Lacie ethernet disk that is connected to a netgear router as external storage. I use to connect to the NAS drive via CAT5 to the router with no problems and access the internet from the PC. After getting HB 3.1 installed I dont have an internet connection but I am connected to the network and ONLY if I disconnect the cat5 cable from the PC do I get a connection to the Internet as soon as cable is reconnected there is no internet. I took a screen shot for the settings see pic --- Double Post Merged, 12 Dec 2013 --- Currently I have on win 7 036H, NHR and now Installed NHR V2. Installation was painless strange thing ( i thought read somewhere you need to uninstall V1 before V2) is I can unplug NHR with NHR V2 with no problems they both work. Looking at the driver installed its running V2 and both Alfa's like it even after a few reboots. Judging from the signals it appears that this V2 driver works or uses a different method of calculating signal strength and link quality and is better and runs on both with no issues so far but time will prove its OK. I
If you think about it....5 bars of signal is meaningless, because there is no defined standard as to what one bar represents. They can just about program the driver to report any signal strength they want ie. real SS x by an X factor, doesn't mean it's correct or stable or even accounts for any interference you can't even see, or even wholly represents the full performance or capability of the adapter. I think practical testing of range comparisons head to head, and word of mouth of how popular a device is, tested under controlled conditions is the only real answer because there is no "one size fits all" adapter or golden egg irrespective of the multitude of marketing hype. I have a sneaky feeling my 8187L based adapters also exaggerates it's figures somewhat, and others are guilty also of faking to an extent their values... Notice how no one ever dares to gives concrete range figures... Here in Europe anyway where the output power is unfairly weak, you cannot exceed 100mw regardless of the power or flashy range claims produced on the adapter's box, which means the TX output will not exceed 100mw *regardless* of antenna used. And it will not influence EIRP, just help more to receive. So now you have all this boosted "reception" yet still no further "range". Since wireless connection is a two way street, exceeding the power would do you no good at all since everyone else's AP's in Europe is also limited in their TX output even though you may be not anymore and still using comparatively weak router antenna's more likely than not, so they can't transmit back reliably either. There are some adapters out there that can hold a connection all day long on 1 bar, then there are those that show 5 bars for everything yet cannot connect to half of them despite when the "apparent" SS being indicated strong. Or they will connect, but the behaviour is not by any account a "5 bar" connection like it says it is, because you only get a trickle of data. It's all relative and meaningless the values shown most of the time and varies from chipset to components used to adapter...Only 3 things really matter.... good connection, bad connection, or no connection. Everything else is endless blather...
I have installed 3.1 for my Kasens G9000 and everything appears to be fine, the adapter doesn't seem any better or worse. I had already unlocked several things by editing the 8187.ini for my 2010 drivers so I had the Power TX slider and some added options in the Advanced Tab. I have the domain set to FCC in device man and advanced tab.
Even if you experience no improvements to certain brands of RTL8187L adapter which may consist of many variables, useful extra functionality for all 8187L based adapters is still unlocked... Such as the ability to force on all specific data rates etc, which may carry your connection that little bit "further", and driver options for certain OS's that have been missing have been restored for consistency across all OS versions. The ability to toggle things that were not available or toggleable before so you may have more options in front of you to play around with. The GUI is an updated version...It's completely been tidied up, unlocked, cross checked on different OS for accuracy, well rounded, re-working every .inf and .ini file for several OS and taking the best parts from everything out there. I just did the best I could with what there was out there available, because I wasn't satisfied with the default ones because of too many omissions, mistakes, flakiness and inconsistencies and limited options...
How could I set power to max 30 dBm? There is only max 5 dbm in CCX page of utility. Sorry for a stupid question of a newbie.
Thank you for your reply. I thought like you but the power in CCX page is change with TX power slider (ex. TX=60%, CCX dbm = 3 dbm). So, it think the power may be limited by dBm in CCX page but that is all my guess.
I have been working on the Ralink (036NH) drivers, but it may take some time. I have been able to unlock specific Wireless modes (b/g/n) selection, and MAC address spoofing, which is more than the default drivers offer. But not specific data rates as of yet. In the meantime the latest version available for Ralink 3070L out there is 5.1.7.0 (all OS) which was put out fairly recently. Also there doesn't seem to be an AR9271 section (036NHA) on here, so with that in mind, I'm going to create one...
I think you will find.... (and I'm beginning to seriously believe) ALFA screwed up and shipped the wrong driver disc in the box with the NHR V2's. The V2 driver disc has black stripes 1012.131.2011 driver The V1 driver disc has blue stripes 1024.2 0618.2013 Except, with the V2 you will most likely have a disc with blue stripes which will be the NHR v1 drivers. If you install those V1 drivers on your V2, the signal strengths, RSSI, and amount of bars will all be messed up compared to installing 1012.131.2011. When you go to ALFA to find or download a V2 driver, it takes you to 1012.131.2011 instead and the signal strengths read out ok if not perfect because the NHR is junk and the receiver is messed and no good at all with the standard 5dbi unlike the others, which smells to me like it doesn't have the range it claims it has. While the new drivers appear to work on the V2. Output power seems reduced. I've emailed ALFA over this apparent cock up with the driver versions and shipping incorrect discs in the box, but got no reply. You will think your adapter is busted using those 1024.2. drivers out of the V2 NHR's box, the signal strengths can and will be reported completely silly, like 8% and stuff for networks. Not true on 1012.131... You would think an August 2013 adapter would likely need this "new" driver. Not so according to the ALFA page on the V2 driver download ! Resultingly, if my assertions are correct. There is then no "compatible" NHR V2 driver for Windows 8 or 8.1 as of yet... They say you cannot use V1 drivers on V2, but they don't tell you why. After the early death of lot's of V1's floating around, I'm not going to risk using the wrong driver for V2.
LOL ... you confused me now about which CD is which but I mixed up V1 & V2 disks anyway. Looks like Im running driver ...2013 not ...2011 on my V1 and V2 is put aside for backup now. So what your saying is using V1 drivers on a V2 adapter will work (not so well) but doing so will destroy the adapter in time? Perhaps thats if power is maxed out? The funny thing is my 036H does get warm and neither V1 or V2 gets as warm. I dont have win8 to try but Im guessing force the drivers on install in win8 to run in win7 mode or vista should work? Alfa will respond if you mention you suspect you have a fake product and throw in your question again as a side issue. Im sure they will respond this time round. Update on your homebrew 036H, I now have stability and no issues in both vista and win 7 32 bit, Thanks for the sharing V1 NHR on ....2013 driver pulls in weak signals and holds where V2 on ...2013 driver will not and 036H sees nothing that V1 does when weak on 1-2 bar. When I say weak signal I have all metal roller shutters closed all around the house and the signal bleads in and gets sucked in with NHR V1 running 1024.2 0618.2013 driver. Its amazing compared to the V2 and 036H and signal king Im running V1 as everyday and it runs cool, well the outside housing case is cool but it might be a bit warm on the chipset but I doubt it. Where you say NHR is junk?? is that V1 or V2 running their correct drivers? Any readers with issues on 036H should try the home brew drivers latest offerings by kevsamiga
Try switching your 5dbi antenna out on the V2, mine came broken as new and wouldn't connect to weak signals, but the Antenna works on other adapters but the NHR likes to be using the 5dbi off of my 036NH atm where it then works with weak signal. Totally weird as hell in the extreme. Where to buy or get hold of an specific NHR v1 these days ? I don't wanna order and get a duplicate V2 because this is what everyone is going to be eventually shipping. Would you say the V2 is weaker than V1 ?, some tests I found find the v2's RSSI better and it has the same output figures, but the PCB inside is half the size of v1's. My V2 holds fine on 2013 driver btw ! Especially with the bad 5dbi changed for another. On the page for the V2 they say you shouldn't be using V1's driver, and on the page for the v1 they say in reverse you shouldn't be using V2's driver. But as to which is which is a mystery. Why the hell would the V1 have newer drivers+Windows 8 support than the V2 when it's actually a newer model from 2013 ? It looks that way at the ALFA site. Only ALFA could come up with this crap, and I can't find out anymore info because the V2 is still relatively new as it were. I'm almost sure early on in it's life, the V1 shipped with 1012.1.131.2011 as well, but when you click on the link to d/l driver for V2 this is exact stupid old version you get. £%%£%^ Confusing... Which driver is which is confusing because the V2 adapter is 2013, v1 is 2011, therefore you would expect to be using the 2013 driver on V2 and not the other way around, but if you do all the signal strengths are messed up. However my V2 holds on these drivers but I don't get as much noise inductance feedback in the PC stereo speakers when transmitting as the 1012.1.131.2011's do which leaves me to believe TX on these new drivers for V2 is weaker, but out of the box as brand new, the V2 autorun goes ahead and installs 2013 driver for the V2 ! Utter bollox. The V2 claims Windows 8 support on the box, the V1 does not (only up to Win7). The 2013 driver has Windows 8 support, the 1012.1.131.2011 does not, but yet still at the alfa site this is *supposed* to be the right V2's driver, it even says it in the god damn filename you download. So why do they ship and install the 2013 one in the box ?!? And why should the V2 be devoid of any Windows 8 support when on the box claims it does. This is not the driver offered at the V2's download page for the ALFA NHR v2. I don't actually have a reason why you shouldn't be using each others drivers, because they didn't/couldn't be bothered to explain why you can't, or why you shouldn't be. Or what the dangers are. So almost all people buying the V2's are going to be using probably the wrong drivers for it, because they don't know or wasn't told what the right drivers actually are. So it looks like someone at ALFA has played a sick joke with the V2's, and the disks or boxes, I cannot find the answer for... I've had this piece of :censored NHR v2 new now for over 2 weeks and I still don't know what the £^$%^$%^ correct drivers are for it, since they both work ok with it (despite the signal strengths misreported). Sorry man, but ALFA aint into replying to my emails despite buying through the only UK authorised seller, and the right answer to this utter confusion with the different models, and different drivers they don't specify version numbers for which is which is really beginning to "£$£"$"£ me off.
Thank you for sharing your work. This is something that should have come from the vendor, if they knew what was good for them, they would cut you a deal to distribute your work. From what I have found so far at the usage standpoint, it's flawless. Not only correcting malfunction from the vendor version, but enabling hardware functionality they had left out.... and I understand that when you work towards something where your efforts are only going to be be compensated by the appreciation you receive, every bit counts! I encourage everybody who has made use of work by someone else to at least show your appreciation with a simple "thanks". It means all the difference and encourages people to keep developing their work. I do have a quick question about the Alfa utility. Is there a way of manually connecting to networks using the network profiles? I don't always want to automatically connect to a default network, but like the ability to save the credentials of multiple networks for ease of connection. This is achieved easily in the default windows wireless connection manager with a check box "Connect Automatically" but I cannot find any such option in the Alfa utility.
yep I was looking too, I just have a dummy network as default ie a SSID that I just entered a random (wrong) password and thats set as the default but of course it will never connect but having saved networks as profiles I just double click on a profile saved and set as default to connect manually
Unfortunately the auto connect feature was implemented much later in WLan utility.. (I think) l will see what I can fish out about it.
