It depends on what you mean by a conflict. Most of us use a debugger, a
performance profiler (kernrate is free from Microsoft in the WDK). A lot
of us use a code coverage tools, personally I use one from Bullseye
http://www.bullseye.com
There are hardware debuggers such as the Arium but they are expensive, and
mainly needed for debugging BIOS or other times that the debugger does not
have a chance to start yet.
--
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website:
http://www.windrvr.com
Blog:
http://msmvps.com/blogs/WinDrvr
"JJ" <> wrote in message
news:f38bbc2b-6434-4c70-9ea6-...
> Hi
>
> I would like to know what software or hardware is commonly used for
> troubleshooting software conflicts (besides a debugger that is).
>
> Are there hardware that can be used for this (I thought I once saw an
> ad somewhere for some hardware kit) and if so could anyone give
> recommendations for a specific brand?
>
> Also if you know of a good book or website that deals with the subject
> of software conflict troubleshooting, I would appreciate hearing about
> that.
>
> Thanks in advance,
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 4661 (20091204) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
__________ Information from ESET NOD32 Antivirus, version of virus signature database 4661 (20091204) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com