Re: 16 bit debugging - options?
- From: Pop Tart <morespamsREMOVE@xxxxxxxxxxxxxxx>
- Date: Wed, 20 Feb 2008 19:03:09 -0600
On Wed, 20 Feb 2008 19:47:41 +0000, Frank Kotler wrote:
As I read RBIL, "infile.txt" must exist for dx = 1, try "or"ing it with
16 to open or create. (716Ch does not work with dosemu, but ah=6Ch does,
and that's how *that* works, anyway)
that was the problem. arghh :)
Also, when I got codeview working, debugging was opening the file and
writing the output file to c:\masm611\binr\ - probably due to the way I
invoked codeview from the command line. I kept looking in my project
folder for the outfile to appear. Even when there were no errors, it
wasn't showing up... lol.
and linking with
link16 main.obj,,NUL,,,/CODEVIEW
I'll take your word for it on the command lines... When I (rarely) used
MSlink, I just added commas until it shut up. :)
lol
If the carry flag's set, ax should contain the error number. As an
alternative to running it in a debugger, it isn't difficult to display
the contents of ax... I'll include my Nasm "test" - shouldn't be
difficult to paste the "display" routine into Masm... I don't think
it'll even need alteration... (if it does, you can probably figure it
out). You may have a "printint" (in Irvine's lib?) that you'd prefer.
Best,
Frank
I've tinkered with NASM, and hope to eventually getting around to working
with it in Linux... but, one thing at a time...
--
Regards,
Pop Tart
.
- References:
- 16 bit debugging - options?
- From: Pop Tart
- Re: 16 bit debugging - options?
- From: Pop Tart
- Re: 16 bit debugging - options?
- From: Frank Kotler
- 16 bit debugging - options?
- Prev by Date: Re: 16 bit debugging - options?
- Next by Date: Re: HLA v1.101 is now available on Webster
- Previous by thread: Re: 16 bit debugging - options?
- Next by thread: [OT] for the close of all fission nuclear reactor in the world
- Index(es):
Relevant Pages
|