ohhihohello57
|
For a while I've had problems logging in on AIM 1.0 due to the server not accepting the roast/XOR-based authentication it used, despite it working before. But as I tested more of the early clients, I realized that they don't work in one way or another. I tested (almost) all of these clients on a Windows 2000 VM and my host machine (Windows 7). These were the results:
- AIM 1.0: Doesn't install on 64-bit systems; errors out on login with "Unknown error"
- AIM 2.1: Stays at Step 2 (authentication) and does nothing
- AIM 3.0: Errors out with a "server disconnected" message
- AIM 3.5: Same situation with 2.1; when sniffing the packets sent to and from this application, it's clear that it uses MD5 authentication and authenticates successfully, but when it is introduced a BOS server (on port 5191), it doesn't attempt to connect to it
- AIM 4.7: Crashes when it reaches Step 2
Anything on or after 4.8 successfully logs in and fetches your buddy list.
I have a problem with this as these versions did work at one point, and they're also still available for download on this very site. The sudden halt of support for these clients is frustrating for people who use these affected versions or plan to and can't get to login, thinking that it's some sort of cruel joke. I suggest iWarg to get to the bottom of this problem ASAP to avoid any further complications in the future and to make sure he offers what he advertises (again, the downloads page).
~ ohhihohello57
if (Nerd->Personality == (NERD_PERSON_FRONTFACING + NERD_PERSON_SMARTALEC)) { return; }
|
![[Reply]](img/forum/topicreply2.png)