Return to model386.equ CVS log

Up to [Witchaven II] / gcl520h

Annotation of gcl520h/model386.equ, revision 1.1

1.1     ! root        1: ;
        !             2: ; MODEL386.EQU      5.20A  June 8, 1995
        !             3: ;
        !             4: ; DESCRIPTION
        !             5: ;
        !             6: ; This is the header file used by assembly files to determine
        !             7: ; model dependent information for 32 bit assembly code.  Note that
        !             8: ; the segments are idiosyncratic to 32 bit flat model as supported
        !             9: ; by our various DOS Extenders.
        !            10: ;
        !            11: ; MODIFICATIONS
        !            12: ;
        !            13: ;  December 1, 1994   5.10A :  Initial release.
        !            14: ;
        !            15:                              .386
        !            16:                              .MODEL  SMALL,C
        !            17: ;
        !            18: ; The code segments are lined up in this order for a reason, don't
        !            19: ; change them around.
        !            20: ;
        !            21: REAL_RELOCATED_16            SEGMENT DWORD PUBLIC USE32 'CODE'
        !            22: REAL_RELOCATED_16            ENDS
        !            23: ;
        !            24: ; The new segment scheme dictates that everything in the
        !            25: ; ISR goes into PISRCODE.  PISR_START and PISR_END are
        !            26: ; just little marker segments.
        !            27: ;
        !            28: ;
        !            29: 
        !            30: PISR_START                   SEGMENT BYTE PUBLIC USE32 'CODE'
        !            31: PISR_START                   ENDS
        !            32: PISRCODE                     SEGMENT BYTE PUBLIC USE32 'CODE'
        !            33: PISRCODE                     ENDS
        !            34: PISR_END                     SEGMENT BYTE PUBLIC USE32 'CODE'
        !            35: PISR_END                     ENDS
        !            36: ;
        !            37: ; I'm going to eliminate these and go to a new system
        !            38: ;
        !            39: ;KILLCODE                     SEGMENT BYTE PUBLIC USE32 'CODE'
        !            40: ;KILLCODE                     ENDS
        !            41: ;DEBUGCODE                    SEGMENT BYTE PUBLIC USE32 'CODE'
        !            42: ;DEBUGCODE                    ENDS
        !            43: 
        !            44: PISRDATA                     SEGMENT DWORD PUBLIC USE32 'DATA'
        !            45: PISRDATA                     ENDS
        !            46: ;
        !            47: ; I'm not sure if this DGROUP definition is necessary
        !            48: ;
        !            49: ; I think i need the cgroup definition so that I can do near
        !            50: ; jumps to asi_kill_time
        !            51: 
        !            52: ;CGROUP                       GROUP REAL_RELOCATED_16,PISRCODE,KILLCODE,DEBUGCODE,_TEXT
        !            53: ;
        !            54: ; It turns out that I am really screwed under Watcom + DOS/4G if I use this
        !            55: ; group definition.  If I can't build my masm without it, I need to
        !            56: ; add _TEXT and BEGTEXT to the definition.  I am worried about what would happen
        !            57: ; then if I added yet another group.
        !            58: ;
        !            59: ; This works, but I don't like it
        !            60: ;
        !            61: ;BEGTEXT                      SEGMENT BYTE PUBLIC USE32 'CODE'
        !            62: ;BEGTEXT                      ENDS
        !            63: ;CGROUP                       GROUP REAL_RELOCATED_16,PISRCODE,KILLCODE,DEBUGCODE,_TEXT,BEGTEXT
        !            64: 
        !            65: DGROUP                       GROUP _DATA, PISRDATA
        !            66: 

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.