erikl@milton.u.washington.edu (Erik Larsen) (02/28/91)
Does anyone use System Sleuth to locate hardware conflicts? At work we've had a number of problems with net cards and other cards conflicting with one another in terms of interrupts and memory mapped locations. Can something like System Sleuth locate cards in memory and give a *real* memory map above a000:0000 (a lot of programs don't find some cards in upper memory)? And what about locating shadow ram or rom that doesn't have all address lines decoded so it "reflects" around upper memory? We've also had problems with hard disks. They seem to be interrupt conflicts. Will System Sleuth point out such problems? Erik Larsen erikl@u.washington.edu
edm@hpfcmdd.hp.com (Ed Moore) (03/02/91)
I have System Sleuth. I wish I understood more of the things it tells me about a system. It paid for itself in one exercise. A system with a VGA card and a 1280x1024 TIGA video card would not run any software using a TIGA driver. The diagnostic program for the TIGA card thought everything was correct. System Sleuth showed that the base address chosen for the TIGA card conflicted with the VGA card.