9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: elbing <elbingmiss@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] installing Plan 9 under Microsoft's free Virtual PC?
Date: Mon, 24 Jul 2006 19:14:13 +0200	[thread overview]
Message-ID: <a0214d140607241014m74d573d7mf6d304784d8bf982@mail.gmail.com> (raw)
In-Reply-To: <53f976bd0607240941q6967ead3ld9114079775c4814@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]

2006/7/24, Andrew Hudson <ahudson.inc@gmail.com>:
>
> Since Microsoft just decided to release its Virtual PC virtualization
> product for free I decided to give it a spin and see how Plan 9 worked
> as a virtualized OS. I downloaded Virtual PC from here
> (http://www.microsoft.com/windows/virtualpc/downloads/sp1.mspx) and
> installed it on a Proliant server with a 2.4 GHz Xeon processor, 1.3
> GB of RAM, and a 15K SCSI disk, Windows 2000 Server. Virtual PC
> complained that it was only supported on Windows 2003 and Windows XP
> but seemed to install fine.
>
> At the partdisk prompt I was not able to install a Master Boot Record
> (mbr) in Virtual PC's virtual disk partition and so the installation
> stopped dead. Does anyone have any insight to this problem or a
> possible work-aounrd? Running Plan 9 under the now free Virtual PC
> would eliminate a lot of hardware compatibility headaches and make
> Plan 9 more accessible to a large number of people running Windows.
>
> - Andrew




I've got running Plan9 in a Virtual PC 5.3.582.27 (not free), with XP in an
Acer Aspire AMD 2.0GHz (Sempron 3000, 1GB RAM) and tipycal hardware. When it
asked me about mbr, it offered to create a new mbr, I said "y" and
installation continued without problems. It copied filesystem very slow,
around one hour.

Elbing

[-- Attachment #2: Type: text/html, Size: 1701 bytes --]

  reply	other threads:[~2006-07-24 17:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-24 16:41 Andrew Hudson
2006-07-24 17:14 ` elbing [this message]
2006-07-24 18:21   ` Paweł Lasek
2006-07-24 18:24     ` andrey mirtchovski
2006-07-24 18:28       ` Paweł Lasek
2006-07-24 18:32         ` Sascha Retzki
2006-07-24 19:11           ` David Leimbach
2006-07-24 18:32         ` andrey mirtchovski
2006-07-24 18:39           ` Paweł Lasek
2006-07-24 18:41             ` Sascha Retzki
2006-07-24 18:45             ` Ronald G Minnich
2006-07-24 19:03               ` Paweł Lasek
2006-07-24 19:30                 ` Ronald G Minnich
2006-07-24 19:42                   ` Paweł Lasek
2006-07-24 20:24                     ` Richard Miller
2006-07-24 20:30                     ` Ronald G Minnich
2006-07-25 10:31                       ` Paweł Lasek
2006-07-24 18:34 Andrew Hudson
2006-07-24 19:34 ` Álvaro Jurado Cuevas
2006-07-24 22:32 ` Sascha Retzki

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=a0214d140607241014m74d573d7mf6d304784d8bf982@mail.gmail.com \
    --to=elbingmiss@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).