linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Kirilenko <icedank@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Searching for string problems
Date: Wed, 23 Apr 2003 23:12:09 +0300	[thread overview]
Message-ID: <200304232312.09987.icedank@gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.53.0304231602270.26351@chaos>

Hello!

> >
> > 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.
> >
>
> 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.

Already solved the problem. AX was overwritten, before storing it's value (0 
or 1) into memory. The most stupid mistake, I've seen last year. 20 hours of 
kernel programming without breaks isn't really good.

Thanks too all of you, once again. You really saved my life.

Best regards,
Andrew.


  reply	other threads:[~2003-04-23 20:00 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
2003-04-23 20:12                   ` Andrew Kirilenko [this message]
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=200304232312.09987.icedank@gmx.net \
    --to=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).