Mail Archives: djgpp/1996/12/01/19:38:07
Glen Miner wrote:
>
> It has come to my attention that a program that I've made in and for dos
> is being used in Win95. <shrug> I suppose that this shouldn't suprise me,
> and for the most part I don't care. I have absolutely no ambitions to
> make it win native in ANY way.
>
> However, there have been confirmed allegations that my program fails to
> correctly redraw the screen when it is placed in the background and then
> brought to the foreground again.
>
> Is there any way for me to detect this? Does win95 raise any kind of
> "refresh" signal that I can detect? I don't really want to do a
> "video-memory" sanity poll; that would really suck.
>
This is gleened from Ralf Brown's iterrutp list:
--------W-2F4005-----------------------------
INT 2F C - Windows 3.x - SWITCHING DOS TO BACKGROUND
AX = 4005h
Note: called by Windows when the DOS box is about to be placed in the
background and the video driver should save any necessary
state
information (this may be called only in Standard mode)
SeeAlso: AX=4001h,AX=4006h
t--------W-2F4006-----------------------------
INT 2F C - Windows 3.x - SWITCHING DOS TO FOREGROUND
AX = 4006h
Note: called by Windows when the DOS box is about to be placed in the
foreground and the video driver should restore any necessary
state
information (this may be called only in Standard mode)
SeeAlso: AX=4002h,AX=4005h
I haven't tried these out, but I imagine all you have to do is hook the
int 2f interrupt. Hooking the rm int should work if hooking the pm int
doesn't
Bill
--
Leave others their otherness.
- Raw text -