Spooling for Native Windows filePro

[Lauren]

Windows apparently doesn't spool print jobs sent by native windows console
applications to local printer ports, the way that it does for MS-DOS programs
that do the same thing.  (That is, open "lpt1" as a file and write to it.)

We have added the necessary code to the native windows version of filePro
to use the Windows printer routines (ie: OpenPrinter, StartDocPrinter, etc.)
which do respect the Windows spooler.  However, the spooler is also limited
to those printers defined in the printer control panel.  Therefore, we have
made it a requirement that, in order to use the Windows spooler, you must
prefix the filePro destination with "win:", as in "win:lpt1:".   The rest
of the destination must be the exact port name or printer name as you have
defined it to Windows.   So, if you have a printer attached to LPT1 that is
named "HP DeskJet 870Cse", you would use either:

   win:lpt1:
or   win:HP DeskJet 870Cse

If you have a network printer "\\server\printer" that is captured to LPT2,
called "Bob's printer", and the Windows destination is "\\server\printer"
then you would use either:

   win:\\server\printer
or   win:Bob's printer

You could not use "win:lpt2:" as "lpt2" is not the destination that Windows
knows the printer by.  (Though you could use "lpt2" without the "win:" and
go directly to that port without the spooler.)

Remember:  You can only use the exact port name or printer name that Windows
uses.  Anything else will result in a "the parameter is incorrect" error when
filePro tries to open the printer.

[kenbrody]

Remember:  You can only use the exact port name or printer name that Windows uses.  Anything else will result in a "the parameter is incorrect" error when filePro tries to open the printer.

Note that, as of filePro version 5.6.02 (for Windows), you can press F6 in printer maintenance's printer setup screen to pop up a list of Windows-defined printers, and have filePro fill in the proper "win:printername" value for you.