For example, since Vista home editions are permitted in the EULA to have no
more than 5 inbound connections and Business is permitted 10, a registry or
other modification to allow 10 in Home is deemed exceeding the scope of the
Home license and puts you out of compliance. There are lots of other
edition-specific limitations that are enforced in the technology by registry
keys and such. Just because you know how to exceed the limitations
specified in the EULA does not keep you from being out of compliance when
you do it.
In this case, if an upgrade edition license prohibits continued use of the
software after its license has been subsumed by the upgrade license, then
the mere fact that you can make it work anyway (working around the technical
limitation) does not make it OK to do so.
I want to reemphacize that because this is a licencing issue, whatever you
decide to do on your own machine, don't give out advice to other users to do
it unless you can get confirmation from a Microsoft local office that it
does not create an out of compliance situation in your region. Remember,
like OEM restrictions, this can vary according to your region.
"MICHAEL" <u158627_emr@dslr.net> wrote in message
news:%23raOs9bRHHA.4692@TK2MSFTNGP02.phx.gbl...
> >You may not work around any technical limitations in the software
>
> I've never liked that statement.... I'm not even sure what that could
> possibly cover.
>
> -Michael
>
> "Colin Barnhorst" <colinbarharst@msn.com> wrote in message
> news:4EA92999-9E8B-4043-9226-003DF7C9EF8E@microsoft.com...
>> The Vista EULA states:
>>
>> "8. SCOPE OF LICENSE. The software is licensed, not sold. This agreement
>> only gives you some
>> rights to use the software. Microsoft reserves all other rights. Unless
>> applicable law gives you
>> more rights despite this limitation, you may use the software only as
>> expressly permitted in this
>> agreement. In doing so, you must comply with any technical limitations in
>> the software that only
>> allow you to use it in certain ways. For more information, see
>> http://www.microsoft.com/licensing/userights. You may not
>> · work around any technical limitations in the software;
>> (snip)
>>
>> The procedure in the DT article may be covered by this provision. At the
>> very least, I would check with MS to see if does before recommending it
>> to others.
>>
>> Now, guys, fire away.
>