CompuServe Messages

Hello fellow Amigans! I am having some severe problems with my (usually) trusty A2000HD, and the problems seem to be the kind that have probably been there for a while, but have grown considerably worse over a long period. I currently have a GVP 25 MHz '030 board (1 MB RAM) along with 2 A2091's. One 2091 has 2 MB on it, the other 512K. I have three HD's, one being the original 40MB Quantum, a 52 MB Quantum and a 210MB Conner. Currently, the two small Quantums are on one SCSI chain on the GVP, while the Conner is on the 2091 with 2MB. The second 2091 with 512KB is by itself. I have a 2MB Agnus installed using the TMAP board. The mother board is a rev 4.x board (I don't remember exactly which one) while the 2091's are rev 4.3 and 4.4 (I believe) and the 2091 ROMs are a rev4.x and 6.x. I have the 2.05 system ROM and the 2.1 OS. My problem is this: prior to installing the GVP board, I was getting some strange system crashes with guru numbers 0f 81xx xxxx and always in the task address range of 002xxxxx. It progressed to the point where on rebooting, the machine came up with the dreaded blood-red board diagnostics screen showing me that the memory portion of the 2091 with the 2MB was bad (of course, I no longer had that 2MB available after that). Subsequent reboots without powering down would always result in that message. Powering down would "reset" the machine, apparently, and the board would be available again. Again, this was prior to installation of the GVP board. Now, with the GVP board installed, the same guru's occur, but now they may also appear in the 01xxxxxx address range, but I have yet to have them result in the board diagnostics screen on restart. What has happened, at least once, is that it apparently loses track of the boot drive, because it suddenly popped up a black screen with the animated disk insertion into the disk drive routine. The machine will now "hard-lock" – even no mouse response – if very much memory is used, i.e. unpacking the AmigaUser.CAT file to RAM (although I can unpack it to disk just fine). Another example is trying to pull up the catalog in AutoPilot – AP works fine until I try to pull up the download catalog ( which is ~760KB) at which time everything just stops. Another example – VLT works fine, including ZModem downloads, but Term crashes miserably, especially if I try to do a ZModem download (it uses an external xpr library that must be loaded in is my guess). I'm sorry if this is a little long-winded, but this problem has got to stop! My question: is it possible that the power supply is weak, and as more memory and disk drive usage occurs, it is not capable of maintaining voltage on the bus? Or, is this possibly a problem with the motherboard revision? Does anybody have any similar experiences, or engineering insight as to what the problem is and how it can be corrected? Thanking all in advance (especially for the patience to read this <g>), Duane.