This guide explains how to install and configure AIM 6.x and 7.x for use with Retro AIM Server.
Installation guides are available for the following versions:
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 the hostname from your
OSCAR_ADVERTISED_LISTENERS_PLAIN
Retro AIM Server config. For example, if
OSCAR_ADVERTISED_LISTENERS_PLAIN=LOCAL://127.0.0.1:5190
, use 127.0.0.1
.
-<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>
Install your server’s SSL certificate database generated from the server setup guide or provided by the server operator.
Copy the following files to %APPDATA%\acccore\nss
. Note that the nss
directory must be created if it does not exist.
cert8.db
key3.db
secmod.db
Tell AIM where to connect:
443
.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