Changeset 618 in xtideuniversalbios for trunk/XTIDE_Universal_BIOS/Src/Handlers/Int13h.asm

Timestamp:

Aug 31, 2021, 2:17:47 PM (4 years ago)

Author:

Krister Nordvall

Message:

Changes:

• Updated the BIOS makefile. Added the NO_ATAID_CORRECTION define back to the Tiny build as I've realized that the correction code should not be needed for builds without MODULE_EBIOS. Also added a new makefile target 'custom' to make it easier for people to make custom builds.
• Fixed a bug where calling INT 13h/AH=15h for drives not handled by XUB (floppy drives for example) would return an error due to the fact that any non-zero return value in AH from the other BIOS would cause the CF to be set in Int13h_SetErrorCodeToIntpackInSSBPfromAH. The return path is now via Int13h_ReturnFromHandlerWithoutStoringErrorCode which means that no status/error code will be returned in the BDA but that should not be a problem as the other BIOS should do that anyway. This change also fixed another potential problem where return values in DL from the other BIOS were assumed to be drive numbers when MODULE_SERIAL_FLOPPY is included in the build.
• Minor optimizations and fixes.

File:

• trunk/XTIDE_Universal_BIOS/Src/Handlers/Int13h.asm (modified) (1 diff)

trunk/XTIDE_Universal_BIOS/Src/Handlers/Int13h.asm

@@ -250 +250 @@
     pop     WORD [RAMVARS.xlateVars+XLATEVARS.wFDandHDswap]
     cmp     dl, [RAMVARS.xlateVars+XLATEVARS.bXlatedDrv]    ; DL is still drive number?
-    je      SHORT Int13h_ReturnFromHandlerAfterStoringErrorCodeFromAH
+    je      SHORT Int13h_ReturnFromHandlerWithoutStoringErrorCode
     mov     [bp+IDEPACK.intpack+INTPACK.dl], dl ; Something is returned in DL
 %endif
-    jmp     SHORT Int13h_ReturnFromHandlerAfterStoringErrorCodeFromAH
+    jmp     SHORT Int13h_ReturnFromHandlerWithoutStoringErrorCode
+    ; We cannot return via Int13h_ReturnFromHandlerAfterStoringErrorCodeFromAH!
+    ; 1. If the other BIOS returns something in DL then that is assumed to be a drive number
+    ;    (if MODULE_SERIAL_FLOPPY is included) even though it could be anything.
+    ; 2. Any non-zero value in AH will cause the CF to be set on return from the handler.
+    ;    This breaks INT 13h/AH=15h for drives handled by the other BIOS.