Comtrol RocketPort Series Device Driver for the SCO UnixWare 7 - Manual (Page 6)

RocketPort® Series Device Driver for the SCO UnixWare 7 Operating System Software Installation Card 6 of 8
9. You may now direct output to the printer via the tprint
device name. For example, enter this command:
ls> /dev/term/tpr0a
This should print a listing of the present working
directory on the printer, without printing to the
terminal screen.
10. To further test the printer, cat files to /dev/term/tpr0a.
11. Login on the terminal and cat files to the printer. The
video display should not stop while printing is in
progress.
Common Installation Issues
Before you call Comtrol technical support, please use
following checklist:
• Check to make sure all cables are connected properly.
• Check the signals between your peripherals and the
RocketPort interface box to verify that they match (if
applicable). See the RocketPort Hardware Installation
Card for port pinouts.
• If using RocketPort/ISA cards, check the DIP switch
settings on each card to verify that the addresses are
correct.
• Use /sbin/dcu to examine the system memory usage for
conflicts.
• Make sure the controller board is seated firmly in the
bus slot and the expansion slot screw is in place.
• Reinstall the board and driver, selecting a different
I/O address range for the controller.
If this fails to resolve the problem, run the diagnostic:
1. Shut down your system.
2. Insert the RocketPort Diagnostics diskette in your
primary drive.
3. Power-up your system, and allow it to boot from the
diagnostic diskette.
4. Follow the on-screen instructions.
Solving Modem-Related Problems
If you have problems connecting to a modem-equipped
port, disconnect the cable to the modem or turn off the
modem. You can use the cu command to test a port with no
modem present by using the loopback plug. Attach the
loopback plug to the port being tested and enter data; it
should appear (echo) to your screen.
After connecting to the port, reconnect or power on the
modem and set the modem parameters.
If you get a “connected” message when you test the modem
with cu but no response to an AT command, follow these
steps:
1. After issuing the cu command, press Enter several
times and watch the lights on the modem. The receive
light should flash. If only the send light flashes, the
local echo may be turned off. Use the ATE1 command to
turn on the modem’s local echo feature.
2. Verify that the modem switch and software settings
are correct.
3. Check the modem cable to make sure it is attached at
both ends.
4. If no lights flash, the modem cable may be defective.
Replace it.
5. Move the modem to a standard serial port and try it
there. If it works on a standard port but not on a
RocketPort port, the problem lies in the RocketPort
board or port configuration.
6. Move the modem back to the RocketPort port.
7. Use the RocketPort Diagnostics to verify that the port is
working.
Solving Printer-Related Problems
To identify and resolve printer problems not related to
transparent print, follow these steps:
1. Verify that a serial printer is powered up, connected to
the correct port, and on-line.
2. Verify that the printer is connected using the correct
cable. See the RocketPort Hardware Installation Card
and your printer manual for connector pinouts and
cable specifications.
3. Move the printer to a standard serial port, and try it
there. If it works on a standard port but not on a
RocketPort, the problem may lie in the RocketPort
board or port configuration.
4. Move the printer back to a RocketPort port.
5. Enter this command to send a file directly to the
printer port:
cat /etc/termcap >/dev/term/rXX
Where XX is the port to which the printer is attached.
a. If you get nothing, check to make sure the device
driver is loaded, the port is enabled, and that you
are in fact connected to the port you think you’re
connected to. If all of this is true, connect the
printer to the COM1 or COM2 port and repeat this
step. If the printer still fails to print, the problem is
in the printer. If the printer does print, run the
RocketPort diagnostic.
b. If you get a partial file printout or garbled
characters, go to the sections on Flow Control.
c. If the file is printed correctly, but you are unable to
print from an application, check the application
setup.
d. If the file is printed correctly, but you are unable to
print through the UNIX spooler, go to the section
on UNIX Spooler Problems.