From: Jani Monoses <jani@iv.ro>
To: blp@cs.stanford.edu, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: ecos and qemu
Date: Fri, 23 Jul 2004 18:05:16 +0300 [thread overview]
Message-ID: <20040723180516.0c8c10f4.jani@iv.ro> (raw)
In-Reply-To: <87oem6vkcs.fsf@benpfaff.org>
I'm looking at it right now.
It works also if you extend the floppy image to be 1440M.
something like this
dd if=/dev/zero of=$TMP bs=1024 count=1440
dd if=$FLOPPY of=$TMP conv=notrunc
now $TMP has the extended image.
bdrv_read() drops the last part of the image if it's not 512.
So if the last part of the image is important.... :)
Jani
>
> 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)
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
next prev parent reply other threads:[~2004-07-23 15:09 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 ` [Qemu-devel] " Ben Pfaff
2004-07-23 15:05 ` Jani Monoses [this message]
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=20040723180516.0c8c10f4.jani@iv.ro \
--to=jani@iv.ro \
--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 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).