Hi Todd,
> I am struggling to get the Netconnect octopus thing going. I never have
> gotten this stable. I regret if I am repeating a problem that this
> informative list has already solved, and I have missed the solution.
> 1. On running Voyager 3.32 my system either crashes immediately or becomes
> unstable after opening a few voyager windows.
> 2. Voyager is unable to find my V3 key
I guess you mean Voyager 3.2, not 3.32? :) If so, ISTR that this
could be a bit iffy in low stack situations. Some of us found that
increasing the stack figure in the V icon to around 100K would help. I
also recall a lot of talk at one point about *totally* clearing out
the cache - give the new V a completely clean, empty cache dir to work
on. Several people have had problems trying to run different versions
over the same cache.
Alternatively, you could try the newer Beta releases, V3.2.4� being a
stopgap update but some people saw problems with the history list, or
the V3.2.12� which seems ok except being a bit wobbly with some
javascript. Sorry, but neither of those will work until you get the
keyfile thing sorted. :-/
Since you're approaching this from a whole Netconnect package point of
view, you may also want to ask the less Voyager-specific questions on
the NC list as more people are likely to be able to help.
Cheers,
Ian
===
--
http://www.greew.freeserve.co.uk/
--
_____________________________________________________________________
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
