At 15:23 Uhr +0900 16.6.2007, Izumi Tsutsui wrote:
>> Can you try the equivalent of a 'for ff in `ls *.tgz`; do gzip --test $ff;
>> done' in a snapshot's binary/sets directory? I see crc errors on every
>> second or third set, but never on the first one.
>
>I get *.tgz sets from daily-build and try the above checks (~10 times),
>but I see no errors.

Sigh...

To summarize a day of experimenting, and swapping components: The 40 MHz
clock was too much for the 68040/33 cpu. Going back from a 20 MHz
oscillator to an 18 MHz one "fixed" the problem.

Obviously no amount of overclocking can catch up time wasted that way.

Sorry for the fuzz,

	hauke


--
"It's never straight up and down"     (DEVO)