This has been the main reason I have never purchased Voyager, as this has
persistently happened with every version of V that I've demo'ed. One
additional interesting facet: If you simply fire up V without firing up
Miami, this doesn't happen (ie you are browsing local web pages or web pages
on an AF CD, for example). I've found that in those cases, exiting V works
fine and ARTM doesn't show stuff still running. It's something to do with the
TCP stack + Voyager that is the problem. But I doubt it's Miami, as otherwise
this would happen with AWeb and IBrowse and I don't see that behavior with
those two (Voyager has such a nicer GUI and feel to it, that's why I'm kind of
holding out for it if this problem can be fixed).
I hope that's helpful!
Kevin Orme
amiga university
http://www.amigau.com
[EMAIL PROTECTED]
_____________________________________________________________________
Voyager Mailing List - http://v3.vapor.com/
Voyager FAQ....: http://faq.vapor.com/voyager/
Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP
Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
