In Windows programming you typically attach an external debugger to your
service to see whats going on. Such an external debugger is beside debugging
your service also able to catch trace message sent by the debugged
application.
The debugged application can send these trace messages using the
OutputDebugString() API (from Kernel32.dll). 

These simple outputs on the native Windows NT debug stream are also usefull
for tracing and debugging Smalltalk/Squeak application startup 
or Smalltalk headless applications, especially when you implement a 
service.

The trace messages can be viewed either with an external debugger or 
the system debugger attached to the Squeak virtual machine process. (a very
small and handy tool to use is the debug monitor dbmon.exe (9kB) from the
Microsoft Windows Platform SDK).

You could download and install the free Platform SDK for your platform
from the MSDN website and use the attached squeak code to do be able to
write on the NT debug stream. 

Have fun,
Torsten

Note: use it with care since it only works on Windows and it should 
      also be used in debug builds of your applications.

-----Original Message-----
From: Bill Schwab
To: squeak-dev at lists.squeakfoundation.org
Sent: 17.02.03 15:46
Subject: Networking from NT service

Hello all,

Various FAQs describe how to run a Swiki as an NT service.  I haven't
actually tried a Swiki yet, but I have a TCP server that seems to work
fine until I run it as a service.  Any ideas on what might be wrong
and/or how to debug it?

Bill


Wilhelm K. Schwab, Ph.D.
University of Florida
Department of Anesthesiology
PO Box 100254
Gainesville, FL 32610-0254

Email: bills at anest4.anest.ufl.edu
Tel: (352) 846-1285
FAX: (352) 392-7029



-------------- next part --------------
A non-text attachment was scrubbed...
Name: DebugWinNT.2.cs
Type: application/octet-stream
Size: 2223 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20030217/832f1318/DebugWinNT.2.obj