Nuno Lucas wrote:
> Hi all,
> I have been toying around with the latest snapshot (21/5), mainly trying to compile the console-nt with VS .NET 2003.
> Well, I did it, and all is well except I can't get the keyboard to work (it accepts the Win+Alt combination, at least).
> My guess is that some of the changes I had to make broke the message passing code (I had to hack the messages structures because msvc doesn't accept zero lenght arrays in structs -- at least not in all situations).
> I would like to know if someone has any hints or tips about this, as the code is not the best documented one and explicit I've seen ;)
> I would also like to know if there is any future on this. From what I see, the linux kernel driver is what decides what messages to pass, no «standard» here, so it may be that even if I can fix all the oustanding problems on the console, a later version will just throw away my code (I recall some writings about the framebuffer, wich could lead to another kernel driver being made).
> I have no experience with linux or linux kernel programming, thats why I am trying to concentrate on the windows part.
> As this is my first post, I just wanted to add that I am still impressed with the CoLinux idea and congratulate everyone involved in the project. The advantages of CoLinux over all other similar projects are amazing!!!
> I know have a gentoo box, running xfce 4 with vnc at a very good speed, and samba, apache, mysql, unixODBC and even wine working great and with only 64MB allocated to coLinux!!!
> Best regards,
> ~Nuno Lucas
Can you make a special build of console-nt for me?
I think can be cool to redirect to stdout and from stdin, because this
way can be posible to use netcat to force console-net to work has a
"network server", so shell to console-net from remote computers.
Other use of this quick hack can be to log whatever is printed to
console-net, to add a filter to the structure, etc..
I suggest "pipe-nt" to this littel console-nt hacked build.