Hi Ramiro,
The way I locate this kind of errors is th change "DUMPFILE",
now in vernr.h, to 1.
Then add statements xz("comment");
between code statement statements.
xz={fprintf(dmp,"%s\n",agr);fflush(dmp);sync();}
When the computer has rebooted, the last line in the file
dmp is the last xz statement encountered.
Then I would remove all xz before the last one
and insert more of them between the last one and
the next one that was not executed. Pretty soon
I know what statement that does not return.
My Debian Sarge 2.6.8 installation will be complete (perhaps)
in about 12 hours. I will try to reproduce the error you report,
but I do not think the chances are so good I can get this
error.
Maybe you could place some xz statements in your lmain.c
like this:
if(global_uiparms()==0)
{
lir_errcod=1197;
xz("goto exitmain");
goto exitmain;
}
xz("glob_uip OK");
.
.
}
vga_setmousesupport(1);
xz("mouse OK");
Verify that the mouse driver is specified correctly in libvga.config.
(You can check by trying mousetest)
Linrad-01.35 uses
mouse_init("/dev/mouse",vga_getmousetype(),MOUSE_DEFAULTSAMPLERATE);
mouse_setdefaulteventhandler();
while linrad-02.05 uses
vga_setmousesupport(1);
I do not know what the best way would be to find out where
the correct mouse driver is located. The 2.05 way is intended
to force users to get into the libvga.config file. I added
tools to allow some editing of libvga.config because that
seemed to be something needed to make the live CD easy to
use. Now with a Windows version I think it is time to
delete the 'libvga.config editor' and replace it with
some on-screen instructions about the need to use a
text editor on /etc/vga/libvga.config before proceeding.