Mail Archives: djgpp/1997/12/18/15:15:38
Hi!
I just wrote one article(yesterday) but it
is no longer here, so again:
I got a strange problem concerning interrupts.
First I got strange problems when i set the graphic mode, a lot of trash
that I wasn't able to erase was on screen, actually over the graphics
that I drew. I thought of hardware problems as I could put a bitmap on
screen, almost not see it because there was a lot of strange graphic
trash covering it, but then get it back 100% right with a get_bitmap.
The only workaround I could find was to, in the main loop, reinstall
graphics(setmode) when i hit the "q" button. That works always, I can
even 'reinstall' the graphics as many times I want without getting any
problems.
So, now the funny part, in my main, I call init_graphics to set
variables etc. and put the screen in gr-mode, then I call init_mouse to
initialize the mouse(both functions use __dpmi_int(... ) and when I one
day changed so the prog is calling init_mouse before init_graph the
graphics work perfect but the mouse got problems!
Actually, the mouse doesn't get initialized(I get no errors from the
interrut) the first(and only the first) time I run the program after a
cold-boot.
I'm writing the program under win95 and it runs in a dosbox.
I dont have a slightest idea of why the first interruptcall doesn't
work, have I forgot some strange codeslines in the beginning of my
program?
Oh, BTW, the graphic problem tended to be worse when i doubleclicked on
the short-cut to the .exe and not the .exe itself.
Please help me with this wierd problem!
Ludvig
please send e copy to <ludvig AT club-internet DOT fr>
- Raw text -