HRMMM? In that case, I wonder if RFI from the unshielded CRT/Monster duo might be causing the problem? Try making an RFI shield for the Monster or using it externally again.
Magnetic interference from the CRT could be the problem as well. The electronics on the monster could be a LOT more sensitive to electromagnetic interference than the usual inhabitants of the SE/30 expansion slot stack. The processor on board the monster is likely operating at a clock rate something like a couple orders of magnitude faster than any SE/30 PDS Cards packed into that bucket.
< scratched head and decides to warm up his first cup of coffee >
Dunno, top-o-the mornin' WAG posted above . . . xx(
< returns w/coffee >
Could the RFI from the monster we whackin' your SE/30's Processor? :?:
OOPSIE!!!!!! That's what I get for posting while I'm still asleep. :I It's not an SE/30, but the plastic chassis of the 840AV is probably just about as electromagnetically opaque as the air in a Compact Mac Bucket. So CPU and I/O subsystem whackage may still be the culprit.
Magnetic interference from the CRT could be the problem as well. The electronics on the monster could be a LOT more sensitive to electromagnetic interference than the usual inhabitants of the SE/30 expansion slot stack. The processor on board the monster is likely operating at a clock rate something like a couple orders of magnitude faster than any SE/30 PDS Cards packed into that bucket.
< scratched head and decides to warm up his first cup of coffee >
Dunno, top-o-the mornin' WAG posted above . . . xx(
< returns w/coffee >
Could the RFI from the monster we whackin' your SE/30's Processor? :?:
OOPSIE!!!!!! That's what I get for posting while I'm still asleep. :I It's not an SE/30, but the plastic chassis of the 840AV is probably just about as electromagnetically opaque as the air in a Compact Mac Bucket. So CPU and I/O subsystem whackage may still be the culprit.