Thanks for this update, I was starting to pull my hair out trying to work out why WPA (and therefore WPA2 via the regedit) had disappeared from the ralink utility after I uninstalled and reinstalled the drivers. Got them back now, and my Dell Latitude 233MMX has now card WiFi connectivity. Thanks!

Hello,
I've figured how to enable the WPA2 setting on the RaUI.exe. I did add a post about this on https://cloakedthargoid.wordpress.com/win9x-wpa2/, but I figure I'd comment here as well.
I only worked with version 1.3.5.0 (which comes from “IS_AP_STA_2500_D-3.2.0.10_VA-3.2.0.0_RU-2.1.3.0_VA-2.1.3.0_AU-2.0.3.0_VA-2.0.3.0_021209_1.0.1.0_Free.exe”.

In short, use a hex editor, like XVI32, open RaUI.exe (the one that's NOT in the "common" directory, the one that auto-starts with Windows; but I guess it wouldn't hurt to modify all of them), and locate the following positions. They should be a 07 in hex. Change (modify, NOT insert!) all of them to 04.

0xA394
0xD0F5
0xD689
0xD6BC
0xDD37
0xDD65
0x27281
0x272AF
0x2BF00
0x2BF3C
0x2D854
0x2D8B4

These are offsets within the .exe file, i.e. linear offsets on the file. Don't continue if any of these positions contain a byte different than 07 in hex.

Please make a backup before editing the file. You have to close the Ralink tool in order to modify the .exe.

I can explain in further detail what's been patched here, but basically, Ralink made a mistake on their code. Seems they didn't want WPA2 on Win9x, thus all these places were checking if the Windows version was above 9x (apparently). Because we know it works on 9x, I've lowered the check to the actual value they use for Win9x (which is a value of 04, 07 is a newer version).

If you have another RaUI exe that needs to be patched, attach it here or send it to me and I'll have a look.

Thanks!

cocus wrote on 2025-10-17, 02:42:

These are offsets within the .exe file, i.e. linear offsets on the file. Don't continue if any of these positions contain a byte […]
Show full quote

These are offsets within the .exe file, i.e. linear offsets on the file. Don't continue if any of these positions contain a byte different than 07 in hex.

Please make a backup before editing the file. You have to close the Ralink tool in order to modify the .exe.

I can explain in further detail what's been patched here, but basically, Ralink made a mistake on their code. Seems they didn't want WPA2 on Win9x, thus all these places were checking if the Windows version was above 9x (apparently). Because we know it works on 9x, I've lowered the check to the actual value they use for Win9x (which is a value of 04, 07 is a newer version).

If you have another RaUI exe that needs to be patched, attach it here or send it to me and I'll have a look.

Thanks!

Hi @cocus,

Good work for finding how to enable WPA2 on Ralink Config UI.

I've ported your work on the 1.3.6.0 version and it's confirmed it works also on this newer version.

Here the new offsets (1.3.6.0 newer version) :

- 0xA2F3
- 0xD054
- 0xD5E8
- 0xD61B
- 0xDC96
- 0xDCC4
- 0x2728B
- 0x272B9
- 0x2BF0A
- 0x2BF46
- 0x2D85E
- 0x2D8BE

I’ve also premade the exe changes for both 1.3.5.0 and 1.3.6.0.

Download : https://tgames.fr/tgames/PC/RaUI_WPA2Mod.zip

The zip contains the original exes and their modded versions.

TgamesFR wrote on 2026-01-17, 21:47:

Hi @cocus, […]
Show full quote

cocus wrote on 2025-10-17, 02:42:

These are offsets within the .exe file, i.e. linear offsets on the file. Don't continue if any of these positions contain a byte […]
Show full quote

These are offsets within the .exe file, i.e. linear offsets on the file. Don't continue if any of these positions contain a byte different than 07 in hex.

Please make a backup before editing the file. You have to close the Ralink tool in order to modify the .exe.

I can explain in further detail what's been patched here, but basically, Ralink made a mistake on their code. Seems they didn't want WPA2 on Win9x, thus all these places were checking if the Windows version was above 9x (apparently). Because we know it works on 9x, I've lowered the check to the actual value they use for Win9x (which is a value of 04, 07 is a newer version).

If you have another RaUI exe that needs to be patched, attach it here or send it to me and I'll have a look.

Thanks!

Hi @cocus,

Good work for finding how to enable WPA2 on Ralink Config UI.

I've ported your work on the 1.3.6.0 version and it's confirmed it works also on this newer version.

Here the new offsets (1.3.6.0 newer version) :

- 0xA2F3
- 0xD054
- 0xD5E8
- 0xD61B
- 0xDC96
- 0xDCC4
- 0x2728B
- 0x272B9
- 0x2BF0A
- 0x2BF46
- 0x2D85E
- 0x2D8BE

I’ve also premade the exe changes for both 1.3.5.0 and 1.3.6.0.

Download : https://tgames.fr/tgames/PC/RaUI_WPA2Mod.zip

The zip contains the original exes and their modded versions.

Nice! Thanks for your contribution! I'll try these new drivers some day in the future, as the 1.3.5.0 are not particularly stable enough. Or maybe it's the Win9x being Win9x. 😀

cocus wrote on 2025-10-17, 02:42:

Nice! Thanks for your contribution! I'll try these new drivers some day in the future, as the 1.3.5.0 are not particularly stable enough. Or maybe it's the Win9x being Win9x. 😀

The 1.3.6.0 for me is very stable on Windows 98.

The only bug Windows 98 have (not related to this at all) is if you setup 2 networks cards and if one cannot make his IP with DHCP (for normal reasons like if network is unplugged/unreachable).
It will anyway takes the last IP set and will thinks it's connected successfully and that's a cause of many problems.

In that case all internet traffic will be stuck until the 2nd card manage to really connect because even if card 1 is really connected, no ping/out trafic will works.
That's a known bug on Windows 98, fixed on NT systems (2000 and up).
Microsoft never bothered to fix it even if the problem was reported many times to them.

To fix that i've made a registry script who allow to disable the auto-connection of the Wifi card (profile set to disabled, DHCP last settings removed) if your router/isp wifi is off for example.
That script is really useful if you using a NAS over your network for files and it requires to login on Windows 98 Login Prompt successfully.

Few things...

- Edit in the script the 0002 if your Wifi Card is not at that ID in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Net\0002
- Edit 00000FFFFFFFFF to the ID corresponding to the DHCP binding of your Wifi Card.
- Edit DhcpInfo01 if your Wifi Card is not the matching DHCPINFO in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\DHCP\DhcpInfo01
- Run the script, on next reboot the issue will be gone
- Just reopen the RaLink Config UI and active your Profile if you want wifi back. Then next time relaunch the script to shutdown the wifi side if needed.

1REGEDIT4
2
3[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Net\0002]
4"CurProfile"=""
5"PreambleType"="0"
6"AuthenType"="0"
7"Encryption"="1"
8"WSC"=-
9"SSID"=-
10"ACPowerCam"=-
11"TXPower"=-
12"UseRts"=-
13"UseFrag"=-
14"LeapEnabled"=-
15"LeapUserName"=-
16"LeapPassword"=-
17"WPAPSK"=-
18"WEPKey1Type"=-
19"WEPKey2Type"=-
20"WEPKey3Type"=-
21"WEPKey4Type"=-
22"Use8021X"=-
23"AuthenProtocol"=-
24"TunnelProtocol"=-
25"ID"=-
26"Password"=-
27"TunnelID"=-
28"TunnelPassword"=-
29"SessionResumption"=-
30"PasswordMode"=-
31"UseClientCert"=-
32"UseServerCert"=-
33"ClientCertLen"=-
34"ClientCertData"=-
35"ServerCertLen"=-
36"ServerCertData"=-
37"ServerName"=-
38"NameRule"=-
39"IntermediateCert"=-
40
41[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Net\0002\Default]
42"CurProfile"=""
43"PreambleType"="0"
44"AuthenType"="0"
45"Encryption"="1"
46"WSC"=-
47"SSID"=-
48"ACPowerCam"=-
49"TXPower"=-
50"UseRts"=-
51"UseFrag"=-
52"LeapEnabled"=-
53"LeapUserName"=-
54"LeapPassword"=-
55"WPAPSK"=-
56"WEPKey1Type"=-
57"WEPKey2Type"=-
58"WEPKey3Type"=-
59"WEPKey4Type"=-
60"Use8021X"=-

61"AuthenProtocol"=-
62"TunnelProtocol"=-
63"ID"=-
64"Password"=-
65"TunnelID"=-
66"TunnelPassword"=-
67"SessionResumption"=-
68"PasswordMode"=-
69"UseClientCert"=-
70"UseServerCert"=-
71"ClientCertLen"=-
72"ClientCertData"=-
73"ServerCertLen"=-
74"ServerCertData"=-
75"ServerName"=-
76"NameRule"=-
77"IntermediateCert"=-
78
79[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\DHCP]
80"00000FFFFFFFFF"=-
81
82[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\DHCP\DhcpInfo01]
83"DhcpIPAddress"=hex:00,00,00,00
84"DhcpSubnetMask"=hex:ff,ff,00,00
85"DhcpServer"=hex:ff,ff,ff,ff
86"DhcpDesiredIPAddress"=hex:00,00,00,00
87"Lease"=hex:ff,ff,ff,ff
88"LeaseObtainedTime"=hex:40,5d,9f,56
89"T1"=hex:ff,ff,ff,7f
90"T2"=hex:ff,ff,ff,7f
91"LeaseTerminatesTime"=hex:ff,ff,ff,7f
92"IPAutoconfigurationAddress"="169.254.117.97"
93"AddressType"=dword:00000001

TgamesFR wrote on Yesterday, 10:22:

The 1.3.6.0 for me is very stable on Windows 98. […]
Show full quote

cocus wrote on 2025-10-17, 02:42:

Nice! Thanks for your contribution! I'll try these new drivers some day in the future, as the 1.3.5.0 are not particularly stable enough. Or maybe it's the Win9x being Win9x. 😀

The 1.3.6.0 for me is very stable on Windows 98.

The only bug Windows 98 have (not related to this at all) is if you setup 2 networks cards and if one cannot make his IP with DHCP (for normal reasons like if network is unplugged/unreachable).
It will anyway takes the last IP set and will thinks it's connected successfully and that's a cause of many problems.

In that case all internet traffic will be stuck until the 2nd card manage to really connect because even if card 1 is really connected, no ping/out trafic will works.
That's a known bug on Windows 98, fixed on NT systems (2000 and up).
Microsoft never bothered to fix it even if the problem was reported many times to them.

To fix that i've made a registry script who allow to disable the auto-connection of the Wifi card (profile set to disabled, DHCP last settings removed) if your router/isp wifi is off for example.
That script is really useful if you using a NAS over your network for files and it requires to login on Windows 98 Login Prompt successfully.

Few things...

- Edit in the script the 0002 if your Wifi Card is not at that ID in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Net\0002
- Edit 00000FFFFFFFFF to the ID corresponding to the DHCP binding of your Wifi Card.
- Edit DhcpInfo01 if your Wifi Card is not the matching DHCPINFO in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\DHCP\DhcpInfo01
- Run the script, on next reboot the issue will be gone
- Just reopen the RaLink Config UI and active your Profile if you want wifi back. Then next time relaunch the script to shutdown the wifi side if needed.

Copy code to clipboard

1REGEDIT4
2
3[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Net\0002]
4"CurProfile"=""
5"PreambleType"="0"
6"AuthenType"="0"
7"Encryption"="1"
8"WSC"=-
9"SSID"=-
10"ACPowerCam"=-
11"TXPower"=-
12"UseRts"=-
13"UseFrag"=-
14"LeapEnabled"=-
15"LeapUserName"=-
16"LeapPassword"=-
17"WPAPSK"=-
18"WEPKey1Type"=-
19"WEPKey2Type"=-
20"WEPKey3Type"=-
21"WEPKey4Type"=-
22"Use8021X"=-
23"AuthenProtocol"=-
24"TunnelProtocol"=-
25"ID"=-
26"Password"=-
27"TunnelID"=-
28"TunnelPassword"=-
29"SessionResumption"=-
30"PasswordMode"=-
31"UseClientCert"=-
32"UseServerCert"=-
33"ClientCertLen"=-
34"ClientCertData"=-
35"ServerCertLen"=-
36"ServerCertData"=-
37"ServerName"=-
38"NameRule"=-
39"IntermediateCert"=-
40
41[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Net\0002\Default]
42"CurProfile"=""
43"PreambleType"="0"
44"AuthenType"="0"
45"Encryption"="1"
46"WSC"=-
47"SSID"=-
48"ACPowerCam"=-
49"TXPower"=-
50"UseRts"=-
51"UseFrag"=-
52"LeapEnabled"=-
53"LeapUserName"=-
54"LeapPassword"=-
55"WPAPSK"=-
56"WEPKey1Type"=-
57"WEPKey2Type"=-
58"WEPKey3Type"=-
59"WEPKey4Type"=-
60"Use8021X"=-

…Show last 33 lines

61"AuthenProtocol"=-
62"TunnelProtocol"=-
63"ID"=-
64"Password"=-
65"TunnelID"=-
66"TunnelPassword"=-
67"SessionResumption"=-
68"PasswordMode"=-
69"UseClientCert"=-
70"UseServerCert"=-
71"ClientCertLen"=-
72"ClientCertData"=-
73"ServerCertLen"=-
74"ServerCertData"=-
75"ServerName"=-
76"NameRule"=-
77"IntermediateCert"=-
78
79[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\DHCP]
80"00000FFFFFFFFF"=-
81
82[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\DHCP\DhcpInfo01]
83"DhcpIPAddress"=hex:00,00,00,00
84"DhcpSubnetMask"=hex:ff,ff,00,00
85"DhcpServer"=hex:ff,ff,ff,ff
86"DhcpDesiredIPAddress"=hex:00,00,00,00
87"Lease"=hex:ff,ff,ff,ff
88"LeaseObtainedTime"=hex:40,5d,9f,56
89"T1"=hex:ff,ff,ff,7f
90"T2"=hex:ff,ff,ff,7f
91"LeaseTerminatesTime"=hex:ff,ff,ff,7f
92"IPAutoconfigurationAddress"="169.254.117.97"
93"AddressType"=dword:00000001

I'll keep this handy, since I'm running this card on a mini PCI slot on a laptop, which already has an ethernet card. But I never faced any of these issues, interestingly enough.

My machine becomes unstable when the WiFi cars doesn't connect on boot to the AP, for instance. If it does, then Windows won't "hang". I have some eye candy there, which might be the cause of many of these problems (Revolutions Pack 7), but I remember having some of these issues even before installing RP7. Even after all of these issues, I installed KernelEx with the latest updates (the ones I understood how to install, since the updates are scattered around a mega-post in msfn), and that probably won't help to the overall system stability.

Hardware issues aren't discarded either, as I figured there might be dirty/corroded contacts om the SODIMM memory (installed 2GB of ram on a Dell latitude C640, and 1GB is the maximum supported). Ah, I also installed the patch for the ram, since I have more than 512MB. But you know, all of these things are part of my issues when I play with my retro gear.