tonyw wrote:
@alfkil

It's almost certainly happening because you are using up all the available graphics memory with the big window and the system is having to swap graphics content in and out of RAM.

If I'm right, there is no cure other than to reduce your requirements (smaller screen, reduced resolution, etc).

jaokim wrote:
I have a small ARexx-script that adds my menus:

[...]

I then run this at the end of my startup-sequence.

The biggest challenge, however, would be porting the various native parts of the runtime libraries. GUI toolkits etc.

It depends a lot what your goals are. If you "just" want Mono on X1000, that's a *lot* easier than getting something complete enough to run most C# apps.

I'm not entirely sure what you mean by most c# applications though, because c# is also compiled using Microsoft Visual C#.

thomas wrote:
@nbache

What happens if you do

nbytes = IDOS->Read(fd[0], readbuffer, 1);

?

abalaban wrote:
@nbache

Strange indeed, to finalize the test can you change the line

nbytes = IDOS->Read(fd[0], readbuffer, sizeof(readbuffer));

to

nbytes = IDOS->Read(fd[0], readbuffer, 32);

and see if it change something ?

Mrodfr wrote:
@328gts

I have never known the double mouse button pressed for booting with no startup-sequence........

Another keys shortcut or bouttons pressed during the boot, for special things ?????

JCC wrote:
@nbache

Cool, how did I miss that?

Antique wrote:
Also seems to only have sources for X86. That means xtra work.

freddix wrote:
@nbache
What do you mean with "insane rules of ownership" ?

[...] vous nous accordez une licence non-exclusive, transf?rable, sous-licenciable, sans redevance et mondiale pour l'utilisation des contenus de propri?t? intellectuelle que vous publiez sur Facebook ou en relation ? Facebook (? licence de propri?t? intellectuelle ?). [...]