Hello everyone. It is my first post and a tough one. Perhaps someone else has come across this before.
I am running on a Citrix based client / server application using Progress 9.1D. The server in question is a Windows 2000. A Windows NT server works fine. Also all client setups seem to produce the same problem, however I am running a Windows 2000 locally.
I am attempting to print to a Zebra DA402 although any Zebra printer will fail as we've tried others.
A Zebra printer, to the best of my knowledge, cannot take control codes. It only takes pure ASCII from 32 - 126.
I can print to LPT1: (locally) without problems. Using the Generic / Text driver, I can print through our Windows NT server without problems. I cannot print through Windows 2000 which leads me to believe it is a driver.
The Zebra Print Language (ZPL) uses ^'s (carats) for introductions to its internal code interpretation module. Remember, that a ^X is not a control-X, it is two characters, a carat and an X. This being said, here is what happens when I send a short stream.
The Zebra printer will seem to ignore everything and the queue will empty as if it has done it's job. If I unplug the printer, it will remain in the queue and give me a printer fault. As it should. If I print to the Laser printer, however, (using the 2000 driver) I get the first line indented a couple of spaces and all carat's chopped off on the left side. If I run it through the NT, they all appear. Yet, if I send it to a file or use any other driver, everything looks good.
Here is about as short of an example I can make that will produce the problem:
SYSTEM-DIALOG PRINTER-SETUP.
OUTPUT TO PRINTER.
PUT
"^XA^PR2^LH0,0^FS^LL1218^MD0^MNY^LH0,0^FS" SKIP
"^FO703,21^A0R,56,46^FDHello^FS" SKIP
"^PQ1,0,0,N" SKIP
"^XZ" SKIP.
OUTPUT CLOSE.
Any help will greatly be appreciated.
Randy
I am running on a Citrix based client / server application using Progress 9.1D. The server in question is a Windows 2000. A Windows NT server works fine. Also all client setups seem to produce the same problem, however I am running a Windows 2000 locally.
I am attempting to print to a Zebra DA402 although any Zebra printer will fail as we've tried others.
A Zebra printer, to the best of my knowledge, cannot take control codes. It only takes pure ASCII from 32 - 126.
I can print to LPT1: (locally) without problems. Using the Generic / Text driver, I can print through our Windows NT server without problems. I cannot print through Windows 2000 which leads me to believe it is a driver.
The Zebra Print Language (ZPL) uses ^'s (carats) for introductions to its internal code interpretation module. Remember, that a ^X is not a control-X, it is two characters, a carat and an X. This being said, here is what happens when I send a short stream.
The Zebra printer will seem to ignore everything and the queue will empty as if it has done it's job. If I unplug the printer, it will remain in the queue and give me a printer fault. As it should. If I print to the Laser printer, however, (using the 2000 driver) I get the first line indented a couple of spaces and all carat's chopped off on the left side. If I run it through the NT, they all appear. Yet, if I send it to a file or use any other driver, everything looks good.
Here is about as short of an example I can make that will produce the problem:
SYSTEM-DIALOG PRINTER-SETUP.
OUTPUT TO PRINTER.
PUT
"^XA^PR2^LH0,0^FS^LL1218^MD0^MNY^LH0,0^FS" SKIP
"^FO703,21^A0R,56,46^FDHello^FS" SKIP
"^PQ1,0,0,N" SKIP
"^XZ" SKIP.
OUTPUT CLOSE.
Any help will greatly be appreciated.
Randy