what I do is: use voyager and Miami together to browse the web; exit voyager through the GUI; make Miami offline; try to 'quit' Miami; at that point, it usually says that several V tasks are refusing to allow Miami to quit, so; I open ARTM and sure enough, they are there, so; I kill them off with ARTM and exit it; but then I still can't exit Miami and I have to reboot to clear everything out. Could it be related to having your cache in RAM? I don't like to clutter up my hard drive and the Amiga has a convenient RAM drive useful for this purpose, unlike WinBlows. I know that's not the common practice, though. Kevin ---------- From: Marcus Klemm Sent: Monday, January 31, 2000 3:42 PM To: [EMAIL PROTECTED] Subject: [voyager] Re: still can't 'quit' Voyager successfully Hello Kevin > > Is there any magic to this? Or am I just stupid (you don't have to answer > that - :) I can't get V3 to 'quit' completely when I say 'quit'. It still > leaves a bunch of 'DNS Server' stuff and the Arexx engine, and V itself > running despite going to File/Quit in the GUI. > > Any other thoughts? I really *want* to use Voyager, but if I have to > reboot every time I use it, the magic ends. I think these tasks exist only a few seconds after you quit Voyager. You can see it using a system monitor like scout. Start Voyager, start scout, In the Tasks section of scout the various "V" tasks should be listed. Now quit Voyager, wait, let's say 3 to 5 seconds, hit Update in Scout and the tasks should be gone... Going offline and Closing (not hiding) Miami works for me. Ciau -- Marcus -- Binary/unsupported file stripped by Listar -- -- Type: application/ms-tnef
