-
Couldn't load subscription status.
- Fork 17
How to build
640KB edited this page Sep 23, 2025
·
6 revisions
GLaBIOS can be built using MASM 5, MASM 6.1 or TASM.
See Build Options for descriptions of all available configuration options.
-
MASM GLABIOS;(note: add/Lto create the.LSTlisting file). -
LINK GLABIOS;Will create GLABIOS.EXE.
-
ML.EXE /I. /Zm /c GLABIOS.ASM(note: add/Flto create the.lstlisting file) -
LINK GLABIOS;Will create GLABIOS.EXE.
You may also specify CPU and ARCH types on the command line:
- MASM 5:
MASM /L /DCPU_TYPE="8" /DARCH_TYPE="T" GLABIOS; - MASM 6:
ML.EXE /I. /Fl /Zm /DCPU_TYPE='8' /DARCH_TYPE='T' /c GLABIOS.ASM
-
TASM GLABIOS.ASM(note: add/lor/lato create the.lstlisting file). -
LINK GLABIOS;Using DOSLINK.EXEis recommended.
- Run
GLA2ROM GLABIOS.EXE GLABIOS.ROM(included insrcfolder) to convert to an 8 KiB ROM file.
Alternate step 3:
- Convert EXE manually by removing the EXE header (the first 512 bytes of the EXE file) and extracting the last 8 KiB
- Calculate 8-bit checksum byte and insert into relative file offset
1FFFin GLABIOS.ROM. The low byte of sum of all bytes should equal0.
Due to differences between MASM 5 and MASM 6, the MACROs that ensure that fixed ORGs are not exceeded do not work correctly on MASM 6 and as a result it is possible to end up with a broken ROM build if certain build options are enabled together. If you are experimenting with build options, it's recommended to build with MASM 5 to ensure there is sufficient code space for that custom build type.