Hello!
I am running TB (3.99.29) unattended on a laptop running Windows
XP SP2 (periodically patched thru Windows Update). In a normal
scenario, TB might run for several hours (sometimes even for days)
with no attention from a human. The days-in-between apparently are
during weekends etc. where a family might travel somewhere... :)
Anyway...
Lately - the last few months - I have come to realize that TB is
sometimes heving trouble logging on to an outgoing mail server on
the same laptop. The server has been running quite flawlessly for
a very long time with no updates that might induce malfunction due
to a introduced bug. In fact, it is TB that has been updated. Yes,
it is true that my version 3.99.29 isn't the very latest one. I
have not taken the time to debug (whatever I can debug) the reason
why TB hangs on connecting to the mail server. Hopefully, I will
be able to find something. As for the meantime...
I want to ask whether there is a possibility to add a Time Out
protection to TB, interupting the *outgoing* connection? Currently,
TB just hangs waiting for attention from a human. Using the /EXIT
and /SMARTEXIT macroes won't help. Manually closing TB and then
restarting it fixes the problem - the mail is sent as it should.
In addition, it would be helpful with a /FORCEEXIT macro. My idea
for it would be to be able to simply force TB in ANY situation to
abort everything properly and exit (unconditionally exit of TB).
Another macro; /RESTART could do the same and simply restart TB.
(Personally I have created an Agent to look after TB (whether it is
running etc.) so that my system is not falling over and TB is gone
dead and nothing happens. My Agent restarts TB *IF* appropriate for
the situation, but when I can't take down TB (/EXIT) - what good is
it? (Apparently, my Agent has a Reboot solution...but since there
is no external way of knowing whether TB is stuck or not, I will
have to tell my Agent to restart at time intervals (once a day etc.)
and not because of a stuck connection. So another question would
be: Is there a way to peek Windows to find whether TB is stuck. I
know of one hairy way that could have worked: Set TB to display
Connection Centre only when in use, then if the Agent finds no
Window Handle saying the CC is running then one can qualify that
as being No Inbound/Outbound connections running, thus assuming
everything is fine. Problem is, as soon as you have displayed CC
just once, the Windows Handle is kept (active) and there seems to
be no way of knowing whether it is really displaying or not. (I
might be wrong as I haven't investigated thorougly the conditions
of TB versus then Windows Handles once TB has displayed CC.))
--
...listen2reason... - Musaic.Net [EMAIL PROTECTED]
Current version is 4.0.24.0 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html
