Back to home page

DOS ain't dead

Forum index page

Log in | Register

Back to the forum
Board view  Mix view

In reply to : Bret 'll have to hate FreeDOS mKEYB, too (Developers)

posted by tom Homepage, Germany (West), 16.05.2011, 21:06

> > IMHO Bret is plain wrong with 'INT 15.4F handler is not allowed to
> > actually "process" any keystrokes or make any system changes at all (put
> > ASCII codes in the keyboard buffer, make changes to the BIOS Data Area,
> > etc.).'

>
> Let me explain to you where this "fantasy" of mine, that INT 15.4F can be
> called by any program at any time, came from.
>
> http://support.microsoft.com/kb/67929
>
this is clearly not "any" program, but a program that reboots the system in a SMARTDRV compatible way


> After seeing this, I see only three possible conclusions that you can
> make.
>

I'm not able to follow your logic.
> 1)
> Microsoft is wrong, and INT 15.4F cannot be called from anywhere except
> inside an INT 09 handler. You must find another way besides INT 15.4F to
> flush a SMARTDRV or SMARTDRV-compatible cache when rebooting from inside a
> program.
KB67929 describes a way to reboot the system in a SMARTDRV compatible way; no reason to doubt that.

MS is most likely right - it's great if you MAKE the standards.
>
> 2)
> Microsoft is right, but the ONLY exception to the INT 15.4F rule in
> conclusion 1 is Ctl-Alt-Del.
which INT 15.4F rule ?

> 3)
> (My conclusion) that by logical extension, INT 15.4F can be called by any
> program at any time for any scancode. INT 15.4F is only supposed to
> translate or monitor scancodes, not actually process
> them.

as already said: I'm not able to follow your reasoning; why exactly should
it not call INT 16.5 (besides common DOS/BIOS reentrancy problems)

 

Complete thread:

Back to the forum
Board view  Mix view
22049 Postings in 2034 Threads, 396 registered users, 188 users online (0 registered, 188 guests)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum