I like to use batch files as open source container for x86 assembly to create a new executable file with a little help from Debug. Debug use the instruction to build the mashine code without a linker. Most of these container batch files have to start with one or more hexadecimal or "string" parameter(%1 %2 %3) attached (separeted with a space between) to build and to modify the routine inside, but without that the executable have to convert/combining the ASCII digits of the parameter into values. This part do Debug. Batch files(script files) are the only one executable files that have no problems with copy&paste. All other executable can’t be copy&paste, because not all bytes of a mashine code are visible as an ASCII character. Batch files let you see the source code, but not an executable of mashine code. Batch files with x86 are for tiny executable only usefull. Debug don’t provide jump labels, so we have to use the addresses for memory access and jump instructions.
All instructions of the syscall are not visible and hidden, so we don’t know how the string is going to the screen. Personaly i like to write directly into the screen memory without using a syscall.
To prevent confusion, i prever to speak hexadecimal values digit by digit and not like decimal values, because hex is not based on ten. Else we have to say e-thousand b-hundred f-ty f for ebff and this sounds badly wrong. So 80h is not eighty h, but eight zero h.
Good work.
I like to use batch files as open source container for x86 assembly to create a new executable file with a little help from Debug.
Debug use the instruction to build the mashine code without a linker. Most of these container batch files have to start with one or more hexadecimal or "string" parameter(%1 %2 %3) attached (separeted with a space between) to build and to modify the routine inside, but without that the executable have to convert/combining the ASCII digits of the parameter into values. This part do Debug.
Batch files(script files) are the only one executable files that have no problems with copy&paste. All other executable can’t be copy&paste, because not all bytes of a mashine code are visible as an ASCII character.
Batch files let you see the source code, but not an executable of mashine code. Batch files with x86 are for tiny executable only usefull. Debug don’t provide jump labels, so we have to use the addresses for memory access and jump instructions.
All instructions of the syscall are not visible and hidden, so we don’t know how the string is going to the screen. Personaly i like to write directly into the screen memory without using a syscall.
To prevent confusion, i prever to speak hexadecimal values digit by digit and not like decimal values, because hex is not based on ten. Else we have to say e-thousand b-hundred f-ty f for ebff and this sounds badly wrong. So 80h is not eighty h, but eight zero h.
I am not familar with the C programming language. If somebody try to explain assembly with C commands i can’t understand it.😂
A very annoying and insanely droning monotone from your ai narrator.