On Sat, 17 Mar 2001 23:56:24 -0400, Clarence Verge wrote:
<snip>
>> May I please go back to RAMD caching on my 1.70r3 ??
> Sure thing, L.D., just keep us appraised of any change in the lost
> cluster count on your A1.66 install. Thanks very much, and I think
> it might have been a worthwhile experiment.
> I hope I'm not jumping the gun here, but doesn't it look like it might
> have been a combination of Insight 3.51 and your other stuff that made
> the lost cluster problem ?
I don't think that InSight 3.51 was the *sole* problem. The lost
clusters go back to *before* that version, remember?
In addition, with previous versions it seemed to point to InSight and
SMTP.LOG because contaminated files & lost clusters actually had
portions of that log written into them.
But also back there in herstory were the facts that I, and others, found
the contamination & clusters seemed to hold portions of ARACHNE.PCK ...
something which InSight doesn't screw with, right?
Things are better apparently, whether through intent or not. [Larger
programs require tighter code to keep size manageable??? :> ]
I'm leaving the newer InSight version in 1.66 ... unless/until I see a
reason to move backwards with that install.
And I'm going back to cache on RAMDrive for 1.70r3 because I've had some
lockups that I think are caused by cache constipation ... problems I
hadn't had when cache wasn't on HDD.
l.d.
-- Arachne V1.70;rev.3, NON-COMMERCIAL copy, http://arachne.cz/
