Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!dimacs.rutgers.edu!seismo!uunet!snorkelwacker.mit.edu!mit-eddie!uw-beaver!milton!erikl
From: erikl@milton.u.washington.edu (Erik Larsen)
Newsgroups: comp.sys.ibm.pc.misc
Subject: System Sleuth and hardware conflicts
Message-ID: <17262@milton.u.washington.edu>
Date: 27 Feb 91 18:15:31 GMT
Distribution: usa
Organization: University of Washington, Seattle
Lines: 16

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