Sponsored Content
Top Forums UNIX for Advanced & Expert Users connecting to unix through hyper terminal - as a dumb terminal Post 9915 by rwb1959 on Monday 5th of November 2001 01:44:16 PM
Old 11-05-2001
I'm a bit confused...

Can you verify my understanding of your problem...

1. You are physically connected directly to your UNIX
machine via a cable attached to your PC's serial port.
I assume you have a NULL Modem attached?

2. You are NOT using TCP/IP (dialing out to the Internet
via a modem).

3. You can no longer connect to your PC's COM port
using Hyper-Terminal.

Please let me know if these assumptions are correct
before we proceed further.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Solaris Sparc5 and connecting with a PC via Hyper terminal

I am trying to connect to a sparc5 with my PC via a null modem cable from serial port to serial port. I do not have a sun monitor so I am trying to use my PC. I am unsuccessful in even making the basic connection to the sparc box. Any ideas on how to work around this? (7 Replies)
Discussion started by: adrian
7 Replies

2. UNIX for Advanced & Expert Users

How to "Print Screen" from a dumb terminal on AIX?

Hello Everyone, How can I send a screen print of a dumb terminal to a printer? AIX v4.3.3 Thanks in advance. Suhas (3 Replies)
Discussion started by: stembe
3 Replies

3. Solaris

Sun Server Hyper Terminal

Anyone know how to connect to a sun server using serial cable my client PC is also a Sun !!! I have the cable , just do not know how to start a terminal session in Sun . (1 Reply)
Discussion started by: civic2005
1 Replies

4. UNIX for Advanced & Expert Users

Pseudo-terminal will not be allocated because stdin is not a terminal.

I am trying to automate a SSH login using Keys using the following command ssh -i id_rsa usernamw@ipaddr. I am successful in doing this and i am getting the Warning Screen and I logon successfully. but when I am executing the command tail -1cf put.dat | ssh -i id_rsa username@ipaddr > get.dat ... (1 Reply)
Discussion started by: Shivdatta
1 Replies

5. UNIX for Dummies Questions & Answers

Dumb gnome terminal question.

I've searched and searched but either I'm not using the right key words or the information isn't in print anywhere. I'm running Cent 5.3 and I have a number of terminal profiles setup to ssh into some of my Unix servers at work, what I'm trying to do is setup shortcuts on my desktop to those... (3 Replies)
Discussion started by: nixnoob
3 Replies

6. HP-UX

Adding "dumb terminal"

I have a small network of dumb terminals (9 HP 715 RISC machines OS Ver A.09.05) one as an application server, the other 8 diskless workstations. One workstation failed and I need to get a spare up on the network. With a bootable disk in the spare machine I found the MAC address of the spare... (1 Reply)
Discussion started by: gnappi
1 Replies

7. HP-UX

[Solved] Adding a "DUMB TERMINAL"

I have had a failure on an HP 715 workstation and luckily have plenty of spares to replace the failed one with. I know that on the server these files need to have the replacement machine configured: bootptab, hosts, and clusterconf I can ping the replacement workstation but the workstation... (4 Replies)
Discussion started by: gnappi
4 Replies

8. Shell Programming and Scripting

Cannot get terminal application to launch with a graphical launcher when successful in terminal

I have been having an extremely annoying problem. For the record, I am relatively new at this. I've only been working with unix-based OS's for roughly two years, mostly Xubuntu and some Kali. I am pretty familiar with the BASH language, as that's the default shell for debian. Now, I've made this... (16 Replies)
Discussion started by: Huitzilopochtli
16 Replies

9. Shell Programming and Scripting

Print Terminal Output Exactly how it Appears in the Terminal to a New Text File

Hello All, I have a text file containing output from a command that contains lots of escape/control characters that when viewed using vi or view, looks like jibberish. But when viewed using the cat command the output is formatted properly. Is there any way to take the output from the cat... (7 Replies)
Discussion started by: mrm5102
7 Replies

10. Shell Programming and Scripting

Wireless connecting via CLI/Terminal

Do you use the CLI a lot and encounter new Wi-Fi sources, but don't want to/can't remember the commands to connect to the Internet?? I'm lazy. I mean, that's what scripting is for, right?? Efficiency means obtaining the maximum result with maximum laziness. I wrote this small script a while ago and... (0 Replies)
Discussion started by: Huitzilopochtli
0 Replies
ports(7)						 Miscellaneous Information Manual						  ports(7)

NAME
ports, port_names - Device (tty and lp) names for serial and parallel ports SYNOPSIS
Default Serial Ports: /dev/tty00 /dev/tty01 (not present on a single-port system) Parallel Port: /dev/lp0 DESCRIPTION
AlphaStation and AlphaServer systems provide one or two 9-pin serial communication ports. These ports are usually labelled 1 (COMM1) and 2 (COMM2), but they may be identified by different icons. Using the appropriate serial cable and terminator, you can connect a serial printer, external modem, or character-cell terminal to a serial port. Most AlphaStation and AlphaServer systems also provide one parallel port, for use with a parallel printer. When you add a device to your system, the installation documentation may instruct you to map the device pathname to the port. These devices are located in the /dev directory. For serial-line ports, the two default device pathnames are: This pathname always maps to 1, COMM1, the lowest port number, an icon for a terminal console, or the only serial port (on a single-port system). This pathname always maps to 2, COMM2, the next numbered port, or (if one serial port is labeled with an icon for a terminal console) the remaining serial port. If your system hardware has been extended to include additional serial ports, the pathnames /dev/tty02, /dev/tty03, and so forth, may also be available to you. However, most systems have only /dev/tty00 and /dev/tty01 as the device pathnames for serial ports. The one parallel port on an AlphaStation or AlphaServer may be labeled with the word printer or a printer icon. On some systems, the paral- lel port may not be labeled. The device pathname for the parallel port is /dev/lp0. Currently, Tru64 UNIX does not fully support parallel printers, so fewer devices are connected to this port as compared to serial ports. If you are connecting a terminal console to your system, it must be connected to the serial port mapped to /dev/tty00. For other serial devices, it does not matter which of the serial ports you choose for the connection. For example, suppose you are setting up a system that has two serial ports, labeled 1 and 2. You intend to use a serial-line terminal rather than a workstation monitor as the system console and also want to connect a serial-line printer to the system. In this case, you must connect the terminal to the port labeled 1 (with the device pathname /dev/tty00). Therefore, you must connect the printer to the remaining port labeled 2 (with the device pathname /dev/tty01). If, for the same type of system, you intend to use a workstation monitor as the system console, it does not matter which serial port you use for a serial-line printer or modem. In other words, you can connect the printer to either port 1 (with pathname /dev/tty00) or port 2 (with pathname /dev/tty01). When prompted to enter a /dev/tty** pathname by the lprsetup script or the Print configuration tool in the CDE Application Manager, you would specify /dev/tty00 if you connected the printer to port 1 or /dev/tty01 if you connected the printer to port 2. See the System Administration manual for more information on setting up consoles (including remote consoles) and printers. See the modem(7) reference page for more information on setting up modems. SEE ALSO
Commands: lprsetup(8) Devices: ace(7), modem(7) System Administration delim off ports(7)
All times are GMT -4. The time now is 06:51 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy