Hello Chris Wiles ([EMAIL PROTECTED]),
You wrote about "Re: [netconnect] Just wondering what is happening with the new
Netconnect then.",
on Sun, 13 Jun 1999 17:52:55 +0100.
> Yes, but these aren't the fault of the programs!
>
> ie. if you have a hack/patch that causes some kind of illegal memory address
> in V, you must remove the hack, we can't work around this in Voyager, this
> is not legal.
Chris you didn't read what I typed, it still suffers from the same
problems in a clean setup.
I still have a secound WB partition I can boot from with WB 3.1 and
only the drivers and utilities to use Netconnect. With no hacks
installed Voyager can go nuts on certain sites and make the system so
busy (Especially if trying to run CyberGuard at the same time ot
generate a log file) that mouse movement becomes choppy and eratitic.
The only time I have come close to shutting down safely when this
occures had generated a log file in excess of 1MB in size. However I
could not preserve this because the Voyager task screwing up the
system keeps going even after closing Voyager down. The system was so
busy that I could'nt quit GyberGuard to close and preserve the log
file.
If I have problems here I use the clean setup to boot from and check.
as for MD-2 on your PPC card try having "CyberGuard" running when you
click on the "send" button after typing a mail. You should if using
th same verison as the rest of use get a hit.
Cheers.
--
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]>
