AOL Releases AIM 6.0 Beta


Recommended Posts

Someone just tried to direct connect with me, and it didn't work! I mean we got connected but I was unable to see the pictures. It worked before with someone else. What's the deal? I was away, then came back and then someone tried to direct connect with me. Maybe this is a bug? The person was using 5.9 when they tried, and my friend before when it worked was probably using the same or an even older version. Fix the UI and small things like the first letter in our screennames not being capitalized when someone messages us, get direct connect working 100%, and I'd say you got a winner on your hands. Oh yeah, and those toast windows are a little big. Might want to go back to the 5.9 size.

Someone just tried to direct connect with me, and it didn't work! I mean we got connected but I was unable to see the pictures. It worked before with someone else. What's the deal? I was away, then came back and then someone tried to direct connect with me. Maybe this is a bug? The person was using 5.9 when they tried, and my friend before when it worked was probably using the same or an even older version. Fix the UI and small things like the first letter in our screennames not being capitalized when someone messages us, get direct connect working 100%, and I'd say you got a winner on your hands.

If your screen name is an AOL screen name then this is a issue on their end. I was the one who originally brought this up with SULAX50. It seems like this format screen name thing is affecting AIM users also. :huh:

If your screen name is an AOL screen name then this is a issue on their end. I was the one who originally brought this up with SULAX50. It seems like this format screen name thing is affecting AIM users also. :huh:

My screenname isn't an AOL one, just AIM. So yeah, definitely affecting AIM users as well. It's just a small gripe. I'm more concerned with the UI of the program/chat windows and the inconsistency of direct connect with older versions.

why download a bloated version of AIM with ads when you can download a bloated version of AIM w.out ads, AIM Pro?

Because AIM Pro is intended for business users. We are CONSUMERS. AIM Pro has less features than that of AIM Triton/AIM 5.9. :turned:

I think I managed to track down the causes of my crashing while away. It seems to be coming from Gadgets (I had av props and mytunes enabled). As soon as I disabled the plugins, AIM has been running along smoothly.

OK, I will take a look as to why that is. Most likely it is a mytunes problem, though I have not personally changed the code in there recently.

OK, I will take a look as to why that is. Most likely it is a mytunes problem, though I have not personally changed the code in there recently.

Gah, Greg, read my posts afterwards. It's not gadgets. This build is just very unstable on my system. I've eliminated all variables, yet I don't have much luck.

I'm still running AIM 5.5.3572 and I've been hesitant to upgrade because of the direction AIM seems to be going in. From what I've gathered, and someone correct me if I'm wrong, AIM is striving to be more of a multipurpose application; a program to facilitate all sorts of communication and not just the AIM that many of us discovered back in the '90s.

I like the little program, that all it does is send IMs and the occasional voice conversation. I've also got numerous "improvements" for my version that would be very hard to replace if I were to upgrade. If it ain't broke, don't fix it..ya know?

Are there any features that set the latest versions of AIM apart from the older ones that are must-haves?

Much improved voice. We used "old" 90s technology for voice in AIM 5.x, but changed to use a much more industry standard call setup in addition we are using superior CODECs for BBand.

Gah, Greg, read my posts afterwards. It's not gadgets. This build is just very unstable on my system. I've eliminated all variables, yet I don't have much luck.

I may have one of my engineers PM you to see if we can get some tracing as to why you are crashing. I have just read this whole thread and I am VERY VERY concerned. It seems we have a bunch of bugs that went undiscovered in the testing phase, of course that is why its a beta 1. What I am going to do is compile a list of all the issues brought up in the thread and get our testers to either confirm we have these issues flagged already or make sure they can repro these issues and file new bugs. Its inexcusible to release software that just crashes, I will make sure that we get these issues rectified. As always thanks for your feedback we all appreciate it.

PS - AIM has always (going back to 1997) stood for AOL Instant Messenger, we never referred to it as AOL Instant Messenger internally or even externally, since the name AIM differeniated it from AOL's dial up service, high-speed, and web properties.

Thanks Greg. I want to defend AIM, but I can't keep it running so it's kind of hard to. In my latest TalkBack report, I included my screen name in the email field as requested on the AOL forums and will continue to do so in future reports.

After turning off login/logoff sounds, AIM managed to stay open all night so I guess it was the sound playback causing me to crash out. I'm going to try turning on default sounds while leaving expression sounds off to see if that changes anything.

For those interested in something lightweight check out Aim Lite that was just released:

https://www.neowin.net/forum/index.php?showtopic=500607

Sorry, an error occurred. If you are unsure on how to use a feature, or don't know why you got this error message, try looking through the help files for more information.

The error returned was:

Sorry, the link that brought you to this page seems to be out of date or broken.

I'm getting the same as bangbang - a lot of crashing.

Do what I did and disable sounds. Right now, I'm trying it with sounds on (only logon/off) but expression sounds off and it seems to be holding up also, though overnight will be the true test.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The funny thing here is that like 70% or so of the web browser users use 'Google Chrome' as web browser. What I don't understand is that why on earth would ANYONE choose 'Google Chrome' on Windows when 'Microsoft Edge' is not just better in most things, but it's already there right out of the box for the Windows users. Microsoft Edge has less data collection (yes, that's a fact), less RAM usage and is more optimized for Windows (as it's a Microsoft product) right out of the box. Sure, the way Microsoft is pushing Microsoft Edge on users might not be the best way of doing it and might need to change. But I would never choose 'Google Chrome' over 'Microsoft Edge' today anyways. I'm sure there was a period back in the days when 'Google Chrome' actually was better in most things, but that period is not today.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
    • That stupid annoying Sign in with Google on all these sites now... get the fk outta here
    • I was just being silly based on David Uzondu's comment ☺️
    • The unified inbox, when it arrives, will be a powerful argument for those who have > 1.
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!