linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Andrew Kirilenko <icedank@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Searching for string problems
Date: Wed, 23 Apr 2003 13:05:31 -0700	[thread overview]
Message-ID: <20030423130531.0a7cbcc6.rddunlap@osdl.org> (raw)
In-Reply-To: <200304232248.35985.icedank@gmx.net>

On Wed, 23 Apr 2003 22:48:35 +0300 Andrew Kirilenko <icedank@gmx.net> wrote:

| Hello!
| 
| Big thanks to all of you. Now I'm starting to understand how it's working. 
| Here is current version of my code:
| 
| -->
|        jmp         cl_start
| cl_id_str:      .string "STRING"
| cl_start:
|         cld
|         movw    %cs, %ax
|         movw    %ax, %ds
|         movw    $0xe000, %ax
|         movw    %ax, %es
|         movb    $0, %al
|         xor         %bx, %bx  # start of segment
| cl_compare:
|         movw    $cl_id_str, %si
|         movw    $cl_start, %cx
|         subw    %si, %cx
|         decw    %cx
|         movw    %bx, %di
|         repz    cmpsb
|         je      cl_compare_done_good
|         incw    %bx
|         cmpw    $0xffff, %bx  # are we at the end of segment
|         je      cl_compare_done
|         jmp     cl_compare
| cl_compare_done_good:
|        movb $1, %al
| cl_compare_done:

# here the code needs to do something like this,
# to check the second 64 KB block of memory:
	movw	%es, %bx
	cmpw	%bx, $0xe000
	je	all_done
	movw	$0xf000, %bx
	movw	%bx, %es
	xor	%bx, %bx
	jmp	cl_compare


| <--
| 
| And this code won't work as well :(

Do you understand x86 real-mode segment registers?
They can only address a "segment" of 64 KB (roughly).

| Unfortunately, I can't start DOS and check, cause there is no video and 
| keyboard controller on that PC.

oh yes.

--
~Randy

  reply	other threads:[~2003-04-23 19:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-23 16:58 Searching for string problems Andrew Kirilenko
2003-04-23 17:39 ` Richard B. Johnson
2003-04-23 18:05   ` Andrew Kirilenko
2003-04-23 18:15     ` Richard B. Johnson
2003-04-23 18:25       ` Andrew Kirilenko
2003-04-23 18:56         ` Richard B. Johnson
2003-04-23 19:00           ` Andrew Kirilenko
2003-04-23 19:11             ` Randy.Dunlap
2003-04-23 19:37             ` Richard B. Johnson
2003-04-23 19:48               ` Andrew Kirilenko
2003-04-23 20:05                 ` Randy.Dunlap [this message]
2003-04-23 20:05                 ` Richard B. Johnson
2003-04-23 20:12                   ` Andrew Kirilenko
2003-04-23 18:59         ` Randy.Dunlap

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=20030423130531.0a7cbcc6.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=icedank@gmx.net \
    --cc=linux-kernel@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).