Re: itoa assembly version
- From: leon800219@xxxxxxxxx
- Date: 30 May 2006 18:38:00 -0700
Frank Kotler wrote:
The only thing I see (without testing it) is that you zero dx at theBy *end* of your loop do you mean:
*end* of your loop. What's dx on the *first* iteration? Possibly
different in "protected mode" - I assume you mean v86 mode - and real
mode? That's what first comes to mind... try moving it and see if it helps.
mov byte ptr ds:[si], dl
mov dx, 0
At the *first* iteration the dl holds the remainders. If that was
removed the divide operation will be dx:ax/bx again, I believe that's
the cause of "Divide Overflow"
If that's what you mean. But I really curious what make the program
"Divide Overflow" again?
By rmode I mean the real DOS, and by pmode I mean WinXP
What's the advantage of moving ax to cx and then testing cx for zero," jcxz ok" was also a guard against the last bit of a digit, I wish I
compared to just testing ax for zero?
could compare ax against zero but I haven't learn it yet.
Well, you're closing in on it. As Betov says - one time I do agree withWell, Thanks a lot, encouragement is really what I needed.
him - "Courage!"
.
- Follow-Ups:
- Re: itoa assembly version
- From: Frank Kotler
- Re: itoa assembly version
- References:
- Re: itoa assembly version
- From: Frank Kotler
- Re: itoa assembly version
- From: leon800219
- Re: itoa assembly version
- From: Frank Kotler
- Re: itoa assembly version
- Prev by Date: Re: Linking libraries?
- Next by Date: Re: bootloader
- Previous by thread: Re: itoa assembly version
- Next by thread: Re: itoa assembly version
- Index(es):
Relevant Pages
|