Hello Gavin Kinsey ([EMAIL PROTECTED]),
You wrote about "[netconnect] Re: Voyager crashes cure?",
on Tue, 29 Jun 1999 21:30:49 +0100.
Well I don't have V crash here and neither do I run out of memory
(2Mb chipram 63Mb Fastram and a 4Mb Gfx card) but occationally it
still go's nuts anyway forcing me to shut it down and then go offline
and do a reset.
Even when I have shut down Voyager the system is still very busy
handling whatever routine in Voyager tripped up in the first place.
And when I mean busy I really mean busy the whole computer runs like
a slug, with a jumpy mouse pointer and the works (And this is on a
60Mhz 060). You really have to arm wrestle the mouse pointer just to
safely close down any progrmas that are running.
I have even tried to generate a log file from CyberGuard (Enforcer
clone for the -060 cpu) to send in a bug report. However this amount
of hits generated is endless becuase the task that has tripped up is
still running and cannot be shut down. When I had this logfile being
directed to a harddrive partition the computer became 100%
busy and eventually crashed and as a result I lost the logfile.
However within the minute the computer ran like this the logfile was
already 1.5MB in size!!!
There are definatly bugs in the current 2.96.7 Netconnect release of
Voyager. If these are already fixed in curent pre V3 internal beta's
then perhaps this should be released if it has no additional problems.
I mention this because if I remeber correctly the author posted here a
while ago mentioning that this problem had been fixed in what was then
the latest beta.
--
Jason Watson.
====================================================
Towerised A4K, WB3.1, CS-PPC 060-60 604-200 2+64MB,
CV-643D 4MB (CGfx4.1), 2.1GB IDE (PFS2), Atapi ZIP,
6x2x2 CD-RW (IDEFix97 3.4). Dynalink 33.6 Modem (NC v 2.3)
====================================================
_____________________________________________________________
NetConnect mailing list. To unsubscribe, send an 'unsubcribe'
message to <[EMAIL PROTECTED]>
