From: Frank Kotler <fbkotler@comcast.net>
To: Tu Ha <httu@tma.com.vn>
Cc: linux-assembly@vger.kernel.org
Subject: Re: please help me
Date: Mon, 24 Apr 2006 00:11:51 -0400 [thread overview]
Message-ID: <444C5007.7080203@comcast.net> (raw)
In-Reply-To: <1145873491.3998.17.camel@gaucon>
Tu Ha wrote:
...
> It seems I cannot reference to the "char" memory location. Why?
Wrong combination of ".org" and ds register, I think. Either use ".org
0x7C00", and load ds from cs (presumably zero) as you do (you'll have to
adjust the .org on the signature, too). Or... leave it at ".org 0" (I
assume that's what Gas defaults to), and load ds with 0x7C0. (bios loads
us at 0x7C00, which can be represented as either 0000:7C00 or 07C0:0000).
> How can I debug the binary?
Bochs? I've never used it, but I understand it'll debug bootsectors...
Happy bootin',
Frank
next prev parent reply other threads:[~2006-04-24 4:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 10:11 please help me Tu Ha
2006-04-24 4:11 ` Frank Kotler [this message]
2006-04-24 12:09 ` Tu Ha
[not found] <000101c6734a$573086d0$c41e1ec7@TuThuyHa>
2006-05-09 16:17 ` Frank Kotler
2006-05-10 14:05 ` httu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=444C5007.7080203@comcast.net \
--to=fbkotler@comcast.net \
--cc=httu@tma.com.vn \
--cc=linux-assembly@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).