On 21 May 2000, Tijs van Bakel wrote:
> Jay <[EMAIL PROTECTED]> writes:
> > ..
> > My problem is this: when I exit ggisnes9x, I get funny chars on
> > any keys I press (or release). The only thing I can do is reboot (by the
> > reset button, ctrl+alt+del just gives funny chars)
> > ..
>
> Enable the Alt+SysRq option in the kernel config. By pressing
> Alt+SysRq+R simultaneously, the keyboard will switch back to a useful
> state. If programs lock up, you can use other keycombinations to kill
> the current process, and there are some other useful options. See
> /usr/src/linux/Documentation/sysrq.txt for more information.
>
> Also, you may want to try the latest svgalib (1.9.4,
> http://www.svgalib.org/) -- that saved me quite some trouble, although
> it might introduce new bugs for you :) The best thing about this
> version is that you don't have to be root in order to use svgalib,
> since it uses a /dev/svga helper device which does all the outb()'ing.
>
> oh btw - can't libggi be ``released'' or so? :)
We are working on it. What's left, anyway? Do we have a master
to-do list somewhere? The only things I've seen that would be on such a
list are:
* Weird behavior from the fbdev/glide targets and input devices. Lots of
times it seems like people have problems getting mouse events when using
the fbdev or glide targets, at least without twiddling config files or
setting environment variables. Do we know what the problem is?
* We use SIGUNUSED to signal VT switch handling if it is available. I
have found at least one application which also uses SIGUNUSED, and the
combination is nasty. Is there any other signal we can use for VT
switching?
* Scrofulous old KGI target. No one uses this anymore, they use the
kgicon helper with the fbdev target. This should go. Can I delete it and
its configure.in code? We'll re-add a proper KGI-0.9 (or 1.0 hopefully)
API target later when the API is ready.
* Spurious S3 Virge driver reference in the fbdev.conf file. I just
killed it.
* Ping-pong buffer code in the kgicon helper. I just killed that too.
I'd like to redo in in a much simpler fashion based on execution of static
kgicommand buffers when flushed, but I don't have the time. Better we get
a stable LibGGI release out now. We can (and probably will) put out a .1
or .01 release later on with updated target code.
* Do we care about KGIcon at all for this release, or only LibGGI, LibGII
and LibGG?
* Does the suidkgi target work? Does suidkgi still work? Maybe we should
kill it too.
* Same for the AAlib target. I think AAlib has been updated recently, and
I recall the mode negation in the target code to be pretty broken when I
last looked at it over a year ago.
* Does the VR demo still work?
* Do we want those timer inputlibs for LibGII we were discussing earlier?
> it seems to me that a
> lot of people are losing interest lately.
Oh no, far from it actually. There's plenty of stuff going on:
* We have a new stable release approaching (crosses fingers)
* We finally got a commercial game on board (Jagged Alliance II)
* Berlin is really shaping up which is exercising LibGGI
* My LibXMI work is progressing nicely
* KGI-0.9 is in Sourceforge and work continues although slowly
* Andrew's GFFD library
And there's other stuff I can't talk about, too. Trust me, GGI is
alive and kicking.
Jon "it's kicking me pretty hard right now actually" Taylor
---
'Cloning and the reprogramming of DNA is the first serious step in
becoming one with God.'
- Scientist G. Richard Seed
