- Tinyterm wrong server serial#
- Tinyterm wrong server full#
- Tinyterm wrong server software#
- Tinyterm wrong server password#
Tinyterm wrong server software#
The thing to recognize is that most terminal emulation software is designed specifically for screen display, and does not support the more obscure terminal features. Most likely the reason why you are having problems is because you have moved from an actual terminal device to software that emulates a device on a PC.
Tinyterm wrong server full#
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. 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. I know nothing about Unix and our IT people at work have been no help since I am the only person having problems.Īny thoughts, suggestions would be greatly appreciated.It is now working!!!! I worked with Anzio - very nice people -, Kermit95, and DigiBoard, with no solution. I have been working with Microsoft support on this for about a month as well as posting on several Win 2K forums to no avail. I also have another machine running Windows 98 that connects fine using the same emulator. If I use "hyper-terminal" to connect, I get an error message "error 737 loopback detected".Īll other dial-up funtions (aol, AT&T, etc ) work fine. I have un-installed all of these in one machine but still have the problem. I also installed three programs Drive Image 2002, WebWasher, and Ad-Adware. The only changes I made to the machines around the time this problem started was the installation of Service Pac 3.
Tinyterm wrong server password#
If I type really fast, it will accept the login name and asks for my password before it disconnects. When I call the server, it connects and asks for my login name and then just disconnects me. The specifics are as follows: (both machines) I have been using this for several years with no problems.Ībout a month ago, I discovered that I could no longer connect to the server on either of my machines.
Tinyterm wrong server serial#
We dial in through a modem using serial protocol. I travel for a living and use a terminal emulation program called STEP to connect to our Unix based server at work.
I have two computers running Windows 2000 Pro. This post will be rather lengtly but needs to be to explain the problem. Am new to the forum and hope this post meets the requirements.
0 kommentar(er)
