L.D. Best wrote:
>
> The problem has been that Arachne somehow just doesn't handle things
> well, and "lost chains" linked to Arachne -- or at least crashes of
> Arachne -- have been around for a *very* long time.
>
> P.S. There have been no crashes since the flawed install yesterday.
Well, that may have been it. When I saw your post, I put it together with
my experience of a lost cluster on my ramdisk after my shaky install and
decided I better take her out for a ride.
I rode her hard and I rode her often. I pounded the cr*p into/outof A164 for
two hours on my P90 running DOS 6.22 and nary a single lost cluster.
I even forced three or four lockups by switching from VGA to EGA while online
(Arachne doesn't like to do it online - maybe a problem with EPPPD) and she
didn't hurt me.
And I'm just back from a 20 minute workout with A164 on my '486 running
DOS 3.3. Believe me, 20 mins at 33Mhz seems like an hour. <G>
Anyway, there were no lost clusters even after 4 Illegal xSwap offset reports
and my forced video mode change online. I killed the cache at least 6 times
and let it fill up to about a meg once. That's much more than I usually have
in cache, so that could point to a difference.
Do you experience lost clusters with a near empty cache, or do you collect
stuff forever ? Maybe it's an Arachne function I never get to see.
- Clarence Verge
--
- Help stamp out FATWARE. As a start visit: http://home.arachne.cz/
--
--
- Clarence Verge
--
- Help stamp out FATWARE. As a start visit: http://home.arachne.cz/
--
