Re: alt x oddity
- From: Frank da Cruz <fdc@xxxxxxxxxxxx>
- Date: 5 May 2006 14:48:09 GMT
On 2006-05-05, Scott Caissie <scottac@xxxxxxxxxxxxxxx> wrote:
: is there a great amount of technical detail as to what the fix actually
: does? The bug and the fix is so vague.
:
Kermit 95 runs in multiple threads that have to be synchronized. The command
screen and the terminal screen are just two examples. Executing commands
while in the terminal screen's context is rather tricky business and that's
where the bug is.
: I did discover another problem with those macros. Its a very percular one
: involving IF and ELSE statements.
: If I have a macro with a number of IF statements (using bracketed off
: commands) and use that macro about a hundred times or so (very realistic),
: theres a chance of an error occuring.
: Error #1 pop up box saying it encountered a problem and needs to close.
: Error #2 looking at the COMMAND window with a flashing cursor. Effectively
: frozen. Can't break out of it. Must close the program.
:
I suspect this is an artifact of the same bug. If you invoke the same macro
from the command context the same number of times, I suspect it you won't
see a problem. Again, see our support page:
http://www.columbia.edu/kermit/support.html
A version of K95 is available that fixes the bug, but it's not free due to
the circumstances explained on the support page. I continue to work to make
the needed arrangements to release a new version with this fix and many others
and quite a few new features as well. But it will likely not be free either.
- Frank
.
- References:
- alt x oddity
- From: Scott Caissie
- Re: alt x oddity
- From: Frank da Cruz
- Re: alt x oddity
- From: Scott Caissie
- alt x oddity
- Prev by Date: Re: alt x oddity
- Next by Date: Re: using FILE OPEN quadruples memory usage!
- Previous by thread: Re: alt x oddity
- Next by thread: using FILE OPEN quadruples memory usage!
- Index(es):
Relevant Pages
|
