wanttore.blogg.se

Tinyterm term script language
Tinyterm term script language










tinyterm term script language

Instead I put the codes in the printer interface script where I have full control of what is actually being sent, and can make modifications as required for my terminal emulation software. I myself don't use the PN and PF codes in termcaps because I could never get them to work right. I have been using terminal client printing for a couple of years now, so I am familiar with many of the problems involved. Ok, I've been watching this thread with some interest.

tinyterm term script language

Perhaps it will be of assistance to someone in the future.īill McClure RE: Terminal emulation software, client print problem edfair (TechnicalUser) 28 Oct 03 22:48 Much thanks to everyone who responded to this issue. I would like to understand what is configured in the standard interface that the printer liked when it was attached to a WYSE terminal, but didn't like when it was operating through a terminal emulator. Finally, on a whim, I changed the pra08 printer model to "SCO emulator," a very simple interface. I tried issuing various ditty commands per advice. Both Anzio and Kermit95 would print one job to the printer and a subsequent job to the screen of the emulator, requiring a kill to continue use. In the beginning, the printer model in Digi was "SCO standard" per their instructions. I could probably switch back to to WYSE at this point. I did have the term type as WYSE 60, with no solution to the problem. On the printer, pra08, type = term, term type = ansi, onstr & offstr = digi preset parameters for ansi. The set up in the Digi software was ttya08, type = term, 19200, 8-1-N, software flow = xon/xoff, hwflow = none, fbaud=off.

tinyterm term script language

It is now working!!!! I worked with Anzio - very nice people -, Kermit95, and DigiBoard, with no solution.












Tinyterm term script language