The Register posts an Amiga hardware mystery

[NinjaCyborg]

Not ten years ago, not 30 years ago, but yesterday:

https://www.theregister.co.uk/2020/04/10/on_call/

[NorthWay]

I read it, but there is nothing there that you can hang onto. You'd have to break out all the debug tools to see if something was off. Possibly some kind of memory corruption that was affected or brought on by the clock.

[Matt_H]

Lots of variables we’d need to track down: the particular SCSI controller, chip revisions, driver versions, which CPU card (the dreaded rev 3.0 3640?), FFS version, other expansions, mask and max transfer values in the RDB, hacks running in user-startup or WBStartup, etc.

Personally, I’m betting on it being a wonky Expansion Systems DataFlyer controller. Had one of those in my 1200–nothing but unexplainable trouble!