From: Leif Newsgroups: comp.os.msdos.djgpp Subject: Re: RHIDE and screen swapping Date: Sun, 27 Sep 1998 23:16:48 -0700 Organization: NorthWest Nexus Inc. Lines: 73 Message-ID: <360F29D0.51B4@hotmail.com> References: <36028837 DOT 2006937 AT crispin> NNTP-Posting-Host: blv-pm101-ip12.halcyon.com Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk Ignacio García Pérez wrote: > > Hi, > > I'm experiencing some screen problems that I'll describe, just in case > someone can provide useful tips: > > I program using RHIDE, DJGPP and Allegro, in a DOS box under Windows > 95. At this point I can't help saying that these three are some of the > best pieces of software I've ever dealed with. > > - Problem 1 (minor): when I debug a program which has switched to > graphics mode (currently 640x480x256), each time I display the program > output after having been in the RHIDE text mode, I can see some > undesired points and lines. I know these are caused by the text > written while in text mode, which overwrites video memory which is > also used in graphics mode. > > I can live with this minor interference, but wouldn't it be enough > saving the whole text mode video memory when going back to RHIDE and > restoring it before continuing the program execution ?... (I know > actually RHIDE saves and restores the video status, but doesn't do the > same with video memory probably because it would take too much > storage, and is dependant on video mode, but text mode is much > simpler). > > - Problem 2 (catastrophic): if I run a program that used 640x480x256, > after exit, everything works fine, I mean Windows 95. But when, while > in RHIDE, I stop execution, or step a program in graphics mode, this > is, going from the program screen to RHIDE intergated debugger back > and forth, Windows blows away the next time I go back to the Windows > GUI. > > This happens even if I finalize RHIDE, and being back in the DOS > prompt, close it with EXIT of simply switch to another application. > > The latest is very annoying, because though I hate it, I must work > with W95, and don't want to restart the computer in plain DOS each > time I want to program/debug a RHIDE/DJGPP/Allegro program. > > And yes, I've tried -G 2 with RHIDE. > > As I said before, ANY useful tips will be very welcome. > > Regards. Nacho. Hey, I know what yer talking about. I dont know how to fix those problems but, I can tell you how I get around em.... When running/debugging a program under RHide make sure U window RHide before selecting RUN within RHIDE. What I mean is, Hit ALT+ENTER to make it so U see yer RHide window AND Win95 in the background, THEN select RUN in RHide. Maybe someone can tell us how to FIX them problems instead of using sneaky ways to get around the problems?? Any takers? If so, heres another problem Im sure is related... When I am running RHide AND it is FULLSCREEN(ie. U cant see no Win95 junk) and I select "DOS Shell" the screen remains Completly the same,(ie. U can still see the RHide environment) but I am in the DOS Shell, I can do commands and all that junk but the initial DOS Prompt "C:>" doesnt pop up and the background color is the same as RHide. BUT, none of this happens when I select "DOS Shell" while RHide is windowed(ie. RHide is in a window and U can see the Win95 junk in the background). In the latter case, everything works fine. Also, to clarify the problem about running a graphics program while in RHide.... I select "RUN" while RHide is fullscreened, it works fine and exits and im back in RHide. No biggie. But.. try to step through the program or EXIT RHide and CRASH!!! My display gets all screwed up and I must restart windows.... Well thats my 2cents worth. Any ideas on how to FIX those problems would be great. :)