On Wed, 21 Jul 1999, David Coder wrote:
> I don't believe your mouse is on the first com port. If it were, the output
> of "moused -i all -p /dev/cuaa0" would be "device busy." The message you got
> is generated when there is nothing on the device at all. Check whether it
> isn't on the second
I don't believe your mouse is on the first com port. If it were, the output
of "moused -i all -p /dev/cuaa0" would be "device busy." The message you got
is generated when there is nothing on the device at all. Check whether it
isn't on the second com port.
dc
_
David Coder
>> Ok, the problem seems to be with the mouse, rather than the serial
>> port.
>>
>> Give me some more details about your serial mouse.
>>
>> What model from which manufacuture is it?
>>
>> I suspect it's rather an old model, because moused should be able to
>> detemine the protocol type if it
> Ok, the problem seems to be with the mouse, rather than the serial
> port.
>
> Give me some more details about your serial mouse.
>
> What model from which manufacuture is it?
>
> I suspect it's rather an old model, because moused should be able to
> detemine the protocol type if it is one of
>I posted the other day about sio problems and
>it seems that I'm still having trouble. Below
>is various output for sio (cuaa0). I'm trying to
>get the darn mouse to work ( to get X up and be done
>with it!) but I'm running into problems. For one,
>I can't seem to debug this problem so if AN
I posted the other day about sio problems and
it seems that I'm still having trouble. Below
is various output for sio (cuaa0). I'm trying to
get the darn mouse to work ( to get X up and be done
with it!) but I'm running into problems. For one,
I can't seem to debug this problem so if ANYONE k
