home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!pipex!warwick!uknet!dcl-cs!alan
- From: alan@comp.lancs.ac.uk (Alan Phillips)
- Newsgroups: comp.os.ms-windows.programmer.tools
- Subject: Re: MSC 7.0 windows debug mode and 'Cant read from device AUX'
- Message-ID: <1992Dec17.100939.5506@comp.lancs.ac.uk>
- Date: 17 Dec 92 10:09:39 GMT
- References: <RHARMON.92Dec10144328@triton.uucp> <70560005@hpcc01.corp.hp.com>
- Organization: Department of Computing at Lancaster University, UK.
- Lines: 18
-
- In article <70560005@hpcc01.corp.hp.com> azarian@hpcc01.corp.hp.com (Randy Azarian) writes:
- >I do not agree that DBWIN is not useful in the standard kernel. It is very
- >useful to do OutputDebugStrings in my code as I am debugging. Additionally,
- >I have noticed that DBWIN does display quite a few "warning" messages in the
- >standard kernel, albeit probaby insignificant, although I think it will report
- >unfreed memory handles, and the like.
-
- You might like to look at my TextView DLL, which is somewhere on
- ftp.cica.indiana.edu. It basically manages a scrolling output window
- for you, and you can write text with various options like timestamping
- to it with a single API call. Other APIs allow you to clear it, etc, etc.
-
- I wrote it originally as a real-time trace system for debugging, and there's
- a sample app in the ZIP file that demonstrates it. I use it hugely for
- buiding my PFE editor, and the ability to have a set of trace messages that
- I can scroll back and examine at leisure is _very_ useful.
-
- Alan
-