🚀 go-pugleaf

In article <1992Dec16.135938.21596@panix.com>, rryan@panix.com (Rob Ryan) writes:
|> In <1992Dec15.114345.8779@titan.inmos.co.uk> jeremy@cheetah.inmos.co.uk
|> (Jeremy Thorp) writes:
|> 
|> >I have NEVER got DebugOutput to work. TRACE (C++), and OutputDebugString
|> >work fine, but not DebugOutput. I am using DbWin.
|> >
|> >Could someone give me an example that is known to work (with configuration)?
|> 
|> The main thing is that you need a line in your .DEF file that says:
|> 
|>   IMPORTS		_DebugOutput=KERNEL._DebugOutput
|> 
|> Also, this is a Windows v3.1 routine, so it won't work if you have
|> Windows 3.0.  I'm not sure why this import is needed.  It is a documented
|> function of the Windows 3.1 API, so you really shouldn't need to do this,
|> but you do.  Also, the docs don't seem to reference to DBF_APPLICATION.
|> Perhaps they simply expect everyone to use TRACE().

I have tried (on previous occasions) the IMPORTS thing, and it enables the program to link ok.

However, I have NEVER got DebugOutput to actually output anything. I am using the DBWin
program provided in the SDK to display messages. OutputDebugString, and TRACE both work,
DebugPut doesn't - ever!

Does anyone know what I am doing wrong?

-- 
Jeremy Thorp, INMOS Ltd, 	|	jeremy@inmos.com
1000 Aztec West, Almondsbury, 	|	jeremy@inmos.co.uk
Bristol, BS12 4SQ, UK.		|	
Tel.  +44 454 616616    Fax. +44 454 617910
The above is the personal opinion of the author,
and does not necessarily reflect INMOS policy.