|
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| UNIX for Dummies Questions & Answers If you're not sure where to post a UNIX or Linux question, post it here. All UNIX and Linux newbies welcome !! |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| strange behavior of find with xargs | jerardfjay | Shell Programming and Scripting | 9 | 08-09-2007 09:06 AM |
| Very Strange Behavior for redirection | cahook | Shell Programming and Scripting | 5 | 08-08-2007 12:32 PM |
| Strange Real Memory usage behavior | Skyybugg | AIX | 5 | 05-31-2007 11:17 AM |
| Strange behavior from 'read' statements. (ksh - but could be same on other shells) | alexop | Shell Programming and Scripting | 5 | 05-02-2006 12:14 PM |
| strange sed behavior | Kevin Pryke | UNIX for Dummies Questions & Answers | 5 | 06-13-2003 05:34 AM |
 |
Powered by 
|
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
08-02-2006
|
||||
|
||||
|
Strange Behavior on COM2
Hi,
I have a problem with a new touch screen controller that I am trying to use on a SCO 3.0 system. THe touch screen controller only wants to talk at 9600baud. I have updated /etc/inittab per the manual and also edited /usr/lib/event/devices to use 9600 baud. The only way I can get the touchscreen to communicate is to plug a serial mouse into the COM2 port, then replace it with the touchscreen cable. The problem is, every time I reboot, the touch screen quits working. It is almost as if the mouse is forcing the COM port to 9600 baud, but the touch screen controller itself won't do that. How is SCO configuring the port differently based on whether a mouse is plugged in or the touch screen controller? Any advice would be appreciated, Thanks, |
|
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
Hybrid Mode
