You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Q1: In bios.asm, how can I save a value (number, string, etc.) such as the content of biosstr (string) in a memory area of the emulator, and then read and print that memory area from 8086tiny.c?
Q2: Same question as Q1 but in reverse, storing a variable in 8086tiny.c, and then reading and printing that value from bios.asm.
Q3: In FreeDOS kernel, how can I save a value (number, string, etc.) in a memory area of the emulator, and then read and print that memory area from 8086tiny.c or from bios.asm?
Q4: Same question as Q3 but in reverse, storing a variable in 8086tiny.c or bios.asm, and then reading and printing that value from FreeDOS kernel.
q1: Put value into memory using bios.asm, detect if memory value changed in emulator, print it
q2: same but reverse
q3: same
q4: same
q5: this is emulator of 8086 not emulator of dos. Search for other DOS emulators like dosbox
q6: not possible, modern hard drive bigger than 527, if you have old pc, feel free just open /dev/hda.
Q1: In
bios.asm
, how can I save a value (number, string, etc.) such as the content ofbiosstr
(string) in a memory area of the emulator, and then read and print that memory area from8086tiny.c
?Q2: Same question as Q1 but in reverse, storing a variable in
8086tiny.c
, and then reading and printing that value frombios.asm
.Q3: In FreeDOS kernel, how can I save a value (number, string, etc.) in a memory area of the emulator, and then read and print that memory area from
8086tiny.c
or frombios.asm
?Q4: Same question as Q3 but in reverse, storing a variable in
8086tiny.c
orbios.asm
, and then reading and printing that value from FreeDOS kernel.Q5: I have same question: https://8086tiny.freeforums.net/thread/82/starting-exe-files-command-line
Q6: I have same question: https://8086tiny.freeforums.net/thread/62/local-drive-access
regards,
Danny.
The text was updated successfully, but these errors were encountered: