I have been doing certain experiments with chkdsk, chkdsk /f and
Arachne's clr.bat script - this is latest version, BTW:

Now I am sure, that simple running of CORE.EXE and visiting pages
doesn't cause lost clusters, and neither deleting and then re-creating
open (running) $roura$.bat in TEMP directory by latest clr.bat (F8)
does not cause any lost clusters. I am going to release 1.66 as it
is, ie. almost identical to 1.65, just with new clr.bat (see above).

--cut--
@echo off
rem usage: clrcache.bat (cache.idx) (cache path) (TEMP path) (filemask)
rem cache path or TEMP path MUST NOT be the same as Arachne installation dir.!
if exist %1 del %1
if exist %3$roura$.BAT copy %3$roura$.BAT bat.tmp>NUL
for %%f in (%2*.*) do del %%f
for %%f in (%2headers\*.*) do del %%f
for %%f in (%3*.*) do del %%%f
if exist bat.tmp copy bat.tmp %3$roura$.BAT>NUL
if exist bat.tmp del bat.tmp
--cut--

I suggest Clarence to get used to pressing F8 from some offline page
for now, because modifying clearcache.dgi to output some message would
require changes in CORE.EXE, which is currently code-freezed (well,
maybe I will restore existing right edge after </PRE> - this should
make Yahoo! page look slightly better. I hate what they have done
with the <NOBR> section in the top of the page ... they are no longer
640x480 compatible, which is bad news for future browsers running
in cell-phones :-( They will have to use super-minimized fonts, and
scale down all values in pixels and all image sizes by number of two :-(

--
Michael Polak: [EMAIL PROTECTED]
Arachne Labs: http://arachne.cz/
My mobile phone - up to 160 characters: [EMAIL PROTECTED]

Reply via email to