From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Wayde Milas <wmilas-/tCmSuwdN3vQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: vista install oddities
Date: Wed, 06 Jun 2007 16:47:58 +0300 [thread overview]
Message-ID: <4666BB0E.60103@qumranet.com> (raw)
In-Reply-To: <46669EA7.801-/tCmSuwdN3vQT0dZR+AlfA@public.gmane.org>
Wayde Milas wrote:
>
>>
>> This is probably some kind of copy protection device, it's making sure
>> you're upgrading to the same machine and not to a different one. So
>> most likely this is by design.
>>
> Maybe... but define "different one". The ultimate upgrade comes with
> its own unique key and the only restriction that applies is that it
> must be installed upon a working windows install.
I don't know anything about this really.
>
> Something else I just tried. When not in kvm on an install I can hit
> next and NOT put a key. I get a popup warning me that I'll have to put
> in a key withing 30 days or the os will cease to function and I hit ok
> to proceed.
>
> Inside kvm if I do the same thing I get the same popup, hit proceed,
> and I'm taken right back to the key activation screen and am not able
> to proceed.
>
> Is it possible vista detects that its running virtulized and prevents
> any install because of it?
>
Maybe. Non-upgrade installs do work.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-06-06 13:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 23:25 vista install oddities Wayde Milas
[not found] ` <4665F0F4.4050803-/tCmSuwdN3vQT0dZR+AlfA@public.gmane.org>
2007-06-06 6:28 ` Avi Kivity
[not found] ` <46665417.4040107-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-06-06 11:46 ` Wayde Milas
[not found] ` <46669EA7.801-/tCmSuwdN3vQT0dZR+AlfA@public.gmane.org>
2007-06-06 13:47 ` Avi Kivity [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-07 9:40 Shahar Frank
[not found] ` <64F9B87B6B770947A9F8391472E032160C26FEE6-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-06-07 12:14 ` Wayde Milas
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=4666BB0E.60103@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=wmilas-/tCmSuwdN3vQT0dZR+AlfA@public.gmane.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.