On Sun, 11 Mar 2001 23:53:02, [EMAIL PROTECTED] wrote:
> On 11 Mar 01 at 18:09, owner-arachne-digest@arachne wrote:
>> Date: Sat, 10 Mar 2001 18:43:45 -0500
>> From: Clarence Verge <[EMAIL PROTECTED]>
>> Subject: Re: All spiders bite
>> I was impressed
On 11 Mar 01 at 18:09, owner-arachne-digest@arachne wrote:
>Date: Sat, 10 Mar 2001 18:43:45 -0500
>From: Clarence Verge <[EMAIL PROTECTED]>
>Subject: Re: All spiders bite
>I was impressed by what appeared to be a general localization of the damage
>I had. Core.exe was not
Howard Schwartz wrote:
>
> > If you ever needed a little push to get you to install Arachne on a
> > ramdisk, here it comes:
>
> Later you say that putting arachne on a separate partition will not
> necessarily save files on other partitions. Why will a ramdisk be safer?
> Logically, a ramdisk i
A RAMdisk is not a partition of any HDD, therefore write to a RAMdisk
could not 'slip over the line' to another partition.
Partitions are nothing more than electronic "book marks" on the physical
platter of the HDD, for well behaved programs to use in reading/writing
files on/from the HDD. Shoul
> If you ever needed a little push to get you to install Arachne on a ramdisk,
> here it comes:
Later you say that putting arachne on a separate partition will not necessarily
save files on other partitions. Why will a ramdisk be safer? Logically,
a ramdisk is treated as another partition, i.e.
Hi All;
This is so weird you might think I'm making it up, but I've got proof -
I told Glenn of my intentions BEFORE this happened.
If you ever needed a little push to get you to install Arachne on a ramdisk,
here it comes:
I had decided I might have time to upgrade my Arachne from super-stable
