- For individual users
- Instant access to solutions
- Ask your tech questions
- Start your 30-day Free Trial
Main Topics
Browse All TopicsI considered Softice, But i have trouble with it, the first one is softice debugger is very 'sticky', for example, when you run the menu, the computer is waiting for I/O, softice can't proceed, you have to press Ctrl-D and response to the debuggee when you are done and back to softice, it really execute a lot of other statements and don't know where it has gone to... But more important, is how to debug NE Executable. Thanks
Jack
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: atheistPosted on 2004-03-07 at 12:33:34ID: 10536249
The Microsoft Debugger is free. hdc/ddk/de bugging/in stallx86.m spx
icrosoft.c om/downloa d/symbols
http://www.microsoft.com/w
Create a Debug directory and set you're symbol path to
SRV*C:\DEBUG*http://msdl.m
I am not a developer so can not provide a debugging walkthrough, but you can normally figure what's going on by the function calls. I use it to open minidumps and memory dumps where the online help tells me how to interpret the bugcheck, and LM lists the modules as the memory address can be more informitave. Has lots of other uses.