There is indeed a bug in WinApi.odc.
"WINSPOOL.dll" should be replaced by "WINSPOOL.drv".
OmS sent me a corrected WinApi.odc, which you can find in the attachment.
There is one more little problem which I also reported to OmS but that is not yet 
fixed in the attached WinApi.
There is a function named GetDefaultPrinterA/W, which is not contained in
WinApi. It is, however, fairly easy to define your own interface module
in order to provide access to this function.
May be there are even more of them. It is not possible for me to check this
function by function from the MSDN docu because there are simply too
many functions listed.

- Josef

----- Original Message ----- 
From: Douglas G. Danforth 
To: BLACKBOX@LISTS.OBERON.CH 
Sent: Tuesday, March 23, 2010 9:36 PM
Subject: Re: [BLACKBOX] WinApi and WINSPOOL.dll

Josef,
Interesting that you should ask at this time.
I was just about to investigate what it takes to 
print directly from within a module for a client.
I will be interested in seeing what OmS has to say.
-Doug

Josef Templ wrote: 
Has anybody ever used the WinApi functions specific to
the Windows printing API, i.e. the functions that are supposed to
be provided by the WINSPOOL.dll (e.g. EnumPrinters, OpenPrinter, etc.).

It seems to me that there is no WINSPOOL.dll available under Windows XP.
There is, however, a dll named spoolss.dll, and that one, according to MSDN,
is supposed to provide the Windows printing API functions.

Question to OmS:
Is it possible that the WinApi generator erroneously uses the name WINSPOOL.dll
just because the functions are exported by a Windows header file named winspool.h.

Thanks in advance

- Josef

---- To unsubscribe, send a message with body "SIGNOFF BLACKBOX" to LISTSERV@LISTS.OBERON.CH 
---- To unsubscribe, send a message with body "SIGNOFF BLACKBOX" to LISTSERV@LISTS.OBERON.CH

----
To unsubscribe, send a message with body "SIGNOFF BLACKBOX" to LISTSERV@LISTS.OBERON.CHrn-P