This guide explains how to install and configure AIM (versions 6.0–6.1) for use with Retro AIM Server.
AIM 6.x does not expose server settings via the UI. You’ll need to edit configuration files manually.
To switch from the default Kerberos-based auth (AAM/AAMUAS) to BUCP:
C:\Program Files (x86)\AIM6\services\im\ver1_14_9_1
serviceManifest.xml
.Locate the aol.im.connect.mode
and aol.im.connect.mode2
preferences and change them from AAM
and AAMUAS
to
BUCP
:
-<preferenceDefault key="aol.im.connect.mode" scope="identity" type="string">AAM</preferenceDefault>
+<preferenceDefault key="aol.im.connect.mode" scope="identity" type="string">BUCP</preferenceDefault>
-<preferenceDefault key="aol.im.connect.mode2" scope="identity" type="string">AAMUAS</preferenceDefault>
+<preferenceDefault key="aol.im.connect.mode2" scope="identity" type="string">BUCP</preferenceDefault>
To point the client to your Retro AIM Server:
C:\Program Files (x86)\AIM6\services\imApp\ver6_1_46_1
serviceManifest.xml
.Find the aol.aimcc.connect.host.address
preference and update it to match your OSCAR_HOST
Retro AIM Server
config:
-<preferenceDefault key="aol.aimcc.connect.host.address" scope="identity" type="string">login.oscar.aol.com</preferenceDefault>
+<preferenceDefault key="aol.aimcc.connect.host.address" scope="identity" type="string">127.0.0.1</preferenceDefault>
AIM 6.x’s frontend breaks under the new JavaScript engine introduced in Windows 11 24H2. A workaround described by axelsw.it forces Windows to use an older JavaScript engine compatible with AIM 6.x.
⚠️ Downgrading the JavaScript engine is generally a bad idea, as it may expose your system to vulnerabilities fixed in newer engines. Proceed at your own risk!
To implement the workaround, create a .reg
file with the following content. Double-click the file in Windows Explorer
to apply the change.
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Internet Explorer\Main]
"JScriptReplacement"=dword:00000000