All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leigh Dyer <leigh@eclinic.com.au>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Windows 2000 installation problem
Date: Tue, 04 May 2004 13:52:25 +1000	[thread overview]
Message-ID: <1083642745.22158.25.camel@shawn.local> (raw)
In-Reply-To: <web-2457145@calmail-ma.berkeley.edu>

On Mon, 2004-05-03 at 20:08 -0700, Frederick Earl Gray wrote:
> Hi, all,
> 
> [First of all, let me say that I've tried to send this message a number
> of times in my usual way, and it has been continuously deferred with the
> message "451 Could not complete sender verify callout"...perhaps an overly
> aggressive spam filter?  I'm trying again through the University's webmail
> system...we'll see what happens.]
> 
> I have been trying to install Win2K Pro on qemu (running under Debian "testing"
> on x86).  The installation almost makes it through, but not quite.  At the
> point where you can select optional Windows components, it shows 0.0 MB
> available disk space and simply won't let you proceed, no matter which
> components you select.  A screenshot is at
>    http://kaon.physics.berkeley.edu/~fegray/disk-full.png
> 
> I've tried 1.5 GB and 2 GB partitions, and I've tried both today's CVS
> and the 0.5.3 release.  (In the latter, I commented out the initialization of
> the SB16 sound card and I applied Renzo Davoli's NE2000 patch and Mark
> Jonckheere's patch to suppress dummy mouse events.)  I tried both FAT and NTFS
> partition types.  Always the same results.
> 

I've seen this problem as well - the last time was with a 2000Mb image
that I created using bximage. I tried another install on the same
machine, using dd to create a 3000Mb blank file to use as the disk
image, and that worked. The bximage image was essentially empty (ie:
used no space on disk until i started installing to it), whereas the dd
image was filled with zeros. I'm not sure why this would make any
difference though.

Just to confuse things, I tried using a 2000Mb bximage on another
machine, and Win2k installed without problems. It's not really fast
enough to be genuinely usable on my P3-800 at work, but on my Athlon XP
2200+ at home it's quick enough for basic tasks.

Thanks
Leigh

> I gather that many of you have been successful in installing Win2K --
> has anyone else run into this problem?  Any suggestions for me?  At the
> moment I'm using an evaluation copy of vmWare to run some electronics CAD
> programs (my only use for Windows), but that runs out in a few weeks, and it
> sounds like qemu is close to being ready for prime time if I can just get
> past this one screen...
> 
> Thanks very much for your help,
> 
> -- Fred
> 
> -- Fred Gray / Visiting Postdoctoral Researcher                 --
> -- Department of Physics / University of California, Berkeley   --
> -- fegray@berkeley.edu / phone 510-642-4057 / fax 510-642-9811  --
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://mail.nongnu.org/mailman/listinfo/qemu-devel

      reply	other threads:[~2004-05-04  3:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-04  3:08 [Qemu-devel] Windows 2000 installation problem Frederick Earl Gray
2004-05-04  3:52 ` Leigh Dyer [this message]

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=1083642745.22158.25.camel@shawn.local \
    --to=leigh@eclinic.com.au \
    --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.