Видео

I prever to have brackets [num] for instruction with a memory access.

Good work. Please use brackets for instructions with a memory location like [num]. That would be prevent to confuse num as a contant like num equ 5. Imagine you have many instruction and you can’t see the data segment. The brackets make it clear, if all other without [ ] are used as immediate operands and not as an offset address. Thx.

Input string: mov bx, 0 ; file handle keyboard mov cx, 4 ; input 4 bytes mov dx, oftset BUFFER ; ds:dx mov ah,3Fh ; read from file or device int 21h ; read cx bytes from keyboard or less if return key pressed

nice serie of video

Good work.

I prefer to speak hexadecimal values digit by digit and not like decimal values, because the hexadecimal number system is not based on ten. Else we have for hex ACDB = A-thousend C-hundred D-ty B and this sounds not good. So hex 21 is not twenty one, but two one.

I like to have brackets[n1] for instructions with a memory location, else we can confuse it with a constant like: n1 equ 3

Good work. Wellcome to the mashine.😊

DosBox official version emulates an intel 80386/80387 CPU/FPU and starts in the 16 bit Real Address Mode of the CPU. And in the 16 bit mode we can use operand size(66h) and address size(67h) prefixe to use 32 operands and 32 bit addresses, but the segment size is limited to 64 kb and A20 address gate is offline.

I like to use x86 assembly with DosBox to create a lot of tiny executable com files with a little help from debug (download&unzip into the mouted folder. I use batch files as an open source container to put all instructions of a routine inside the batch file. Most of these special container batch files have to start with one or more parameter attached. Exampel to start with row color "text" attached: CENTER.BAT 8 1b "output center align" The routine count the ASCII of the text and calculates the offset address for output on vga text screen memory at segment 0b800h.