On Tue, 14 Dec 1999, Peter Howell wrote about, Comm port conflict?:
> With a littel tinkering, I was bale to get a legacy win31 program to
> work on my Caldera Openlinux 2.3 system. I was even able to get it to
> communicate with ttyS1. Well, now it has suddennly stopped working. The
> program tells me that it is unable to access com 2, and wine gives the error
> message:
>
> err:comm:OpenComm16: error=16
>
> I haven't been able to find mention of this in the documentation. Does anyone
> know what this means and how to fix it?
Whichever program that used the commport left a "LCK" file in /var/lock or
possably some other directory where your system writes "lock" files.
Try;
ls -al /var/lock/*
If you see something like;
-rw-rw-rw- 1 root root 11 Dec 13 18:17 LCK..ttyS1
Then do;
rm /dev/lock/LCK.ttyS1
This happens a lot when programs just dye and dont exit properly.
> Thanks
>
> Peter
--
Regards Richard
[EMAIL PROTECTED]
http://people.zeelandnet.nl/pa3gcu/
Merry Xmas.
