Skip to main content

[archive] WIN$PRINTER on Win XP not working

  • January 13, 2011
  • 9 replies
  • 0 views
D

[Migrated content. Thread originally posted on 12 January 2011]

We have a client that upgraded from Acu Runtime 7.2.2 to Acu 8.1. In our software we capture the CTL-P key press to print the screen to the default printer. I have debugged this and when the WIN$PRINTER is executed a return code of 0 (zero) is returned from WIN$PRINTER. This code is returned whenever WIN$PRINTER is called on a machine that is not a Windows machine. Obviously it is a Windows computer, Windows XP with latest patches installed.

What dll is WIN$PRINTER in from AcuCorp?

Here is the code were it is blowing up:

CALL "WIN$PRINTER" USING WINPRINT-GET-NO-PRINTERS
WINPRINT-SELECTION
GIVING CALL-RESULT.
The client does have printers installed that are not actually connected to the workstation, could this be the actual error?

Does anyone have any ideas

Thanks, Jim Whalen

    9 replies

    D

    [Migrated content. Thread originally posted on 12 January 2011]

    We have a client that upgraded from Acu Runtime 7.2.2 to Acu 8.1. In our software we capture the CTL-P key press to print the screen to the default printer. I have debugged this and when the WIN$PRINTER is executed a return code of 0 (zero) is returned from WIN$PRINTER. This code is returned whenever WIN$PRINTER is called on a machine that is not a Windows machine. Obviously it is a Windows computer, Windows XP with latest patches installed.

    What dll is WIN$PRINTER in from AcuCorp?

    Here is the code were it is blowing up:

    CALL "WIN$PRINTER" USING WINPRINT-GET-NO-PRINTERS
    WINPRINT-SELECTION
    GIVING CALL-RESULT.
    The client does have printers installed that are not actually connected to the workstation, could this be the actual error?

    Does anyone have any ideas

    Thanks, Jim Whalen
    Hi Jim,

    Try turning on WINPRINT_NAMES_ONLY before the call to get-no-printers.

    SET ENVIRONMENT "WINPRINT-NAMES-ONLY" TO 1.

    Then set it back to zero when you want to get detailed information about the printer.

    See the graphprn.cbl sample program for details.
    D

    [Migrated content. Thread originally posted on 12 January 2011]

    We have a client that upgraded from Acu Runtime 7.2.2 to Acu 8.1. In our software we capture the CTL-P key press to print the screen to the default printer. I have debugged this and when the WIN$PRINTER is executed a return code of 0 (zero) is returned from WIN$PRINTER. This code is returned whenever WIN$PRINTER is called on a machine that is not a Windows machine. Obviously it is a Windows computer, Windows XP with latest patches installed.

    What dll is WIN$PRINTER in from AcuCorp?

    Here is the code were it is blowing up:

    CALL "WIN$PRINTER" USING WINPRINT-GET-NO-PRINTERS
    WINPRINT-SELECTION
    GIVING CALL-RESULT.
    The client does have printers installed that are not actually connected to the workstation, could this be the actual error?

    Does anyone have any ideas

    Thanks, Jim Whalen
    Hi Jim,

    Try turning on WINPRINT_NAMES_ONLY before the call to get-no-printers.

    SET ENVIRONMENT "WINPRINT-NAMES-ONLY" TO 1.

    Then set it back to zero when you want to get detailed information about the printer.

    See the graphprn.cbl sample program for details.
    D

    [Migrated content. Thread originally posted on 12 January 2011]

    We have a client that upgraded from Acu Runtime 7.2.2 to Acu 8.1. In our software we capture the CTL-P key press to print the screen to the default printer. I have debugged this and when the WIN$PRINTER is executed a return code of 0 (zero) is returned from WIN$PRINTER. This code is returned whenever WIN$PRINTER is called on a machine that is not a Windows machine. Obviously it is a Windows computer, Windows XP with latest patches installed.

    What dll is WIN$PRINTER in from AcuCorp?

    Here is the code were it is blowing up:

    CALL "WIN$PRINTER" USING WINPRINT-GET-NO-PRINTERS
    WINPRINT-SELECTION
    GIVING CALL-RESULT.
    The client does have printers installed that are not actually connected to the workstation, could this be the actual error?

    Does anyone have any ideas

    Thanks, Jim Whalen
    Hi Jim,

    Try turning on WINPRINT_NAMES_ONLY before the call to get-no-printers.

    SET ENVIRONMENT "WINPRINT-NAMES-ONLY" TO 1.

    Then set it back to zero when you want to get detailed information about the printer.

    See the graphprn.cbl sample program for details.
    D

    [Migrated content. Thread originally posted on 12 January 2011]

    We have a client that upgraded from Acu Runtime 7.2.2 to Acu 8.1. In our software we capture the CTL-P key press to print the screen to the default printer. I have debugged this and when the WIN$PRINTER is executed a return code of 0 (zero) is returned from WIN$PRINTER. This code is returned whenever WIN$PRINTER is called on a machine that is not a Windows machine. Obviously it is a Windows computer, Windows XP with latest patches installed.

    What dll is WIN$PRINTER in from AcuCorp?

    Here is the code were it is blowing up:

    CALL "WIN$PRINTER" USING WINPRINT-GET-NO-PRINTERS
    WINPRINT-SELECTION
    GIVING CALL-RESULT.
    The client does have printers installed that are not actually connected to the workstation, could this be the actual error?

    Does anyone have any ideas

    Thanks, Jim Whalen
    Does this happen on any XP installation, or this workstation in particular?

    It should not matter whether there are remote printers. I assume they have local printers as well?

    Does it reproduce with any of the example programs provided, like the one Doug suggests? (graphprn.cbl, prndemox.cbl)
    D

    [Migrated content. Thread originally posted on 12 January 2011]

    We have a client that upgraded from Acu Runtime 7.2.2 to Acu 8.1. In our software we capture the CTL-P key press to print the screen to the default printer. I have debugged this and when the WIN$PRINTER is executed a return code of 0 (zero) is returned from WIN$PRINTER. This code is returned whenever WIN$PRINTER is called on a machine that is not a Windows machine. Obviously it is a Windows computer, Windows XP with latest patches installed.

    What dll is WIN$PRINTER in from AcuCorp?

    Here is the code were it is blowing up:

    CALL "WIN$PRINTER" USING WINPRINT-GET-NO-PRINTERS
    WINPRINT-SELECTION
    GIVING CALL-RESULT.
    The client does have printers installed that are not actually connected to the workstation, could this be the actual error?

    Does anyone have any ideas

    Thanks, Jim Whalen
    Well the funny thing about this is we have 2 different versions of our software installed on this WIN XP machine. The old version is using the 7.2 version of the runtime and the New version is using the 8.1 version of the runtime. The old version works fine but the new version does not work.

    What version of the .Net framework does Acu runtime 8.1 require?

    The actual program issueing the WIN$PRINTER call has not changed between the different versions.
    D

    [Migrated content. Thread originally posted on 12 January 2011]

    We have a client that upgraded from Acu Runtime 7.2.2 to Acu 8.1. In our software we capture the CTL-P key press to print the screen to the default printer. I have debugged this and when the WIN$PRINTER is executed a return code of 0 (zero) is returned from WIN$PRINTER. This code is returned whenever WIN$PRINTER is called on a machine that is not a Windows machine. Obviously it is a Windows computer, Windows XP with latest patches installed.

    What dll is WIN$PRINTER in from AcuCorp?

    Here is the code were it is blowing up:

    CALL "WIN$PRINTER" USING WINPRINT-GET-NO-PRINTERS
    WINPRINT-SELECTION
    GIVING CALL-RESULT.
    The client does have printers installed that are not actually connected to the workstation, could this be the actual error?

    Does anyone have any ideas

    Thanks, Jim Whalen
    If the runtime starts, then the version of the .Net framework is not the issue. There is no use of .net in the printing routine.

    Have you tried one of the standard sample programs?
    D

    [Migrated content. Thread originally posted on 12 January 2011]

    We have a client that upgraded from Acu Runtime 7.2.2 to Acu 8.1. In our software we capture the CTL-P key press to print the screen to the default printer. I have debugged this and when the WIN$PRINTER is executed a return code of 0 (zero) is returned from WIN$PRINTER. This code is returned whenever WIN$PRINTER is called on a machine that is not a Windows machine. Obviously it is a Windows computer, Windows XP with latest patches installed.

    What dll is WIN$PRINTER in from AcuCorp?

    Here is the code were it is blowing up:

    CALL "WIN$PRINTER" USING WINPRINT-GET-NO-PRINTERS
    WINPRINT-SELECTION
    GIVING CALL-RESULT.
    The client does have printers installed that are not actually connected to the workstation, could this be the actual error?

    Does anyone have any ideas

    Thanks, Jim Whalen
    If the runtime starts, then the version of the .Net framework is not the issue. There is no use of .net in the printing routine.

    Have you tried one of the standard sample programs?
    D

    [Migrated content. Thread originally posted on 12 January 2011]

    We have a client that upgraded from Acu Runtime 7.2.2 to Acu 8.1. In our software we capture the CTL-P key press to print the screen to the default printer. I have debugged this and when the WIN$PRINTER is executed a return code of 0 (zero) is returned from WIN$PRINTER. This code is returned whenever WIN$PRINTER is called on a machine that is not a Windows machine. Obviously it is a Windows computer, Windows XP with latest patches installed.

    What dll is WIN$PRINTER in from AcuCorp?

    Here is the code were it is blowing up:

    CALL "WIN$PRINTER" USING WINPRINT-GET-NO-PRINTERS
    WINPRINT-SELECTION
    GIVING CALL-RESULT.
    The client does have printers installed that are not actually connected to the workstation, could this be the actual error?

    Does anyone have any ideas

    Thanks, Jim Whalen
    If the runtime starts, then the version of the .Net framework is not the issue. There is no use of .net in the printing routine.

    Have you tried one of the standard sample programs?
    D

    [Migrated content. Thread originally posted on 12 January 2011]

    We have a client that upgraded from Acu Runtime 7.2.2 to Acu 8.1. In our software we capture the CTL-P key press to print the screen to the default printer. I have debugged this and when the WIN$PRINTER is executed a return code of 0 (zero) is returned from WIN$PRINTER. This code is returned whenever WIN$PRINTER is called on a machine that is not a Windows machine. Obviously it is a Windows computer, Windows XP with latest patches installed.

    What dll is WIN$PRINTER in from AcuCorp?

    Here is the code were it is blowing up:

    CALL "WIN$PRINTER" USING WINPRINT-GET-NO-PRINTERS
    WINPRINT-SELECTION
    GIVING CALL-RESULT.
    The client does have printers installed that are not actually connected to the workstation, could this be the actual error?

    Does anyone have any ideas

    Thanks, Jim Whalen
    I don't know if it makes any difference, but there are different set of Microsoft DLL's used for 7.2 versus 8.1. Have you installed the different set with the appropriate runtime?

    Recent badge winners

    Explore all badges
    Terms & ConditionsAccessibility statement