Vista - If I buy the VISTA upgrade instead of the full version....

My experience of the generic oem clean install was pretty similar - very
fast and smooth. Also noticed the speed-up in the formatting.

I don't think the upgraders have been quite so fortunate though, judging
from some of the nightmare stories in here.

--
Jon


"Donald McDaniel" <orthocross@comcast.invalid> wrote in message
news:e62DIlhSHHA.4028@TK2MSFTNGP03.phx.gbl...
> "Jon" <Email_Address@SomewhereOrOther.com> wrote in message
> news:%23SK9CQhSHHA.4404@TK2MSFTNGP03.phx.gbl...
>>
>>
>>
>> "jimmy fallon" <jimmyfallon@discussions.microsoft.com> wrote in message
>> news:70851404-9C53-41E2-8D4A-93C0D8D72B4B@microsoft.com...
>>> Does it work like with xp where you can just put in the xp cd during
>>> installation? or does it force you to load xp on the machine and do the
>>> upgrade?
>>> thanks...
>>> jf
>>>
>>>
>>
>>
>> Officially the latter, although workarounds have emerged.
>>
>> Either way it's a looooooooooooong process with the upgrade, so get the
>> full version if you can.
>>
>> --
>> Jon
>
>
> I have a free upgrade coming from Dell soon (hopefully) to Vista Home
> Premium. But I decided to go ahead and purchase a Generic OEM from the
> local computer shop.
>
> 1) The installation went FAST. I mean FAST. 30 minutes or less,
> including formatting my HD (300GB). Normally, a clean installation takes
> anywhere from 45 minutes to an hour (if one also formats the HD) -- or
> longer with a larger HD.
> 2) However, moving my files to the new installation took a long time,
> since they had to be moved piece-meal.
> 3) The "Upgrade" choice was grayed out. As in the past, "Generic Full
> OEMs" must be installed "clean". Personally, this is my favorite kind of
> installation of a Windows product. The installation was clean and simple.
> 4) The shop owner was very careful this time to warn me that I would be
> subject to the "System Builder License" for Vista, and would be the one
> who supplied all support for the product.. This has NEVER happened since
> I've been using Microsoft OSes (since DOS 2.11). That's OK, since I'm the
> one who is the "system builder". Personally, I wouldn't want to leave
> support for my OS in the hands of some stranger at Dell. While my Dell
> was put together very well, I HATE the crap they put on their OS disks.
> 5) The package containing my product was NOT the normal "shrink-wrapped"
> package with a little booklet. It was actually in a cardboard container
> which stated that it was a "System builder kit", and the owner would be
> subject to the System Builder License. The COA was already stuck to the
> plastic DVD case containing the disk, and had no other branding on it than
> the Microsoft brand (unlike many "Full OEM" products for XP, which have
> the sticker with the COA on it somewhere in the shrink-wrap itself, and
> easily lost, since the shrink-wrap is usually discarded immediately.
>
> All-in-all, I am very happy with my product. Transitioning to a new OS is
> never an easy process, but I really expended very little energy making the
> move, since all my backups were on a secondary disk.
>
> The REAL problems are the software manufacturers who have not prepared for
> the transition, such as Apple and a few others.
>
> Anyway, good luck to all who are changing over to Vista.
> I do have ONE thing to say: The final released product is MUCH more
> stable than the Betas and Release Candidate. Microsoft really cleaned
> this product up.. In addition, I've really not had many notifications
> from either UAC or the Firewall. I was prepared for lots of hassle from
> them, but so far, I've not had many problems.
>
> Donald L. McDaniel
> orthocross@comcast.invalid
> "To validate me, simply 'net' me."
> Please reply to the original thread and newsgroup.
> -------------------------------------------------------------------------
>

On Tue, 06 Feb 2007 19:08:44 +0000, Paul-B wrote:

> I always get a laugh when someone who has discovered a legal workaround
> and publishes it is then told "It isn't ethical" or "It's immoral", or
> "It's against the spirit" etc. etc. etc.

These big megacorps sure don't care about ethics, morality, or the finer
points of law when they're screwing consumers and stabbing business
partners in the back. It's rather hypocritical of their supporters to
turn a blind eye to these activities and yet moan about consumers' lack of
ethics when they play by the very same rules.

From the procedure, one reason is that Microsoft wanted folks doing
this to have twice the pleasure of running clean installs....


--
Barry Schnur

> So that works on a blank computer, even if you don't have a valid copy of XP
> to upgrade from???

> Not that I'd ever consider doing anything like that... honest Guv!
>

Right, that's what would be a license violation (as would continuing to
run XP on the original computer.


--
Barry Schnur

So I went out and bought the Upgrade....
Then, I took someones advice on this thread.
When it asked me for the key code, i put it in... then, setup told me to
install using that keycode from within windows..

THEN, I simply erased the key code, and went ahead with the install.
Formatted the Raid drive after installing drivers for it,,,
And I got a clean install!!! No problems whatsoever!!
So thanks Microsoft for the workaround!!!! I assume you knew about it all
along, wish you'ld clue us all in!
jf



"BSchnur" wrote:

> > So that works on a blank computer, even if you don't have a valid copy of XP
> > to upgrade from???
>
> > Not that I'd ever consider doing anything like that... honest Guv!
> >
>
> Right, that's what would be a license violation (as would continuing to
> run XP on the original computer.
>
>
> --
> Barry Schnur
>

Paul-B wrote:
> CybrGuy wrote:
>
>> Alias wrote:
>>> Roscoe wrote:
>>>> It forces you to load xp on the machine and do the upgrade.
>>>> Convenient, eh?
>>> Read this:
>>>
>>> http://www.dailytech.com/article.aspx?newsid=5932
>>>
>>> Alias
>> This may very well work, I haven't tried it yet. But, it is a
>> violation of the license agreement, at least until MS says otherwise.
>> Only time will tell if there are any other problems with using this
>> method and circumventing MS's intentions. I can't imagine that they
>> wouldn't have known about this workaround, so they may well have
>> broken it in some subtle way that hasn't been found yet. So, our
>> options with upgrade disks at this point are to install 'over' XP, or
>> break our license agreements. I don't like either choice very much...
>
> I always get a laugh when someone who has discovered a legal workaround
> and publishes it is then told "It isn't ethical" or "It's immoral", or
> "It's against the spirit" etc. etc. etc.
>
> I don't know if any of you remember, but when AMD brought-out their
> socket A Athlon/Duron chips they produced them all with the same (high)
> clock speed, so as to gain from economies of scale in production, then
> downrated some of the chips by breaking the L2 bridges so that the
> clock-speed was lower. These they sold at a lower cost. It was
> possible, using just a pencil, to bridge the broken L2 bridges so that
> the chip ran at the original high speed. I managed to turn my 600MHz
> Duron into a 900MHz one by simply doing this, thus saving myself a
> considerable sum.
>
> No-one at the time considered that to be illegal, immoral, cheating AMD
> or anything else. I can't see what the difference is if you are
> installing an upgrade, provided you have a genuine copy of XP and are
> not going to re-use it or sell it on.
>

I'm not telling anyone not to do it. I may end up doing it myself when
my upgrade disk arrives. I am merely saying that it is a violation of
the licensing agreement as written (1) and MS would be within their
rights to invalidate your install of Vista. I don't know that they
will, but neither do I know that they wont. MS is very picky about
their legalese and have a whole slew of lawyers on retainer for no other
purpose than to protect their products.

(1) There are several places where working around their intended install
method would be a violation of their license, but the clearest and
simplest is Section 8. "Scope of license". "The user may not: work
around any limitations in the software. Blanket as that may be, it is
all they need for this issue.

excuse my potential ignorance, but I purchased an UPGRADE and boot from the
DVD and it performed the clean install without the workaround.

"jimmy fallon" <jimmyfallon@discussions.microsoft.com> wrote in message
news:2009E8BD-5380-4442-B003-EB1EE34F3A38@microsoft.com...
> So I went out and bought the Upgrade....
> Then, I took someones advice on this thread.
> When it asked me for the key code, i put it in... then, setup told me to
> install using that keycode from within windows..
>
> THEN, I simply erased the key code, and went ahead with the install.
> Formatted the Raid drive after installing drivers for it,,,
> And I got a clean install!!! No problems whatsoever!!
> So thanks Microsoft for the workaround!!!! I assume you knew about it all
> along, wish you'ld clue us all in!
> jf
>
>
>
> "BSchnur" wrote:
>
>> > So that works on a blank computer, even if you don't have a valid copy
>> > of XP
>> > to upgrade from???
>>
>> > Not that I'd ever consider doing anything like that... honest Guv!
>> >
>>
>> Right, that's what would be a license violation (as would continuing to
>> run XP on the original computer.
>>
>>
>> --
>> Barry Schnur
>>

CybrGuy wrote:

> MS is very picky about their legalese and have a whole slew of
> lawyers on retainer for no other purpose than to protect their
> products.

Heh! They must be sitting on their arses over here in Europe, then,
'cos we rarely see or hear from them. And when we do they end-up
costing Microsoft a fortune, 'cos they always lose.

--
Paul-B

OK -- glad it worked -- I haven't tried it -- did an in place with the
upgrade version.


--
Barry Schnur

> excuse my potential ignorance, but I purchased an UPGRADE and boot from the
> DVD and it performed the clean install without the workaround.
>
It sounds like you got a new install DVD. I was able to boot from the
DVD, but when I responded with the correct key code, the prompt
indicated I needed to do this from within XP.

--
Barry Schnur