Very Computer

Hello, I was using DIP on my Linux machine and when I was done,
I issued a "dip -k" command to kill the dip process.  This
worked, but now Linux thinks /dev/cua1 is busy and won't let
me start DIP again.  The problem is still there even after I
cycle power.  Anyone know how to fix this?  Thanks.

-Bryon Nordquist

There's a file in there that locks the port you're using, to keep other
processes from using it and messing up the original process.  Killing dip
doesn't remove the file.  I forget the file name and path, but I know I've
started up Linux Kermit and it'll automatically remove the lock if the port
is inactive (it mentions the filename and path, I think).  Other, similar
programs that access that same port may do the same thing, like minicom.
I'm not at my Linux box at the moment, and I'd have to go look and see
what exact file it is that is altered.

James Daniel