I am so sorry to be asking this.I am working on an SCO 3.2 system that has a serial terminal card with 8 ports and four are in use. This system has been running for years. The DAT drive died and the BIOS battery was dead so we shut it down to remove the DAT and replace the battery. When we powered it backup the terminal did not work. Using these links

http://www.tek-tips.com/gfaqs.cfm/lev2/3/lev3/20/pid/58/fid/1437
http://www.aplawrence.com/SCOFAQ/scotec6.html

I was able to find that the serial card is /dev/tty3* with these ports, tty3a, tty3b, tty3c, tty3d. I also found that the /etc/inittab had tty3A, tty3B, tty3C, tty3D where off.

When I start the terminals they don't show any text but the cursor flashes. To test if the card was still working I disabled all terminals by doing disable tty3a, disable tty3b... and so on. Then I did echo "hello can you read this tty3a" > /dev/tt3a to each terminal. I found the location of each terminal 3a, 3b, 3c and 3d. But the text would only partly show up. Only the first 10 chars or so. If I send the command again then the rest of the string that was missing from the first message would show up.

I have tried disabling all terminals then enabling the four that are needed and rebooting the server but the terminals still do not work.

If repeatedly enable and disable the terminals they will start to show the first part of the /etc/issue before the login. When the text shows on the terminals is seems fast. The baud rate is 9600. It just seems like there is a buffer that is locking up.

I cannot find any documentation that comes close to what this problem could be.

If anyone has had the horrible misfortune of working with SCO crap I am sorry for you but could you please give me your advice with this problem.



Roy Souther
www.SiliconTao.com


Changing the way people do business.


Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
clug-talk mailing list
[EMAIL PROTECTED]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca

Reply via email to