Hi Tommy,
On Thu, Jul 20, 2000, at 12:39 AM, you wrote:
>
> Hello Todd
>
> On 19-Jul-00, you wrote:
>
> [snip]
> >
> > I had version 2.xy working fine way back when
> >
> > I am registered user for version 3.0.
> >
> > Problems:
> > 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
>
> [snip]
>
> I'm haveing /very/ similar problems. After registering V3 I still get
> the "You Are Using the Demo..." requester when V3 loads. SnoopDos says
> it found the keys, but I still get asked to register. I don't know if
> it "silently quits after 30 minutes" because it crashes the system
> loading my homepage. After a reboot, my Work: volume (where V3is) is
> unvalidated. QuarterBack Tools shows an error in Voyager's cache.
>
---- snip ----
> Regards
> Tommy
>
> --
Boy, are you covering a lot of ground. Now, I am NOT a V expert,
but, after reading a number of queries, with their responses, and after
having some of my own difficulties with V, it appears you may be having
problems from at least one of several areas.
First, your .key file is supposed to be placed in your "S" directory.
V looks for it there (You can have a copy of it in any other directory,
but, the "S" directory is the important place.). Two, V 3.2 is known to
crash when trying to work with a Web site that is sending a lot of
javascript commands and graphics files (jpeg and gif); these seem to
overwhelm V, causing it to crash and often taking your drive, with the
Cache, with it. Now let us separate these two situations.
The V...key: find it and copy it to your "S" directory. If you
still have it in coded form, then have it go through a mail-client (YAM,
AEMail, AirMail) which will decode it. Then place it in the "S" direc-
tory! This should solve the fact that V cannot now find the .key file.
V crashes, taking a harddrive with it and causing validation errors:
As stated in a past thread, V 3.2 seems to have a bug which causes it to
disrupt the I/O process of the disk drive which has the Cache directory,
used by V. This seems to be a constant thing. The solution: Have a
backup of everything on that drive; switch to the PFS v 3 filesystem,
instead of FFS; and, first let your Amiga go through the process of
trying to validate, by itself, without your stopping it or doing any-
thing. (I, twice, found that, when I did not do anything, the drive
finally validated and I did not have to reformat the drive or anything.)
Finally, until the stable, new version of V is available, do not use
V. I apologize to the authors of V, for saying this last thing, but, I
think it is the smartest thing to do, for now. I look forward to that
new version, since, I, too, want to start using V, again.
I hope this helps you, Tommy.
Julian.
--------------------------------------------------------
"When you need to manage your time, manage your workers, organize the
workflow, determine how to store what you need, or to properly use a com-
puter (whether for programming, using programs and packages on it, or
training people on it), and have everything work the right way the first
time, contact me."
--------------------------------------------------------
Author of "MSH Tutorial V. 3.0". Found on Aminet -- MSHTut30.lha
Julian Aronowitz. Tel.: (718) 654-1681; E-Mail: [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
