Mail Archives: djgpp/1997/01/27/13:57:06
Shawn Hargreaves wrote:
>
> Wow! A big round of applause to all concerned - this is *excellent*.
Thanks.
> problem - people can use VESA 1.x when debugging :-) but even in the
> standard VESA modes the display didn't always seem to be restored
> correctly. It works ok the first time the debugger switches back to it,
> but on subsequent switches (eg. when single-stepping through a function)
> I somehow ended up in text mode. Any ideas why?
Oh well, I'm not the only person with that problem. OK here the
description:
As standard RHIDE uses the routines from SET for display swapping. He
said
me, that it is enough to call "Restore VESA mode" and it is not needed
to set
explicit the mode. For me (and for you) there is a problem. The mode is
correct restored the first time but when RHIDE after this tries to save
the screen it asks the bios for the current mode and it reports now
0x03!!!
So RHIDE saves now a text mode and restores it the next time.
So there are now two suggestions from me:
1) Run RHIDE (or RHGDB) with the '-G 1' switch (uses my routines) and
see
if that helps.
2) Get the RHIDE sources and change the define of tvision/sescreen.cc
from
'-D_FORCE_SET_VIDEO_MODE' to '-DFORCE_SET_VIDEO_MODE' (in the makefile
or the project file) and rebuild RHIDE or RHGDB.
> Also, many thanks for including the standalone rhgdb program. I've never
Oh good. You are the first who says something about RHGDB. I thought
already
about removing RHGDB from the binary distrib, because nobody said
something
about it.
Robert
--
*****************************************************************
* Robert Hoehne, Fakultaet fuer Mathematik, TU-Chemnitz-Zwickau *
* Post: Am Berg 3, D-09573 Dittmannsdorf *
* e-Mail: Robert DOT Hoehne AT Mathematik DOT TU-Chemnitz DOT DE *
* WWW: http://www.tu-chemnitz.de/~rho *
*****************************************************************
- Raw text -