Constant Checksum errors

This is driving me batty.

Okiez, I recently received a nice Apollo 1260 running at 80mhz (thanks Stan) with 32mb ram.

I purchased a nice clean A1200 just for it. It is an ID4 revision system.

Anywho, no matter what hard drive I install, it works for a while and then I get Checksum error on Block etc etc at boot up.

I have tried Seagate ST1 microdrives, Compact flash disks etc - all the same.

The A1200 has a nice modified ATX Psu, so lack of power cannot be the prob.

I am using SFS with the default Mask and a max transfer of 0x1FFFE (which apparently is very safe).

I am running the stock standard version of AmigaSys4 (with the Apollo 1260 options selected).

Any idea why this ******* keeps giving me checksum errors?

Hi,

Have you tried with FFS filesystem?
I'm using FFS only.

Not yet - I HATE FFS. FFS is usually where you DO get checksum errors!

---------- Post added at 18:15 ---------- Previous post was at 18:15 ----------

Hey Stan, what mask and max transfer settings do you usually use?

To be honest I never touched original settings; just standard settings that FFS gives in HDToolBox

By the way:
are you using KS3.1 or 3.0?

I think I have found the problem.

I replaced the 80 mhz crystal with a 66mhz crystal..... now no problems.

Obviously this Apollo card cannot run at 80 mhz reliably. I wonder how it would run at say 76?

Maybe you need the timing fixes on your A1200? These Apollo's can be a bit troublesome with some A1200 Mobo's.

I'm sure Stachu would have fully tested the card at 80mhz before sending it.

Steve.

Quote:

---

Originally Posted by abraXXious

I think I have found the problem.

I replaced the 80 mhz crystal with a 66mhz crystal..... now no problems.

Obviously this Apollo card cannot run at 80 mhz reliably. I wonder how it would run at say 76?

---

There are about 20 Apollo cards upgraded by me that are working @80Mhz without any problems.
So it's not obvious.

On top of that I've tested this particular card for about one hour by watching demos, copying files moving icons and os on.

So I don't think 80MHz is an issue.
I would suggest:
1) timing fix for your mobo
2) format your HDD under real Amiga with KS3.1 by FFS filesystem
This should help.

Tried FFS on an A1200 with 3.1 - no difference....

...I thought without the timing fix the Apollo would either not work at all or run very unstable?

Thing is, at 66 mhz it seems rock solid, so I dont see how the timing fix will make a difference.

I dont believe the timing fix makes a card more compatible to overclocking. My understanding is that it simply allows the card to work reliably on some troublesome A1200s.

---------- Post added at 20:56 ---------- Previous post was at 20:53 ----------

Out of interest, it started becoming unstable and corrupting the hd after about 90 minutes of running, so perhaps some components slowly heat up over time.

When I overclocked my Cyberstorm Mk III I thought it was running perfectly, but after 2-3 hours it would start to become flaky, then you had to shut it down for half and hour and it would be fine again. Once I clocked it back to 66 mhz (from 72) it ran perfectly, and has since.

Quote:

---

Originally Posted by abraXXious

I dont believe the timing fix makes a card more compatible to overclocking.

---

You will never be sure until you will do that. ;)

---------- Post added at 13:29 ---------- Previous post was at 13:26 ----------

Quote:

---

Originally Posted by abraXXious

Out of interest, it started becoming unstable and corrupting the hd after about 90 minutes of running, so perhaps some components slowly heat up over time.

---

It can be also electrolytic capacitors.
What you can try to do is to put the +5V form PSU socket to FDD connector to ensure good +5V for whole system.
It is not a lot of work but worth to try.

1D4 board still has to have the timing fix done to be 100% stable with an Apollo @ 80Mhz. I know 'cos I've owned one such set up. ;)

Kin