From: "Natalia Portillo" <claunia@claunia.com>
To: blp@cs.stanford.edu, qemu-devel@nongnu.org
Subject: RE: [Qemu-devel] Re: BIOS behaves different as real BIOS
Date: Sat, 17 Jul 2004 07:45:36 +0100 [thread overview]
Message-ID: <E1Bliz1-0000m6-KR@lists.gnu.org> (raw)
In-Reply-To: <87brifm90u.fsf@benpfaff.org>
Excuse me, where are the CMOS RAM values in qemu :?
> -----Mensaje original-----
> De: qemu-devel-bounces+iosglpgc=teleline.es@nongnu.org
> [mailto:qemu-devel-bounces+iosglpgc=teleline.es@nongnu.org]
> En nombre de Ben Pfaff
> Enviado el: sábado, 17 de julio de 2004 7:40
> Para: qemu-devel@nongnu.org
> Asunto: [Qemu-devel] Re: BIOS behaves different as real BIOS
>
> "Natalia Portillo" <claunia@claunia.com> writes:
>
> > I think that this is because the BIOS searches for the 0x55AA
> > signature on last two bytes of first sector of disk.
> > As far as I remember, this signature was introduced very
> lately and as
> > far as I tested on my real systems, this signature is not really
> > searched at boot time, and every DOS before 3.0 doesn't
> have it (it is
> > used also by later DOSes and Windows to identify a FAT
> filesystem), at
> > least on floppies
>
> You can disable the signature check by setting byte 0x38 in
> the CMOS RAM to a nonzero value.
> --
> "...In the UNIX world, people tend to interpret `non-technical user'
> as meaning someone who's only ever written one device driver."
> --Daniel Pead
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
next prev parent reply other threads:[~2004-07-17 6:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-17 6:01 [Qemu-devel] BIOS behaves different as real BIOS Natalia Portillo
2004-07-17 6:40 ` [Qemu-devel] " Ben Pfaff
2004-07-17 6:45 ` Natalia Portillo [this message]
2004-07-17 6:51 ` Ben Pfaff
2004-07-17 7:04 ` Natalia Portillo
2004-07-17 15:47 ` Ben Pfaff
2004-07-17 7:12 ` [Qemu-devel] " Antony T Curtis
2004-07-17 8:20 ` Natalia Portillo
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=E1Bliz1-0000m6-KR@lists.gnu.org \
--to=claunia@claunia.com \
--cc=blp@cs.stanford.edu \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.