linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Andrew Kirilenko <icedank@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Searching for string problems
Date: Wed, 23 Apr 2003 16:05:45 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0304231602270.26351@chaos> (raw)
In-Reply-To: <200304232248.35985.icedank@gmx.net>

On Wed, 23 Apr 2003, Andrew Kirilenko 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:
> <--
>
> And this code won't work as well :(
>
> Unfortunately, I can't start DOS and check, cause there is no video and
> keyboard controller on that PC.
>
> Best reagrds,
> Andrew.

Change this:

         movw    $0xe000, %ax

To:
         movw    $0xf000, %ax

... like I told you. The BIOS ROM contents, the stuff that has the
serial number _must_ start where I told you.

Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Why is the government concerned about the lunatic fringe? Think about it.


  parent reply	other threads:[~2003-04-23 19:50 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
2003-04-23 20:05                 ` Richard B. Johnson [this message]
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=Pine.LNX.4.53.0304231602270.26351@chaos \
    --to=root@chaos.analogic.com \
    --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).