Changeset 67 for trunk/bootcode/regular

Timestamp:

Oct 11, 2016, 10:42:09 PM (9 years ago)

Author:

Ben Rietbroek

Message:

Replaced some 'eCS' references with generic 'OS/2' [v1.1.1-testing]

With the upcoming ArcaOS, see: ​https://www.arcanoae.com, eComStation
ain't the only game in OS/2-town anymore. So, some references have been
changed to the more generic term 'OS/2' to prevent misinterpretation.

CAUTION:
This is a testbuild !
AirBoot uses the BIOS to access disks and a small coding error can trash
partition tables or other vital disk structures. You are advised to make
backups of TRACK0 and EBRs before using this testbuild. More info at:
​https://rousseaux.github.io/netlabs.air-boot/pdf/AirBoot-v1.1.0-manual.pdf

Location:

trunk/bootcode/regular

Files:

• driveio.asm (modified) (2 diffs)
• other.asm (modified) (1 diff)
• partmain.asm (modified) (12 diffs)
• videoio.asm (modified) (1 diff)

trunk/bootcode/regular/driveio.asm

@@ -1079 +1079 @@
 ; ------------------------------------------------------
 ; Load the master LVM-sector to get the number of sectors per track as
-; eCS views the drive. If no master LVM-sector is found it is assumed eCS
+; OS/2 views the drive. If no master LVM-sector is found it is assumed OS/2
 ; is not installed. The master LVM-sector can be located at three different
 ; places depending on drive size and partitioning scheme and driver used.
-; When DANIS506.ADD is used, the eCS extended geometry will be 255/127 for
+; When DANIS506.ADD is used, the OS/2 extended geometry will be 255/127 for
 ; drives >502GiB but <1TiB. Then the location will be sector 127 which
 ; is LBA 126 (7Eh).
-; IBM1S506.ADD will always use 255/255 for the extended eCS geometry.
+; IBM1S506.ADD will always use 255/255 for the extended OS/2 geometry.
 ; DANIS506.ADD will use 255/255 for drives >1TiB.
 ; Then the location of the master LVM-sector will be 255 which is LBA 254 (FEh).
-; When eCS is installed on a huge drive that alread had a system on it, eCS
+; When OS/2 is installed on a huge drive that alread had a system on it, OS/2
 ; will be confined to the lower 502GiB of the drive.
 ; In this case the normal geometry from Int13X will be used.
@@ -1207 +1207 @@
 
 ; ---------------------------------------------------
-; Rousseau ## Large drives, (eCS) geometry and LBA ##
+; Rousseau ## Large drives, (OS/2) geometry and LBA ##
 ; ---------------------------------------------------
 ; A sector size of 512 bytes is assumed in the below calculations.

trunk/bootcode/regular/other.asm

@@ -290 +290 @@
         call    MBR_Teletype
 
-        mov     si, offset eCS_InstallVolume
+        mov     si, offset OS2_InstallVolume
         mov     al, [si]
         test    al,al                                 ; See if phase 1 is active

trunk/bootcode/regular/partmain.asm

@@ -787 +787 @@
 PART_IsInstallVolume            Proc Near   Uses ax cx dx si di
         cld                                    ; Advance upwards with lodsb
-        mov   di, offset eCS_InstallVolume     ; Address of install-volume label (max. 11 chars)
+        mov   di, offset OS2_InstallVolume     ; Address of install-volume label (max. 11 chars)
 
         mov   cx, 11                           ; Maximum length of label
@@ -967 +967 @@
 ;~ HELEMAAL NAKIJKEN !
 ;~ DRIVELETTER ASIGNMENT CORRIGEREN
-;~ WORDT TOCH BOOTDRIVE IN BPB GEZET ALS NON eCS SYSTEEM BOOT ?
+;~ WORDT TOCH BOOTDRIVE IN BPB GEZET ALS NON-OS/2 SYSTEEM BOOT ?
 
 
@@ -1210 +1210 @@
 
 
-    ; --------------------------------------------------------- OS/2 / eCS I13X
+    ; --------------------------------------------------------------- OS/2 I13X
     ; Now check if the partition to get booted is above 8 GB.
     ;  If yes, set magic bytes 'I13X' at 3000:0 for boot-loader to recognize.
@@ -1735 +1735 @@
         ;
         ; FIXME: PBR Already loaded
-        
+
         ; When FAT12/FAT16/HPFS/JFS then boot-drive-letter can be tested
         ; or adjusted.
@@ -1875 +1875 @@
 
         ; See if the BPB boot-drive-letter is valid
-        ; This one is supposed not to change since eCS cannot be booted
+        ; This one is supposed not to change since OS/2 cannot be booted
         ; from another drive then it was installed on.
         test    ah,ah
@@ -1887 +1887 @@
         add     al,3dh
         mov     bx,[PhysDiskBpbIndex]
-        ; Advance to field for drive-letter in BIOS notation (OS/2 - eCS)
+        ; Advance to field for drive-letter in BIOS notation (OS/2)
         inc     bx
         ; Fix the boot-drive-letter field in the BPB
@@ -1901 +1901 @@
         ; Also, this field is the culprit of AiR-BOOT v1.07 not handling it
         ; correctly when the system uses HPFS and this byte is zero.
-        ; This mostly involved booting older eCS versions on HPFS.
+        ; This mostly involved booting older OS/2 versions on HPFS.
         ; See issues #3067 and #3119 on http://bugs.ecomstation.nl
         ;
@@ -1956 +1956 @@
     no_valid_boot_drive_letter_found:
         ; HERE SHOULD COME AN ERROR POP-UP ABOUT NO BOOT-DRIVE OR NO LVM-INFO.
-        ; WE CONTINUE BOOTING BUT OS/2 - eCS WILL MOST PROBABLY FAIL TO BOOT.
+        ; WE CONTINUE BOOTING BUT OS/2 WILL MOST PROBABLY FAIL TO BOOT.
 
         ; FIXME: Issue some kind of warning
-        
+
         ;mov     ah,07h
         ;mov     si,offset CheckID_MBR
@@ -2037 +2037 @@
         pop     si
 
-        
+
         ; BOOKMARK: Update the CRC of the Partition Boot Record.
         mov     bx, offset [PBRSector]
@@ -2043 +2043 @@
         call    DriveIO_SaveConfiguration
 
-        
+
         ; Setup the registers for the partition location.
         mov     ax, wptr [si+LocIPT_AbsoluteBegin+0]
@@ -2051 +2051 @@
         mov     dl, [si+LocIPT_Drive]
 
-        
+
         ; BOOKMARK: Write the adjusted HPFS/JFS PBR to disk.
         mov     si, offset [PBRSector]
@@ -2095 +2095 @@
 
 
-    
+
 
         ;

trunk/bootcode/regular/videoio.asm

@@ -949 +949 @@
 ;AutoStartPart     db "Auto Start Partition : ",0
 
-Phase1            db "eCS Install Phase 1  : ",0
+Phase1            db "OS/2 Install Phase 1 : ",0