汇编项目中DB语法错误与AAH未定义符号问题求助

安全阿岳

2026-5-8

Fixing Your Assembly Boot Sector Errors

Let's walk through each of your three assembly errors step by step, with clear explanations and fixed code snippets:

1. Syntax Error on the Multi-String DB Line

The Problem

Your original code crams multiple DB directives into a single line without proper separation:

DB 13,10,"Non- system disk or disk error" DB 13,10,"Replace and press any key" DB 13,10,0

Most assemblers (like MASM/TASM) can't parse back-to-back DB keywords on the same line—they expect each directive to be on its own line, or multiple data items grouped under one DB separated by commas.

The Fix

Either split each DB onto its own line (more readable for boot sector code):

DB 13,10,"Non-system disk or disk error"
DB 13,10,"Replace and press any key"
DB 13,10,0

Or combine all data into a single DB directive (compact, but still valid):

DB 13,10,"Non-system disk or disk error",13,10,"Replace and press any key",13,10,0

2. Syntax Error in the IOSYS Block

The Problem

Your original line mixes multiple DB directives and an ORG directive all in one line, which breaks assembler parsing:

IOSYS: DB "IO SYS" DB "MSDOS SYS" DB 0 DB 0 ORG 7C00H + 01FEH DB 55H

Back-to-back DB keywords are invalid here, and ORG (which sets the assembly origin) must be a standalone line.

The Fix

Split each directive onto its own line for clarity and correctness:

IOSYS:
    DB "IO SYS"       ; Note: This is 6 characters (including the space)
    DB "MSDOS SYS"    ; This is 8 characters (including the space)
    DB 0
    DB 0
ORG 7C00H + 01FEH     ; Set origin to the boot sector's signature position
DB 55H

3. Undefined Symbol: AAH

The Problem

Your line DB AAH throws an undefined symbol error because many assemblers (especially MASM/TASM) treat hexadecimal values starting with a letter as symbols (like variable names) unless you prefix them with a 0. So AAH is interpreted as a variable named AAH instead of the hex value 0xAA.