Transports still not working in Exodus

A long time ago I found that Exodus didn't deal correctly with
Transports such as AIM or Yahoo.  I was able to browse and then
add but they would be listed in the main window under unfiled.
I had do do some trick which I don't even remember any more
in order to get them to be listed as a transport and give me the
ability to log in and out of the transport.  Lately the transports
I had stopped working completely.  Today I found that the gateways
I had used were dead so I tried to add a new one but couldn't even
browse there any more.  Later I realized it was because I didn't
right click and choose register.  I went to a Linux computer and
tried with Gabber and it worked perfectly.  I added and registered
with the new gateway and then added some users from those IM systems.
With Gabber the AIM is listed under the Agents group.  I log out there
and go back to Exodus.  The problem is that there it is listed under
unfiled and not as an agent or transport.

Psi was able to correctly identify the Gabber added transports but
Exodus doesn't.  I also discovered that if I added a transport
in Exodus, it is added correctly to Transports and then I am
able to drag the unfiled Gabber added transports to the Transports
group.  Before I file a bug report, I would like to hear from anyone
if there might already be a fix or solution?  Right now I am using
Exodus version 0.9.0.5

Damon Register