Ignore:
Timestamp:
Apr 11, 2014, 8:39:07 PM (11 years ago)
Author:
Ben Rietbroek
Message:

Reworked Build Environment [2012-02-15]

WARNING!!

All commits upto and including the commit of [2012-05-13] contain
a severe bug!! Building from these sources and then disabling
the 'force LBA' feature while also using the drive-letter feature or
editing the label can DESTROY THE MBR on ALL ATTACHED DISKS!!
DO NOT DISABLE 'FORCE LBA USAGE' WHEN BUILT FROM THE THESE COMMITS!!

Changes

o Reworked build environment
o Start made with coding FIXCODE in C
o Moved MBR protection image
o New overlap macro
o Protect type 0x35 from edit (user popup)
o Protect type 0x35 from adding to menu (user popup)
o More...
! No LVM Label change yet

Note

o Changed license to GPL v3

See file COPYING in trunk.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/BOOTCODE/MBR-PROT/MBR_PROT.ASM

    r30 r37  
    1919;                         AiR-BOOT SETUP / GENERIC & GENERAL SETUP ROUTINES
    2020;---------------------------------------------------------------------------
     21                ;
     22                ; First define processor so when a model is specified
     23                ; the correct default segments are created.
     24                ;
     25                .286
     26                ;.model large,c
    2127
     28;_TEXT           SEGMENT     USE16   PUBLIC  'CODE'
     29;_TEXT           ENDS
     30
     31MBRPROT         GROUP       CODE_SEG
     32;DGROUP          GROUP       CODE_SEG
     33
     34CODE_SEG        SEGMENT     USE16   PUBLIC  'CODE'
     35
     36                ;assume cs:MBRPROT, ds:MBRPROT, es:nothing, ss:nothing
     37                assume cs:MBRPROT, ds:MBRPROT, es:nothing, ss:nothing
     38
     39                org 0000h
    2240                .386p
    23                 .model large, basic
    24 
    25 code_seg        segment public use16
    26                 assume cs:code_seg, ds:nothing, es:nothing, ss:nothing
    27                 org 0000h
    2841
    2942; Yes you are :-)
     
    114127    jmp     WindowsProcessing
    115128
    116 MBRProt_WriteLine              Proc Near
     129MBRProt_WriteLine              Proc Near    Uses ax bx cx dx
    117130    add     di, 26
    118131    mov     ah, 4Ch                      ; red/brightred
     
    148161MBRProt_WriteBorderLine        EndP
    149162
    150 MBRP_Line1:     db      'ÕÍÍŽ!ATTENTION! -> A V1RU5 WAS FOUND <- !ATTENTION!ÃÍÍž'
    151 MBRP_EmptyLine: db      '³                                                     ³'
     163MBRP_Line1      db      'ÕÍÍŽ!ATTENTION! -> A V1RU5 WAS FOUND <- !ATTENTION!ÃÍÍž'
     164MBRP_EmptyLine  db      '³                                                     ³'
    152165                db      '³ A program tried to write to your Master Boot Record ³'
    153166                db      '³     AiR-BOOT supposes this as a viral act, so it    ³'
    154167                db      '³        intercepted it and crashed the system.       ³'
    155 MBRP_Line2:     db      '³ If you tried to install a OS or something like that ³'
     168MBRP_Line2      db      '³ If you tried to install a OS or something like that ³'
    156169                db      '³  you have to deactivate MBR PROTECTION in AiR-BOOT  ³'
    157170                db      '³             or contact your supervisor.             ³'
    158 ;MBRP_Line3:     db      'ÔÍÍÍŽAiR-BOOT (c) Copyright by M. Kiewitz 1999-2009ÃÍÍŸ'
    159 MBRP_Line3:     db      'ÔÍÍÍŽAiR-BOOT (c) Copyright by M. Kiewitz 1999-2011ÃÍÍŸ'
     171;MBRP_Line3      db      'ÔÍÍÍŽAiR-BOOT (c) Copyright by M. Kiewitz 1999-2009ÃÍÍŸ'
     172MBRP_Line3      db      'ÔÍÍÍŽAiR-BOOT (c) Copyright by M. Kiewitz 1999-2012ÃÍÍŸ'
    160173
    161174org             1023
    162175                db 0
    163176
    164 code_seg        EndS
     177CODE_SEG        ENDS
    165178                end
Note: See TracChangeset for help on using the changeset viewer.