{#} Replies are directed back to [EMAIL PROTECTED]
{#} To reply to the author, write to Brad Watson <[EMAIL PROTECTED]>
Figured I'd keep with the despair theme which, oddly enough, was my prom
theme too. Go figure.
Anywho, There is a hiccup in the way the ICQ service launches &
auto-launches. Whenever another process or service is taking a minute to
do it's thing, it ends up choking out ICQ, requiring you to manually
launch it when all other, more demanding, processes have finished.
Could this be a timing issue or rather a time-out issue with the
Icy Juice code? All other services are very respectful when delegating
auto-launches. As such, this bug might've flown under the radar as,
again, most services don't hang for very long when auto-launching.
An easy way to reproduce this anomaly is to set your IRC service to
auto-connect to irc.slashdot.org , as it takes a minute or two for fire
to connect to it, while also auto-launching fire's other five services.
Thank you very much
Brad Watson
{#} ----------------------------------------------------+[ fire ]+---
