qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Using Qemu to install Linux in a Windows XP
Date: Mon, 15 Nov 2004 22:46:09 +0100	[thread overview]
Message-ID: <419923A1.4000905@bellard.org> (raw)
In-Reply-To: <pan.2004.11.15.16.34.43.393327@reply.to>

Ronald wrote:
> Le Mon, 15 Nov 2004 10:40:22 -0500, Brett Bonfield a écrit :
> 
> 
>>On Sun, 14 Nov 2004 22:46:59 +0100, Fabrice Bellard <fabrice@bellard.org>
>>wrote:
>>
>>>Brett Bonfield wrote:
>>> > [...]
>>>
>>>>Also, would you consider making QEMUMenu.bat work with "dd for Win32"
>>>>as well as it works with Zitu's program. dd for Win32 is available
>>>>here: http://uranus.it.swin.edu.au/~jn/linux/rawwrite/dd.htm
>>>>
>>>>The advantage it has over mkqemuimage.exe is that it can make any size
>>>>images, at least so far as I can tell. The logic John Newbigin emailed
>>>>goes as follows:
>>>
>>>Then why not fixing mkqemuimage.exe to do that too ?
>>>
>>>Fabrice.
>>
>>I hope I didn't offend anyone and I definitely didn't mean to imply that
>>dd for Win32 was somehow better than mkqemuimage.exe. Honestly, I don't
>>know anything about mkqemuimage--someone on the Mepis forum suggested
>>using dd so I investigated how to do that on Windows. Is there a good
>>reason to use mkqemuimage instead of dd for Win32? I have no idea how to
>>adjust mkqemuimage so that it meets my needs, but if someone else wants to
>>take on that project I suspect I'm one of many people who would be
>>grateful.
>>
>>Brett
> 
> 
> Is there a particular reason to not use qemu-img.exe?
> mkqemuimage is perhaps much simpler to use but have this 2G limit and only
> output raw images.
> 
> Anyway this is a nice tool that have been created for making empty images
> to use with qemu on windows instead of borrowing one from another project.  

OOops, sorry, I wanted to say that qemu-img.exe should be used instead 
of other tools as it handles all images formats that QEMU supports and 
some manipulations like AES encryption and compression.

Fabrice.

  reply	other threads:[~2004-11-15 21:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5100168789854548368@unknownmsgid>
2004-11-14 21:41 ` [Qemu-devel] Re: Using Qemu to install Linux in a Windows XP Brett Bonfield
2004-11-14 21:46   ` Fabrice Bellard
2004-11-14 15:45     ` [Qemu-devel] SDL compile error Shivkumar Shivaji
2004-11-15  0:20       ` Jim C. Brown
2004-11-15 15:40     ` [Qemu-devel] Re: Using Qemu to install Linux in a Windows XP Brett Bonfield
2004-11-15 16:34       ` Ronald
2004-11-15 21:46         ` Fabrice Bellard [this message]
2004-11-16  0:56           ` [Qemu-devel] " Ronald
2004-11-14 23:03   ` [Qemu-devel] " Ronald
2004-11-15 13:52   ` Anand Kumria
     [not found] <8065327220681899303@unknownmsgid>
2004-11-15 18:04 ` Brett Bonfield
2004-11-15 19:54   ` Ronald
2004-11-15 21:54   ` Fabrice Bellard
     [not found] <-2034955394811227980@unknownmsgid>
2004-11-14  2:57 ` Brett Bonfield
     [not found] <4854949625174207626@unknownmsgid>
2004-11-13  3:18 ` [Qemu-devel] " Brett Bonfield
2004-11-13 12:17   ` [Qemu-devel] " Ronald

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=419923A1.4000905@bellard.org \
    --to=fabrice@bellard.org \
    --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).