[LispM-Hackers] Keyboard problem

[John Leuner]

> Thinking out loud, I figure I've got three options:
> 
> (1) Figure out how to get GDB cross-debugging working between the two
> PCs.  Switch to the most appropriate graphics mode possible using the
> BIOS before protected mode.  Use GDB for debugging.  (I think I'd have
> to either port or write a special stub -- I've done this before in a
> past life -- about 20 years ago -- for a different debugger for an
> embedded system, and it was a pain in the ass.)
> 
> (2) Implement the v86 mode, and use that to write debugging info to a
> virtual screen.  Implement a "magic" keystroke to switch graphics
> modes (and foci) from emulated Explorer to microcode console.
> 
> (3) Live without debugger, and without ASCII debugging printouts.
> Either: (a) do some stupid stunt like writing color-coded pixels to
> the extra "border" in 1280x1024 mode to give me some clue as to what
> the microcode THINKS it's doing (kind of like blinking LEDs in POST or
> using Morse code); or (b) figure out how to write ASCII text to that
> border using SVGA fonts or something like that.
> 
> Any other ideas?

Write to serial port attached to something (another computer, or some other output device)?

John Leuner