-=> Quoting Sylvain Lauzon to Peter Louwen <=-
 SL> @MSGID: 1:242/100 58bbe40a
 > INT 2F U - DOS 3.2+ - SET DISK INTERRUPT HANDLER
 >         AH = 13h
 >         DS:DX -> interrupt handler disk driver calls on
 > read/write
 >         ES:BX = address to restore INT 13 to on system halt
 SL> I might have overlooked the documentation. Thanks for pointing me
 SL> this one But my main idea was to scan whole INT 2F for a free hole.
 SL> So, isn't a good thing. It is standard if i scan C0h-FFh for a free
 SL> hole? Or do i need to jump over some reserved functions?
From Ralf's list:
INT 2F - Multiplex - NOTES
        AH = identifier of program which is to handle the interrupt
           00h-7Fh reserved for DOS
           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.  When searching for a free identifier code for AH
   using the installation check (AL=00h), the calling program should set
   BX/CX/DX to 0000h and must not depend on any registers other than CS:IP
   and SS:SP to be valid on return, since numerous programs now use 
dditional
   registers on input and/or output for the installation check.
Notes:  Since the multiplex chain is growing so long, and beginning to
          experience multiplex number collisions, I am proposing an alternate
          multiplex interrupt on INT 2D.  If you decide to use the alternate
          multiplex, please let me know.
        DOS and some other programs return values in the flags register, so
          any TSR which chains by calling the previous handler rather than
          jumping to it should ensure that the returned flags are preserved
          and passed back to the original caller
Peter
... Make way!, Make way!, A PROGRAMMER HAS ARRIVED!!
--- GEcho 1.11+
---------------