> Try finding the kernel syscall number from the kernel source and then
> finding the syscall.dat file in the libc portion of the devkit. I had asked that
> Al include instructions for doing this with the 0.77 ELKS release, but I haven't
> looked at it yet.
I have to admit i didn't believe anything would really happen when i ran
microwin binary in elks .. but the thing actually works :-)))
My installation procedure (after reading all the comments on the list i
didnt want to mess with trial&error methods), i hope it is useful for
other people out there too:
- get newest elks kernel source (0.0.77) and the newest Dev86 package
- unpack kernel source, unpack Dev86 (in /usr/src for example), go to
/usr/src/linux-86/libc/syscall, rm syscall.dat
- ln -s /usr/src/elks/arch/i86/kernel/syscall.dat syscall.dat
- now you have flexible linux-86 package, just be sure to recompile libc
whenever new syscall is added to the kernel (= cd /usr/src/linux-86;
make, maybe make install after that)
- modify Makefile in mwin/server directory according to the instructions
in INSTALL file (Greg: IMO there should be another ifdef in that
makefile, at the line where graphics libs are defined, where comment
looking like "if LINUX ..." appears, shouldn't it ?), modify the other
three Makefiles mentioned there and finally modify demo.c to exclide
some demos
- make; cp microwin to your elks root image (i suggest using comb disk
image as it is already equipped with all the fancy tools and still has
plenty of room for user binaries and besides that allows easier kernel
image manipulation (copy your newly built Image from elks source tree to
/mnt/boot/linux where /mnt is the mountpoint where your floppy with comb
image is mounted)
- boot ELKS using that floppy, run microwin, enjoy, ask yourself why
doesn't author use some sort of XORmapping before doing real output to
the screen :)
Yeah Greg, why don't you use some sort of XORmap ? I understand it
consumes lots of memory but it would allow faster screen refresh (try
clicking on background window, do it once again and again and you'll
notice flicker when former background window gets redrawn layer by
layer). I guess you already use some memory for framebuffer so you could
do xormapping in that memory before outputting it to the screen.
bye, Ab
