1. Forum
  2. Usenet
  3. COMP.LANG.CLIPPER

  • Clipper 5.2 Printing Issue on Windows 2008 Server

    From John Ward@21:1/5 to All on Thu May 10 14:31:29 2018
    Has anyone encountered an issue running Clipper application in Windows 2008 32 bit server?

    Error TERM/0 Print error
    Severity: Error : Corrective Action Needed For Further Processing
    GenCode: EG_PRINT

    We are trying to print to the LPT1 port which is mapped to a network printer, and no matter what we try, clipper does not seem to see it.

    Yet, I can copy a PCL file to LPT1 from the command line, and that works.

    Would anyone have a clue what to try?

    Thanks in advance!

    John

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From dlzc@21:1/5 to John Ward on Thu May 10 18:02:13 2018
    Dear John Ward:

    On Thursday, May 10, 2018 at 2:31:30 PM UTC-7, John Ward wrote:
    ...
    We are trying to print to the LPT1 port which is mapped
    to a network printer, and no matter what we try, clipper
    does not seem to see it.

    Clipper is a DOS program, that runs inside a COMMAND.COM session. Did you do the printer network mapping in the batch file just before you call your executable?

    David A. Smith

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From info@wautersit.com@21:1/5 to All on Fri May 11 05:09:53 2018
    Hi,

    If your printer is connected on the physical LPT1 port, your application prints directly to the port. Notice that some printers don't allow DOS printing direclty, then you need to go "trough the Windows driver" using a redirection as show.


    You need to run this once on the machine:

    NET USE LPT1: \\computer\printer /PERSISTENT:YES [ /USER:userid thePassword ]

    Userid and password are optional if the printer configured on the same computer. Be sure the printer is shared -> Properties of the Printer -> Sharing.

    I never had a problem printing to a Windows printer this way and I never need to set up printerpooling.

    Regards,
    Frans

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John Ward@21:1/5 to All on Tue May 29 05:45:37 2018
    For everyone who asked... Yes, I properly mapped the LPT1 port to the printer, which is why copying a PCL file to LPT1 works.

    This only seems to happen on the Windows 2008 server. It works fine on XP, Windows 7, and Windows 2003 servers.

    It seems to be something specific to the Windows 2008 server, where my Clipper application is not recognizing the LPT1 port properly.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From dlzc@21:1/5 to John Ward on Tue May 29 06:37:14 2018
    Dear John Ward:

    On Tuesday, May 29, 2018 at 5:45:39 AM UTC-7, John Ward wrote:
    For everyone who asked... Yes, I properly mapped
    the LPT1 port to the printer, which is why copying
    a PCL file to LPT1 works.

    Did you do it in the same COMMAND.COM session that ran the Clipper program, via a batch file? "Properly" is something that Micro$haft changes routinely.

    Does the hardware actually have an LPT1 port?

    Can always take your code base and compile with (x)Harbour, and not have to mess around with port mapping. Only 3rd party libraries are the major stumbling blocks.

    David A. Smith

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From lawrence.edelstein@gmail.com@21:1/5 to dlzc on Tue May 29 17:19:19 2018
    On Tuesday, May 29, 2018 at 11:37:15 PM UTC+10, dlzc wrote:
    Dear John Ward:

    On Tuesday, May 29, 2018 at 5:45:39 AM UTC-7, John Ward wrote:
    For everyone who asked... Yes, I properly mapped
    the LPT1 port to the printer, which is why copying
    a PCL file to LPT1 works.

    Did you do it in the same COMMAND.COM session that ran the Clipper program, via a batch file? "Properly" is something that Micro$haft changes routinely.

    Does the hardware actually have an LPT1 port?

    Can always take your code base and compile with (x)Harbour, and not have to mess around with port mapping. Only 3rd party libraries are the major stumbling blocks.

    David A. Smith



    I print using PCL Esc to a file and then copy that file to a PCL enabled printer. Don't know if that is a solution anymore as I have gone down the XHarbour path

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)