In response to Clarence's commentary & query:
On Fri, 09 Mar 2001 18:20:02 -0500, Clarence Verge wrote:
> Finally, and this is PURE speculation right now, circumstantial evidence
> points to a possible involvement with Ncache !
> I had just recently (about 1-2 months ago) switched from PC-Cache to Ncache.
> AND, LD is famous for lost clusters, and used Ncache in the past.
First, I continue to use Ncache on all fixed drives.
> How about it, LD ? Any lost clusters recently ?
Second, no lost clusters associated with v1.70r3
thousands of lost clusters, 2.2Mb+, over 400 "recovered" files
with v1.66
I continue to run two versions; I use 1.70 & the kids use 1.66.
A finger was pointed at a problem with SMTP.log some time ago, I double
checked the ACF files [loaded automatically depending upon user choice]
for both of the kids, and although POP3.log is YES, SMTP log is NO. So
it is not due to SMTP logging.
Of the files I checked [I am *not* going to even glance at over 400
files!] 100% of them appeared to start out as GIF files and then
appeared to have cache idx written into the file.
I am *currently* using cache2tmp [on ramdrive] and have installed the
actual cache directory on the RAM drive -- in my 1.70 version.
In the 1.66 version the kids run, cache2tmp is yes [on ramdrive] but the
cache files are kept on the HDD.
Those are the facts AFAICT. Let someone else try to make sense out of
it.
l.d.
P.S. I spent over 2 hours the other day pulling an RTFM on Ncache, to
make certain I was not delaying writes which could, for whatever reason
real or imagined, cause trashed files. I determined I had everything
set up just fine ... the only changes I made were: move Ncache back to
Config.sys [instead of autoexec]; increase size of Ncache because things
were still too slow at times [went to 8Mb]; increase size of block to be
written to 4096 [required due to much larger cache set aside]. FYI, the
same config.sys runs for both versions of Arachne being used; it is only
at the point of the decision tree in autoexec that anything is
different, and that is which ACF is loaded into 1.66 *or* going to 1.70.
-- Arachne V1.70;rev.3, NON-COMMERCIAL copy, http://arachne.cz/
