CompuServe Messages

The problems are solvable and actually, I have written several programs to get around the problem, including a replacement handler. But these are part of stuff that I am not really at liberty to discuss or release right now. The truth is that software which causes a bus error exception on the A3K is broken even though it may work fine on an A2000. The example I quoted, SysInfo, even claims to have used enforcer in development. Until a couple of months ago, enforcer only was aware of 24 bit address space and apparently accesses outside of that area weren't always detected. The most recent version fixes that. It is important for developers to be aware of what the most recent versions of these tools are and update asap. When the A3K first came out, I was against it because there were too many changes to be software compatible. I think most of the kinks are out and having the chance for a cheap 040 card, I bit the bullet and went for the A3K. I'm happy I did. -Greg As far as A3000 SCSI, I have no problems with it. I have a recent motherboard and 2.04, which seems to be OK to me. I have two hard drives, a CD-ROM, and a SCSI scanner on it and it works just fine. While the hardware uses some of the same components as the 2091, it is considerably different as it can DMA to any address, and can move data 32 bits at a time, making it potentially faster. – via Whap!