Hi,

I've got some new information.

First of all, the cmap program you sent works.

I tried some different resolutions and on all I tried (including 1280x1024)
the  problem with the moving of wrong columns when inserting chars is
there.

Regarding the 804x600 resolution, I faked the console code to think
the resolution ix 800x600 and then the display is garbled. So it seems
to really be a 804x600 resolution.

On all resolutions the X display is garbled, not only on 804x600.
But that's another problem.

I found that on the higher resolutions the console only uses part
of the screen (80x34) where it could have much bigger character
resolutions.

I made the following chage in sys/dev/pci/tga.c:
--------------------
--- tga.c       2000/06/30 00:01:22     1.28
+++ tga.c       2000/08/26 22:06:00
@@ -320,7 +320,8 @@
        }
        dc->dc_rinfo.ri_wsfcookie = cookie;

-       rasops_init(rip, 34, 80);
+       rasops_init(rip, dc->dc_ht / rip->ri_font->fontheight,
+                    dc->dc_wid / rip->ri_font->fontwidth);

        /* add our accelerated functions */
        /* XXX shouldn't have to do this; rasops should leave non-NULL
--------------------

Then the whole screen is used. Is there a reason that the console
size was hardcoded to 80x34?

So my main problem is still when inserting chars at the
beginning/middle of a command line with bash.
Funny as it is, the same problem doesn't happen when I
insert chars in a line with vi.

regards,
chris