DeadAIM 3.0 Released


Recommended Posts

A new version of DeadAIM was released. Below is from the changelog:

The following new features were added:

-Logging - The ability to search by screen names and dates.

-Logging - Log files can be easily saved to another location.

-Logging - Inline images and files are logged.

-Logging - Time stamps are always shown.

-Logging - Text background is shown correctly.

-Logging - The Log Manager now remembers its window size and position.

-Grouping of instant message windows into one tabbed window.

-Cloning; the ability to have more than one AIM client running simultaneously (NT4/2000/XP and higher only).

-DeadAIM can now add a link to its website in your profile so others viewing your information can find out about it.

-DeadAIM group in the start menu that contains a link to the Log Manager.

-"Repair DeadAIM" shortcut in the DeadAIM group that will re-associate DeadAIM with AIM after an upgrade.

-A very small lightweight program is run on system start up to check DeadAIM is associated with AIM correctly.

The following bugs were fixed:

-Logging - Date format in the log manager had an errenous '[' in some locales.

-Logging - If a picture or other binary file was inserted no more conversations were logged that day for that person.

-Logging - If Windows was shutdown or if the user logged off without first closing the IM windows then the conversations would not be saved.

-Logging - Logging could not be disabled.

-Transparency - Docking and undocking the AIM window removed transparency.

-Transparency - Clicking on the area around or using the keys to manipulate the slide control did not work correctly.

-Dependencies on new DLLs caused 2.06 not run on Windows NT 4.0 unless the IE desktop enhancement was installed.

-The installer did not prompt the user to close AIM before installing. This lead to a lot of people thinking DeadAIM did nothing as they hadn't restarted AIM.

-When Apache running on jdennis.net did not respond in a timely fashion after the connection of a socket DeadAIM would crash.

-DeadAIM would not work after upgrading AIM when using AIM's built in upgrade functionality.

-On Windows 9x platforms the user would be prompted to report their installation everytime AIM was loaded until they clicked "no".

Notes for release:

DeadAIM will now automatically check for a new version once every 24 hours instead of every sign-on. Manual checking for a new version is not effected by this change.

Download DeadAIM 3.0

Link to comment
https://www.neowin.net/forum/topic/54209-deadaim-30-released/
Share on other sites

deadAIM had, as of now, more features than AIM+ and the tabbed IM's is what people have been waiting for for a long time and now the support for cloning brings it up to and beyond AIM++.

thats. the reason i didn't want to switch from AIM+ to deadAIM was because, at the time, there was no logging feature. but once jdennis incorporated it. i immediately switched over, and have been very satisfied with it. AIM+ was too bulky for me (having to use a seperate application).

though i look forward to seeing what this new AIM+ 3.0 has to offer.

btw, where was this information about released AIM+ 3.0 on wednesday, learned from? i didn't see anything on the big-o-software website about it.

Just downloaded this and it worx great, no more need for my tabbed im window patch hahaa, Finally jdennis updated his site too looks much more better and I like the forum he put there too. This one is gonna be a tough one for big-o to beat, guess we will have to see which one is better tomorrow.

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

    • No registered users viewing this page.
  • Posts

    • Why? Does anybody actually want this? The constant need to close all browser sessions and wait for a new version to install, just so that there’s a integrated coupon manager feels like a waste of everyone’s time
    • I remember when Louis used to just do interesting Mac/iPhone repairs, now he's boring and just launches "crusades" every week
    • A shame it don't allow people to bypass the MS account, I will stick to using Rufus.
    • Microsoft about to radically change how often your Edge browser updates by Paul Hill Microsoft has just announced that starting with Edge 152, it will be moving to a two-week release cycle for faster, smaller updates. This faster release cadence will begin on August 27. This change comes just several months after Microsoft switched Visual Studio Code to weekly updates. The company said that the Extended Stable releases will remain on an eight-week cycle and that no admin changes are needed to experience the faster release cycle on the Stable channel. The new two-week release cycle will enable the faster delivery of security updates and platform improvements, all while reducing the size and complexity of individual updates. Microsoft claims that organizations will benefit from this change as it offers predictable validation cycles. For organizations that prefer a “more deliberate pace”, the Extended Stable channel remains an option. This change will affect Edge Stable releases on Windows, macOS, Linux, and mobile. The Extended Stable channel will continue to be updated every eight weeks, or every fourth Stable release, for example: versions 152, 156, 160, and 164. The Extended Stable could be a good option for organizations that don’t want the latest updates twice a month and don’t want as much hassle constantly updating browsers. In the case of Visual Studio Code, many of the updates being pushed by Microsoft are AI-related. As we all know, Microsoft Edge has a lot of AI features, so we could see Microsoft pushing more AI, thanks to the faster cycles. On the flip side, quicker releases could mean faster security updates, which is beneficial in a world where AI systems are hunting for software exploits. What do you think? Let us know in the comments. For more updates on Edge, be sure to follow Neowin's coverage. In May alone, we reported on Edge offering in-browser pop-ups to assist users with website compatibility issues, that Edge was losing Copilot Mode, and that Microsoft had fixed a plain-text password bug in Edge. Source: Microsoft 365 Admin Center
    • not yet, because at the moment it is not a threat to MS, if and I mean if it did become a threat to MS Office, then it may be a different thing. MS don't like competition
  • Recent Achievements

    • Week One Done
      davidbazooked earned a badge
      Week One Done
    • One Month Later
      Jamswaz earned a badge
      One Month Later
    • Week One Done
      Jamswaz earned a badge
      Week One Done
    • Rookie
      Marzoid went up a rank
      Rookie
    • Community Regular
      coch went up a rank
      Community Regular
  • Popular Contributors

    1. 1
      +primortal
      514
    2. 2
      PsYcHoKiLLa
      185
    3. 3
      +Edouard
      159
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!