From: Ben Pfaff <blp@cs.stanford.edu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: ecos and qemu
Date: Fri, 23 Jul 2004 08:01:07 -0700 [thread overview]
Message-ID: <87oem6vkcs.fsf@benpfaff.org> (raw)
In-Reply-To: 20040723111415.4c10521f.jani@iv.ro
Jani Monoses <jani@iv.ro> writes:
> For a while I thought it wasn't since not all apps worked. I think now it is a
> problem with the floppy code(either in qemu or in ecos).
> The apps are built as bootable floppy images and some of them were lacking
> sectors so parts of the image were NULLs leading to crashes.
> If I turn those same floppy images to bootable iso-s using mkisofs and run
> qemu-cdrom on them they work all the time.
That's very interesting. At least part of the problem I've had
with Windows NT 3.51 appears to be floppy-related. I'll have to
see if I can try anything similar.
--
"Let others praise ancient times; I am glad I was born in these."
--Ovid (43 BC-18 AD)
next prev parent reply other threads:[~2004-07-23 15:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 8:14 [Qemu-devel] ecos and qemu Jani Monoses
2004-07-23 15:01 ` Ben Pfaff [this message]
2004-07-23 15:05 ` [Qemu-devel] " Jani Monoses
2004-07-23 15:08 ` [Qemu-devel] QEMU floppy problems (was: ecos and qemu) Johannes Martin
2004-07-23 15:12 ` Jani Monoses
2004-07-23 15:24 ` [Qemu-devel] Re: QEMU floppy problems Ben Pfaff
2004-07-30 10:01 ` [Qemu-devel] QEMU floppy problems (was: ecos and qemu) Johannes Martin
2004-07-30 10:06 ` Jani Monoses
2004-07-30 18:56 ` SPAM[RBL] Re: [Qemu-devel] QEMU floppy problems Leonardo Marques de Souza
2004-07-23 15:14 ` [Qemu-devel] QEMU floppy problems (was: ecos and qemu) Jani Monoses
2004-07-23 15:51 ` Johannes Martin
2004-07-23 15:27 ` [Qemu-devel] Re: QEMU floppy problems Ben Pfaff
2004-07-23 16:03 ` [Qemu-devel] QEMU floppy problems (was: ecos and qemu) Karel Gardas
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=87oem6vkcs.fsf@benpfaff.org \
--to=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.