Everything works perfectly, apart from the occasional lockup which leaves usually a number of
applications dead, so that they cannot be quit for example. While usually not all programs fail,
Workbench always does. This phenomenon can happen even twice a day, or it may not happen for a week
(during which time the CPU is mostly doing calculations).
I tried several "drop" tactics, not using a certain patch/app for a while, and the same happened in
no diminished way. Also this testing is very time consuming, because I cannot even produce it, I just
have to wait and see every time.
This is posted in hardware, because while the problem may be of a software
nature, I am currently suspecting that the SCSI bus locks up. That
would in my opinion be capable of these effects, and explains why WB has most problems as it wants to
keep up with the volume/drive status. So people with similar hardware, or who had similar problems,
would you have a word of advice? Details at the end.
Perhaps it is a clash between drivers of hardware. Or there exists a piece of software (hack) that can reset
this SCSI bus without reboot? That could then, not solve the problem, but halve its negative effects.
My setup:
Hardware A1200, Blizzard 1260 accelerator, Mediator A1200 PCI (Voodoo3 and nic),
Seagate Barracuda ST39173N SCSI drive, IBM IDE drive, old Philips CD-RW, some IDE doubler
Software OS 3.5, 1230scsi.device v8.5 (on chip), Blizkick 1.24, MCP 1.33 (tested w MCP off, didn't help), recent dnetc