hey.. I'm really not sure where I should go for help with this so I decided to try here along with the other forums I've tried lol.
I used dos debug to dump a file (it HAS to be done using dos) the out is here pastebin.com/m69fa9513 so I have all that stored in file.scr now using debug in dos:
debug file.scr
r cx
AOF
n file.otm
w
q
that's "supposed" to assemble the dumped file back to an otm file. There's a reason why I'm doing it this way.. so yea, I'm just curious why it's not assembling it? I did it once and it assembled fine I just forgot what I did right...
thanks
ps: it copies the hex code as it is to file.otm
DOS Debug
Started by youwish, Aug 27 2008 06:59 AM
2 replies to this topic
#1
Posted 27 August 2008 - 06:59 AM
|
|
|
#2
Posted 27 August 2008 - 07:47 AM
Check dargueta's blog. He's writing a series on architecture, debugging, assembling, disassembling and much more, and he's using debug for many of the examples.
#3
Posted 27 August 2008 - 09:44 AM
Assembly is the only language I know. However that doesn't answer my question :) The issue still exists. How to assemble hex code using dos debug...
ps: why the hell is he using 16-bit for teaching assembly when we're in the 64-bit days although everything is still 32-bit..for now :)
pps: Dos isn't my strong point, there was no need at-all for me to use it for something like this up until now.
The correct input was:
rcx
56F0
n C:\file
w
q
thank you for you're reply :)
ps: why the hell is he using 16-bit for teaching assembly when we're in the 64-bit days although everything is still 32-bit..for now :)
pps: Dos isn't my strong point, there was no need at-all for me to use it for something like this up until now.
The correct input was:
rcx
56F0
n C:\file
w
q
thank you for you're reply :)
Edited by youwish, 27 August 2008 - 11:34 AM.


Sign In
Create Account


Back to top









