Sponsored Content
Full Discussion: serial card in SCO Unix
Top Forums UNIX for Advanced & Expert Users serial card in SCO Unix Post 25570 by ArkiMage on Wednesday 31st of July 2002 11:03:49 PM
Old 08-01-2002
There's a dozen ways to skin this cat. This is how I setup modems for primarily dial-in access:

Hardware modems are best.. Not "WinModems".

Get the serial port working the modem is on, I'll assume COM1 or tty1A.

Hook the modem to a terminal or PC and set the baud rate to something appropriate (115,000bps for a 56K modem perhaps). Enter the appropriate AT commands to disable echo and result codes and turn on auto-answer. If there's a setting to "lock" the serial baud rate, enable that. If not, most of the time this is remembered by the speed the terminal or terminal emulator are running at when you do an AT&W.

Set the port in inittab something like this:
Se1A:234:respawn:/usr/lib/uucp/uugetty -t60 tty1A 6

The "6" in the gettydefs file I modified for the baud rate I wanted. Here it is set for 19,200bps which along with 115,000 isn't in the gettydefs file by default (for modems) I think:

6 # B19200 HUPCL # B19200 CS8 ORTSFL SANE HUPCL TAB3 ECHOE IXANY #login: # 6

Also notice the ORTSFL which sets CTS/RTS hardware flow control. Very important for high-speed modems.

Good luck!
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

terminal/port (serial) lock up mystery! SCO 5.0

Sorta new to Unix. great site here. I have SCO server with (5) 16 port Digi-boards and 5 line printers. For 3 years we've had no problems, till now... All of a sudden I get terminals and printers locking up. Killed the PID's for these particular situations. No help. So I disable the tty post... (10 Replies)
Discussion started by: ftn96
10 Replies

2. Filesystems, Disks and Memory

SCO TCP/IP runtime System for SCO Unix

Hi everyone i have a question for all of you. It may be basic or it may be a good one. I recently aquired a copy of "SCO TCP/IP runtime System for SCO Unix" (thats what the disks say) and for the life of me i can not get it to load. i have tried opening the disk in linux and it can not determine... (0 Replies)
Discussion started by: Cerberus
0 Replies

3. UNIX for Dummies Questions & Answers

Unix sco 5.0.6 Serial card

Hi guys how r you doing. I have a ISI 4608 is a serial card from multi-tech system, i'm installing it on sco 5.0.6. The driver version that i'm using is VER 3.01. the reason i'm doing this is because i have a APC power supply that works with unix. Ones i do the firts install of the... (1 Reply)
Discussion started by: josramon
1 Replies

4. UNIX for Dummies Questions & Answers

Disable form feed on a serial printer connected to Sco OpenServer

I connected a serial printer to my scoOpenServer which works great. I was able to disable the banner in the interface of the printer. However i am unable to find the command in the interface to disable the formfeed . Below is a copy of the interface file. Please can anyone instruct me on how to... (0 Replies)
Discussion started by: scoman2
0 Replies

5. SCO

3c905b network card problem with SCO 5.0.5

Hi, I was wondering if anyone could help me out with this problem. I have SCO 5.0.5 installed on a system that I am using 3c905b (3 Com) network card. This system is always powered on. After no certain time period this NIC doesn't work. I can't ping to this system from any other machine or vice... (2 Replies)
Discussion started by: AtALoss
2 Replies

6. SCO

SCO 5.0.7 and Serial ATA HDD question

Hi guys, I have this quick question , is it posible to isntall SCO 5.0.7 on a serial ATA and if it is can you tell me how or maybe a website that has some info about this. I'm not using any raid, just one HDD. Thanks a lot (0 Replies)
Discussion started by: josramon
0 Replies

7. UNIX for Dummies Questions & Answers

isa serial port adapter card no longer detectedworking

hi all, i've got an old PC with unix (SCO System V/386 rel. 3.2) on it. Pentium I; 128mb; ISA 2-port RS232 serial adapter card for an oki dot-matrix printer. (no usb, no CD) i've been running an old cobol program to do some invoicing and print reports. some time back i changed the... (0 Replies)
Discussion started by: frankpky
0 Replies

8. Shell Programming and Scripting

