Re: [coLinux-users] Unresponsive keyboard/mouse on Vista

[Paolo M. <pao...@gm...>]

On Tue, May 6, 2008 at 9:10 PM, Henry Nestler <Hen...@ar...> wrote:
> Hello Mark,
>
> Mark Rodriguez wrote:
>> I've tried getting coLinux running (tried latest release, stable, and
>> dev. snapshot) on my Vista laptop, but it consistently freezes all
>> input devices (keyboard and mouse don't work). Even after I'm unable
>> to move my mouse or type on my keyboard, I can see the console
>> messages (both on NT and FLTK) continue until it reaches the login. At
>> this point, I'm unable to type 'root' or navigate my mouse for any
>> other operation. It appears the machine is still alive since I'm able
>> to use my "non standard" function keys to do things like turn on the
>> keyboard light or access Lenovo's "ThinkVantage" menu options.
>>
>> Thinking this might be related to the console specifically, I even
>> tried running as a service, but it behaves the same way. Seems like
>> starting coLinux on Vista hijacks my input devices. The same
>> configuration works fine under XP. Any ideas, tips, suggestions?
>
> I feel, you have the same promblem as Andreas.
> Please try some of my debugging tips from help forum:
> http://sourceforge.net/forum/message.php?msg_id=4948804
>
> At other coLinux users with running Vista: Exist any difference between
> your Vista versions? Build number, Professional/Home, Service Packs or
> what ever?
>
> Please ansewer here in the list, not in the forum.
>
> --
> Henry N.
>

Hello,
on my PC with Vista there is a small problem about CTRL-C
I run colinux-0.7.2 (with you fix, Henry :=) ) and console-nt.
Then I run the following command :

> hexdump /dev/cobd1

where cobd1 is connected to my physical CDROM.
There are a lot of data.
If I want to stop, I press CTRL-C.
Under XP all is OK, the console-nt pass the CTRL-C to linux and
hexdump stops almost immediately.

Under Vista CTRL-C doesn't stops the hexdump command.
To be more clear, in Vista CTRL-C is not always bad.
For example, if I compile a program with this command :

> gcc myexample.c

and I press CTRL-C during compilation, CTRL-C works OK and stops the compiler.
It seems that it depends on the amount of data that pass throught the
console-nt or someting similar.

For Mark:
I dont't have your problem of freezing input device ....
It seems that on Vista everyone has a different problem :=(

Henry, your fix is OK .... no more hangs after IPI Shortcut mode :=)

Bye,
Paolo