Dear Rodney,
We have pulled 1.1.1.95 and moved the current version back 1.1.1.92 for the reasons you indicated.
The stack overflow has to do with faulty entries in the Server's Address book for some sites causing an overrun during the index creation. It can happen even when the client is in scheduler mode, so its not related to close after fetching mode.
We have experienced some problems with the .95 Profile editor hanging on conversion and failing to respond after downloading the first profile.
We recommend any sites running 1.1.1.95 go to the help-->update AllTalk and follow the instructions. This will return the site back to 1.1.1.92.
Unfortunately, the bug fixes in 1.1.1.95 which addressed the problem of "random" authentication failure profile editor key download will come back to haunt us.
After the AAPP descision (now several weeks overdue) we will have a better idea of the time-frame for addressing these problems and will get back to you with a date for 96 release
Thanks
Glen.
From: alltalk-avp@... [mailto:alltalk-avp@...] On Behalf Of rodneyebird
Sent: Wednesday, 18 July 2007 9:34 AM
To: alltalk-avp@...
Subject: [alltalk-avp] Bugs
Sent: Wednesday, 18 July 2007 9:34 AM
To: alltalk-avp@...
Subject: [alltalk-avp] Bugs
Glen,
Just a couple of bugs that I have come across recently (?ver 1.1.95)-
1 - Stack overflow error, when alltalk set to close after fetching.
2 - Alltalk doesn't cope with being unable to write to destination
directory (ie directory exists but current user does not have write
priviledges)
3 - When migrating multiple equery accounts to a new install of alltalk
the profile editor does not load the profiles properly, in the first
instance.
4 - Seem to be having a problem with mac installs corrupting their
keys, two in the last few days.
Rodney
Offline 
Send Email