![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
#4
| |||
| |||
|
|
Hi Steve - No workaround except for sending the data from the host twice. When AccuTerm is in Text mode, it simply passes the data received from the host to the Windows spooler, which sends it on to the printer. In Graphics mode, the data is "drawn" on a page using the Windows printer driver, thus you can specify the number of copies, font, etc. Tradeoffs ... tradeoffs ... Thanks, Peter |
#5
| |||
| |||
|
|
Steve, You don't mention your platform, but if D3 then how about using the sp-assign copies + "alternate port" feature, e.g. :sp-assign 2 as :sp-assign ? Line# Status Copies Form# Device 113 s a 2 0 Functionality depends on your terminal emulation, but I have had good success with VT100 and Wyse 60. Just "sp-assign as" then print whatever, and voila, local print-out. I use this feature a lot for remote ssh users, who get "sp-assign a" in their login proc, so that whenever they print anything it comes out on their local windows printer. Here are the relevant parts from the 'sp-assign' entry in ref: number.copies (integer number in the range 1-125) indicating the number of copies. (default = one). a Ouput goes to the alternate port on the current terminal. To function correctly, the auxiliary port on and off commands must be defined for the current terminal in the devices file. Note that the a option does not suppress output to the system printer by default. To disable system printer output, use the "s" option as well. /Scott Ballinger Pareto Corporation Edmonds WA USA 206 713 6006 Peter Schellenbach wrote: Hi Steve - No workaround except for sending the data from the host twice. When AccuTerm is in Text mode, it simply passes the data received from the host to the Windows spooler, which sends it on to the printer. In Graphics mode, the data is "drawn" on a page using the Windows printer driver, thus you can specify the number of copies, font, etc. Tradeoffs ... tradeoffs ... Thanks, Peter |
#6
| |||
| |||
|
#7
| |||
| |||
|
|
There are a usually many flavors of "adds" and "viewpoint" terminals in the devices file. You may need to try different ones. You can also tweak the terminal definition item using "define-terminal." It may be that the viewpoint will not support this feature. My recollection is that a viewpoint does not have a "pass-through" print mode (the text going to the slave port also scrolls past on the screen- pretty ugly. That's why they called it a "slave" port and not a "printer" port.) If you don't want to change your terminal type (why not by the way?... viewpoint does not support more than one screen attribute at a time and is hideous in many other ways as well) then you could use the accuterm command to change the emulation to one that does support pass-through printing (e.g. vt100), execute a "term vt100" command on d3, execute "sp-assign as", print something, then switch it all back. /Scott |
#8
| |||
| |||
|
|
Hi Steve - No workaround except for sending the data from the host twice. When AccuTerm is in Text mode, it simply passes the data received from the host to the Windows spooler, which sends it on to the printer. In Graphics mode, the data is "drawn" on a page using the Windows printer driver, thus you can specify the number of copies, font, etc. Tradeoffs ... tradeoffs ... Thanks, Peter |
#9
| |||
| |||
|
|
Does anyone have a workaround for this? If you are on an office LAN, perhaps you could bounce the print job off |
![]() |
| Thread Tools | |
| Display Modes | |
| |