Hi Jerome,
there is no need to allocate a whole int 0x2b for just one driver.
There are mechanisms which already invite drivers to share them :-)
INT 2D - ALTERNATE MULTIPLEX INTERRUPT SPECIFICATION (AMIS) [v3.6]
AH = multiplex number
AL = function
00h installation check
01h get private entry point
02h uninstall
03h request popup
04h determine chained interrupts
05h get hotkey list
06h get device-driver information
07h-0Fh reserved for future enhancements
Return: AL = 00h (not implemented)
other application-dependent
other registers vary by function (also see individual entries
below)
You also are in good company there, for example screen thief uses it.
INT 2F - Multiplex - NOTES
AH = identifier of program which is to handle the interrupt
00h-3Fh reserved for IBM (for DOS)
40h-7Fh reserved for Microsoft (for DOS)
80h-B7h reserved for IBM
B8h-BFh reserved for networks
C0h-FFh reserved for applications
AL is the function code
This is a general mechanism for verifying the presence of a TSR and
communicating with it.
AMIS got introduced (by RBIL, sort of?) because so many apps use INT 2F,
but if you only need an install check, performance is no issue and you
can use INT 2F without problems.
You can also use INT 2F just for detection and then acquire a pointer
to a fast call provided by your driver if you need something quick.
Regards, Eric
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
