🚀 go-pugleaf

In article <bouldin-2709952120380001@charles.intr.net>,
bouldin@enh.nist.gov (Charles Bouldin) wrote:

>It happened to me again. Major b tree corruption, ultimately Speed Copy
>won't work as it thinks there are more or few items in the trash than are
>really there. That is how I've first noticed the problem each time.

<snip>

>This is very worrisome. I strongly suspect that this has something to do
>with Speed Copy, but I cannot prove it. I'm simply going to keep using all
>3 components of SD and look for further problems. The next time I detect
>it, I will throw out Speed Copy and see if the problems go away.
>
>It is not a great loss, as Speed Copy is the least important part of the
>package to me, but I do think there is a bug here that needs to be fixed.

I experienced b-tree errors on my PM7100 just a few hours after updating
to 1.0.2 and reverted to 1.0.1 for all *but* Speed Copy. I have Speed Copy
1.0.2 running happily alongside its younger brothers/sisters and have had
no more HD problems.

I contacted Connectix straight away, expecting the prompt response that
I've viewed here... nothing. I was very supportive, not the least
disgruntled. I included a comprehensive Norton's HD report and a
description of the circumstances of the trouble, nothing...

What gives Connectix? (You'll noticed that this missive is also headed
their way)

--

Culture is what we condone.

Marc Nothrop
University of Tasmania, Australia
mnothrop@postoffice.newnham.utas.edu.au

-- 
Culture is what we condone.