home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.unix.admin:4906 comp.unix.misc:3538 comp.misc:3596
- Newsgroups: comp.unix.admin,comp.unix.misc,comp.misc
- Path: sparky!uunet!pilchuck!fnx!del
- From: del@fnx.uucp (Dag Erik Lindberg)
- Subject: Re: What is the best way to communicate remotely?
- Message-ID: <1992Sep6.181858.10279@fnx.uucp>
- Organization: I/Ovations
- References: <1992Sep04.172530.22261@wap.oau.org>
- Distribution: usa
- Date: Sun, 6 Sep 1992 18:18:58 GMT
- Lines: 26
-
- In <1992Sep04.172530.22261@wap.oau.org> bdixon@wap.oau.org (Bill Dixon) writes:
-
- >I just found out that my company plans to open up warehouses out of state
- >in the next 2 or 3 months, and of course they want terminals and printers
- >there.
-
- >If it was just terminals they wanted, I would just give them PC's with a
- >modem running ProComm. But I don't know how to handle the printers. I
- >have toyed with the idea of faxing their reports to them with a fax modem
- >(which I don't have right now, but this would give me justification to get
- >one :).
-
- I would suggest using remote terminals with printer ports (auxilliary
- serial ports) attached. Such terminals have special codes which can
- be sent which will allow the screen/keyboard to be disabled and the
- aux port to be enabled. There is special Unix drivers available which
- will allow this feature to be used to implement a standard 'lp' device
- which will print through that terminal, while allowing a normal login
- session to run at the keyboard. The user will notice some response
- degradation while the printer is active, but in general it works well.
-
- The Wyse 60 is a fairly 'standard' terminal which will do what you want.
-
- --
- del AKA Erik Lindberg uunet!pilchuck!fnx!del
- Who is John Galt?
-