I am aware that there are a few threads on this topic already,
however, I still have some more questions that I think are unanswered
as I'm having trouble getting this example built and installing it to
explore what it is doing.

From the documentations, from what I understand, I'm supposed to build
genprint.dll using "build" in the build environment. In my case, I
have used the Windows XP x86 Free/Checked Build Environment. However,
no dll gets built, and I'm getting the following message.

C:\WinDDK\6001.18000\src\print\genprint>build
BUILD: Compile and Link for x86
BUILD: Loading c:\winddk\6001.18000\build.dat...
BUILD: Computing Include file dependencies:
BUILD: Start time: Tue May 13 10:43:55 2008
BUILD: Examining c:\winddk\6001.18000\src\print\genprint directory for
files to
compile.
c:\winddk\6001.18000\src\print\genprint - 9 source files (7,549
lines)
BUILD: Saving c:\winddk\6001.18000\build.dat...
BUILD: Compiling c:\winddk\6001.18000\src\print\genprint directory
BUILDMSG: Warning : The sample c:\winddk\6001.18000\src\print\genprint
is not va
lid for the current OS target.
BUILD: Linking for c:\winddk\6001.18000\src\print\genprint directory
BUILD: Finish time: Tue May 13 10:43:56 2008
BUILD: Done

The next step, from what I can understand, is copy genprint.dll into a
Windows systems directory and build a simple program that uses
AddPrintProcessor to install the printer without the inf file, but
I'll ask about that another day.

My question is what exactly is going on with WDK refusing to link.
Thanks.

I think this is easy to understand: BUILDMSG: Warning : The sample
c:\winddk\6001.18000\src\print\genprint is not valid for the current OS
target.

Try building for Vista and not XP.


<sleviantron@gmail.com> wrote in message
news:209619c8-d99b-4d3e-b7cd-339f96d169d1@k10g2000prm.googlegroups.com...

On May 13, 11:40*am, "David Craig" <driv...@nowhere.us> wrote:
I have managed to build it successfully for Vista. Why is XP not
proper for this example?

This looks to be a very relevant topic that I'm attempting. I've managed to
build the genprint example for Vista environment, but I am confused when I'm
reading about the section on MSDN about "Installing a Print Processor." It
says that I have to write an INF file before using the AddPrinter function
while taking in a PRINTER_INFO_2 structure. There are a few questions that I
don't understand:

1. Do I need to have a printer driver and a print monitor dll files ready
with the genprint dll files before I add the print processor and associate
the print processor with a print queue?
2. I tried to call AddPrinter after calling AddPrintProcessor in a test app,
however, the compiler complaint about one of the parameter type conversion
being inappropriate. Is this why the WDK documentation tells the developers
to use an INF file to associate the print processor with a print queue?

"sleviantron@gmail.com" wrote: