Mail Archives: djgpp/1996/06/16/18:09:08
machek AT atrey DOT karlin DOT mff DOT cuni DOT cz (Pavel Machek) wrote:
>: > > I have a keyboard interrupt in my game. Under DOS, you cannot reboot the
>: > > system or anything. The controler take total control of the keyboard
>: > > like it is supposed to. But with win95, If I hit the START button, or
>: > > Cntr-Alt-Del, windows takes over. How can one stop this?
>: >
>: > Basically you can't. What you are getting under win95 is not a direct
>: > hardware interrupt: it is a virtualised interrupt which the OS has
>: > already looked at and decided to pass on to your app. Some keys it keeps
>: > for itself, and so your program never sees the interrupt.
>Well. You can. But you would have to write some windows-specific code in
>386 assembly, which would become part of windows and pass these interrupts
>to you. Not worth writing, in my opinion.
Hitting the START button (the new Win95 key that sits between the left CTRL
and ALT keys) is very easy to do. If you haven't seen this it effectively
moves your application to the background and brings up the START menu in
Win95.
The *big* problem is that if you're in an SVGA mode switcing back to your
application is not likely to work. Certainly, this crashes my applications
outright.
This is important if you're writing an app (as I am) that you want to say
works under lots of OSs including Win95.
I personnaly don't have the skills to attempt the solution suggested above. If
anyone has a simpler solution or is inclined to implement the above then
*please* share it.
(Personally, I think that the Win95 developers made an oversight when
ommitting the START key from the PIF editor)
Jason.
- Raw text -