[failed] dlink dwa 525 a2 (pci 11n wifi on ralink rt5360f) and 9x?

[MERCURY127]

It's can work? Someone try so?

[pangoomis]

Can't really find Windows 9x drivers for it, earliest one is for Windows 2000, I would try the Win2K driver with a modified INF and see if it works with the Odyssey Client.

[LoneCrusader]

The oldest driver package D-Link has listed for this device (1.00) of course contained only 2K+ files. However it uses DRT2860.SYS. I believe D-Link adds the "D" to the beginning of drivers, as the Internal file name for the driver is RT2860.SYS. For the heck of it I searched for "RT28609X.SYS" which led me back here to MSFN. Did we ever get a definitive answer as to whether or not the RT28609X.SYS file discussed in that linked thread works (and/or works for later RT2860 devices)?

[MERCURY127]

OK, thanks, i check all tomorrow... 

[pangoomis]

Would be nice to see the exact device ID of the exact card you have @MERCURY127 WikiDevi says it's PCI\VEN_1814&DEV_5360.

The drivers mentioned in the topic @LoneCrusader mentioned from here: https://www.download3k.com/Install-Asus-ET1602-Wireless-LAN-Driver.html support only PCI\VEN_1814&DEV_0601 and PCI\VEN_1814&DEV_0681. Those are RT2800 PCI and RT2890 PCIe chipsets respectively.

Those are dated 2007, and I'm pretty sure Ralink would not bother with 9x drivers after 2007, I think only Realtek kept making 9x drivers after 2007 until 2008.

WikiDevi also says the RT5360 chipset was approved by the FCC at the end of 2009. Seeing as the earliest drivers on the D-Link drivers are from 2010, I'm pretty sure those are the earliest ones.

So I think those older Ralink chipsets are supported, but not newer ones under 9x.

As a side note, I really would not bet on any official 9x drivers with devices manufactured after 2008 (not counting unofficial ones like the AHCI driver)

[MERCURY127]

Code 10 :(

My card is PCI\VEN_1814&DEV_5360

Edited October 9, 2018 by MERCURY127

[pangoomis]

Code 10 means dead end, sorry

[MERCURY127]

No, this is not end.

It's devids white list in driver. I replace one value 01h 06h to 60 53 and now... have vfat error... 

So i understand, me need new rlp with /m option? 

Edited October 10, 2018 by MERCURY127

[pangoomis]

Should have written it would be a dead end for me, I'm not experienced enough (though want to be!) to directly modify .sys files

Still don't understand how would that driver work, if it's made before the RT5360 even existed...unless you have a way to import stuff from the 2010 driver to the 2007 one

 

[MERCURY127]

i not sure that it work now. my system now wont boot, i have bsod with VFAT error, instaed normal boot wiith code 10 yesterday.

so, if anyone interesting, here is my patched RT28609X.SYS:
9A904 -> 01 06 00 00 - first devid (now 60 53) - dword,
9A908 -> 81 06 00 00 - sec devid - dword,
9A90C -> 14 18 00 00 - realtek vid - dword.

so u can write here own device for testing ur wifi cards.

2860.zip

[rloew]

You made the driver think you have a RT2800, so it installed and now initializes upon boot causing the VFAT problem.

Gigabit Ethernet often causes VFAT to crash, this is why I added the /M option to my Patch.

No guarantees that the Driver will actually work.

[MERCURY127]

last result (after using /m switch, or limiting of memory other methods):

- vfat bsod now gone;
- driver now is loaded successfully, w/o any errors;
- Odyssey see wifi card, provided by driver;
- but after scanning, list of networks remain empty. :(

i think, it is all. THE END.
but u can try this method (patching sys for vid/pid) with other (not so new) ralink pci cards.

Edited October 14, 2018 by MERCURY127

[rloew]

Unfortunately, I have never succeeded doing this with any Ethernet Driver so far.