Auto sending text files from SCO box to a PC via serial cable

I have an SCO system with several PC's hooked up via ProComm and serial cabling (no Ethernet). I want to occasionally transfer a small text file from the UNIX system to a specific PC without the PC operator having to do anything (she may be out to lunch or doing other work during the transfer) ... (0 Replies)
Discussion started by: gbrowne
0 Replies

9. SCO

Problems with network card in SCO

hello, i am new to unix and need support</SPAN></SPAN> </SPAN></SPAN>The problem is: I have a SCO 5.0.5 server, and has no local network access, I think my problem are the drivers for network card. my network card is Kingston EtheRx PCI Fast Ethernet Adapter KNE120TX and already installed the... (9 Replies)
Discussion started by: daniel_cie
9 Replies

10. Solaris

Looking for driver for SunSAI/P 3.0 (Serial Asynchronous Interface) card X2156A

I'm looking for driver for SunSAI/P 3.0 (Serial Asynchronous Interface) card X2156A for Solaris. It used to be on sun-solve, but I fail to find it on the Oracle site. Any help would be very appreciated! (1 Reply)
Discussion started by: Ira28
1 Replies
modem(7)						 Miscellaneous Information Manual						  modem(7)

NAME
modem - Describes guidelines for using modems DESCRIPTION
The Tru64 UNIX system enables you to use a variety of modems for point-to-point connections to systems that are not in close proximity to each other. These connections can be Serial Line Internet Protocol (SLIP), Point-to-Point Protocol (PPP), and UNIX-to-UNIX Copy Program (UUCP) connections. In addition, these connections can be basic dial-out/dial-in connections (for example, to log in to a remote system to perform remote system administration). This section presents general guidelines for using modems on Tru64 UNIX systems for all types of connections. See Network Administration for specific information on SLIP, PPP, and UUCP connections. Using the Correct Modem Cables In order to connect a modem to the serial port of your system, you must use the correct cable. If you do not, you might experience signal loss, resulting in the software not functioning properly. The following table lists the cables you should use. The cable connector is either 25-pin or 9-pin, depending on the type of serial port on your system. See the hardware documentation for your system if you are unsure about the type of serial port. Note OPEN DECconnect cables do not provide a sufficient number of wires for full modem control. You should not use them for connecting modems to the system. ------------------------------------------------------------------------------ Cable Number Description ------------------------------------------------------------------------------ BC22E-xx 16-wire modem cable (Male DB25 pin to female DB25 pin cable) BC22F-xx 25-wire modem cable (Male DB25 pin to female DB25 pin cable) BC29P-xx Male DB25 pin to female DB9 pin cable PC modem cable Male DB25 pin to female DB9 pin cable In the previous table, xx denotes the cable length. For example, BC22E-10 is a ten-foot cable. Configuring a System for Dial-In Access After you have obtained the correct cable and connected your modem to it and the telephone network, do the following: Edit the /etc/remote file and create an entry similar to the kdebug entry. For example, if your modem is connected to tty00 and you are going to use a baud rate of 38400 to access the modem, create an entry similar to the following: b38400:dv=/dev/tty00:br#38400:pa=none Note Some modems set their baud rate to the serial port rate. Be sure to access the modem using the same baud rate that you are going to specify to getty or uugetty. Otherwise, you might not be able to log in because of a mismatch in baud rates. See ports(7) if you are unsure which port your modem is connected to. Use the tip command to access the modem as follows: tip b38400 The tip utility responds with a connected message. You can now communicate with the modem. If your modem is using the AT command language, enter the following command: at<Return> If the modem is not in quiet mode, it responds with an OK message. Set the modem up for dial-in access. The following table lists the AT commands required. Most of these command settings are the default settings. -------------------------------------------------------------------------- Command Description -------------------------------------------------------------------------- at&c1 Normal Carrier Detect (CD) operation. Tells the modem to not raise Carrier Detect until it see Carrier Detect from the other modem. at&d2 Normal Data Terminal Ready (DTR) operation. This is important in that it tells the modem to hang up the line when DTR drops. For example, when the user logs off the system. atq1 Sets the modem into quiet mode. Result codes are not sent to the system. ate0 Echo off. This prevents the modem from echoing back the login prompt issued by the getty process. ats0=n Specifies the number of rings to wait before answering. If n = 0 (zero), the modem will not answer. at&w0 Saves the current modem settings in NVRAM. The operating system supports both hardware and software flow control. If the system supports hardware flow control, set the modem and the serial line up to use hardware flow control by using the appropriate commands. If hardware flow control is not supported, you should use software flow control. Edit the /etc/inittab file and create an entry for the modem. If you want to use the modem line in non-shared mode, create an entry similar to the following: modem:23:respawn:/usr/sbin/getty /dev/tty00 M38400 vt100 If you want to use the modem line in shared mode (for dial-out and dial-in connections), use uugetty instead of getty and create an entry similar to the following: modem:23:respawn:/usr/lib/uucp/uugetty -r -t 60 tty00 38400 With uugetty, you will be able to use the tip and cu utilities, but might not be able to use third-party utilities because of dif- ferences in file locking. Note If you want to use the uugetty utility, you must install the UNIX-to-UNIX Copy Facility subset. As root, start the getty or uugetty process by entering the following command: init q The getty or uugetty process starts, then goes to sleep, waiting for someone to dial into the system. Configuring Your System for Dial-Out Access After you have obtained the correct cable and connected your modem to it and the telephone network, do the following: Verify that there is an entry for the modem name specified with the modemtype subcommand in the /etc/acucap file. If your modem does not have an entry in the /etc/acucap file, do the following: Copy an entry similar to that of your modem. The following entry is for a US Robotics modem for use in shared mode with tip: us|US|US Robotics (28.8 fax/data modem): :cr:hu:ls:re:ss=AT ATE1Q0&C0X0&A0 :sr=OK: :sd#250000:di=ATD:dt= : :dd#50000:fd#50:os=CONNECT:ds=d+++dATZ dATS0=2 : :ab=d+++dATZ dATS0=2: Be sure the entry includes at least the AT commands in the following table. The other modem settings can remain as they are. ------------------------------------- Command Description ------------------------------------- ate1 Turns on echoing. atq0 Displays the result codes. Modify the modem attributes to match your modem's attributes and include the debug option (db). With debugging turned on, the modem will provide you with additional information with which to tune the modem attributes in the file. See acucap(4) for more informa- tion. Create an entry in the /etc/remote for the system you want to call. Among the information you can supply is the Tru64 UNIX device, baud rate, and /etc/acucap that defines your modem. The following two entries are for the modem specified in step 1a. tip38400:tc=us38400 us38400|38400 Baud dial out via US Robotics modem: :el=^U^C^R^O^D^S^Q@:ie=#%$:oe=^D: :dv=/dev/tty00:br#38400:ps=none:at=us:du: In the previous example, the first line is an entry that points to the us38400 entry specifying shared capabilities for modems. The second line is the first line of the us38400 entry. The third line defines end-of-line characters, and input and output end-of-file marks. The fourth line defines the UNIX device to open for the connection, the baud rate, the parity, the name of the /etc/acucap file entry, and the dial-up line. See remote(4) for more information. If you use getty to provide access to the system from a modem and a getty process is already running, do the following: Edit the /etc/inittab file and put a comment character (#) at the beginning of the modem entry. Issue the init q command to terminate the getty process. Use the tip command, specifying the -baud_rate flag and the telephone number to dial out as follows: tip -38400 8881234 In this example, tip strips off the minus sign (-) from the baud rate and concatenates the tip command name and the baud rate to create the string tip38400. Then, tip searches the /etc/remote file for the entry matching the string. The entry in the /etc/remotes file, points the capability information in the us38400 entry to initialize the modem. By specifying the telephone number on the command line, you can share the same modem attributes for outgoing connections that have different telephone numbers. When you log off the remote system and exit tip, the modems saved settings are restored, readying the modem for the next user. If used in shared mode, the modem is available for dial-in access. RELATED INFORMATION
Commands: cu(1), tip(1), getty(8), uugetty(8). Files: acucap(4), inittab(4), remote(4). Devices: ports(7). Network Administration delim off modem(7)
All times are GMT -4. The time now is 12:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy