Conference jamin::pathworks32

249.0. "PowerTerm Printing from TMS to "Local Printer" as Network Printer" by nqos01.nqo.dec.com::respnt.ogo.dec.com::nuzzo (shrimp, ... plate of shrimp) Wed Apr 23 1997 10:43

Problem: Printing from TMS to "Local Printer" where default printer 
is a network printer.

Scenario:
1. NT 4.0 or WIN 95.
2. PowerTerm 525 V.4.00.38 installed WITHOUT Pathworks32 (just 
pwtelnt.dll and dectal.dll added)
3. Telnet connection to TMS
4. TMS configured to print to "local Printer"
5. Default Printer is a LPS17 on the network with Network Printer 
services provided by local NT Machines.
6. PowerTerm Terminal/Setup/Printer settings of:
   Printer Device = Print Manager
   Use Form Feed = Enabled
   Print Screen Data Conversion = Graphics
   Slave Printer Data Conversion = None
   Slave Printer Job Delimiter = None
7. Printing from TMS generates a PostScript Error and the job fails

If on # 6 the Printer Device = File and a local file is spec'd ... 
this does work but is not a nice way to 
work.

Now in KEA! v2.10 the above scenario can work by setting in KEA! 
Options/Terminal/Printer and enabling
Emulate ANSI Printer so that the Scenario above works.

Is there a similar setting to Emulate ANSI Printer in PowerTerm 525.

This is an important problem to me.  We are looking at having 
PowerTerm replace KEA! on the Sales Workbench;
we want to use a DIGITAL product (at least on we sell) on the systems 
our Sales Rep's use when possible. 
Any help is greatly appreciated.