That's right, Windows 2000 it is no longer available in MSDN, you need
an existing MSDN subscription before the WIndows 2000 was withdrawn -
one where the licence keys for Windows 2000 were claimed.  If that
MSDN has the media too, then all well & good.  But otherwise, that
does not matter, the world is full of Windows 2000 media.

An MSDN subscription lasts for a fixed period (2 or 3 years), during
which media is received or content downloaded.

AIUI, the licence entitles the licensee(an individual programmer or
whatever) to install & use for development purposes.  Microsoft can't
withdraw that, I think.  The licensee remains entitled to install & to
use (within the development restrictions) in perpetuity.

Do you see?

Once again, IANAL

On 12 Sep, 14:33, deanm <[EMAIL PROTECTED]> wrote:
> http://msdn.microsoft.com/en-us/subscriptions/aa948864.aspx
>
> I cannot find a product in MSDN Subscriber Downloads.
> A product might be unavailable for several reasons:
>
> The product is not available due to past Java settlements.  Due to
> past Java settlements we have had to re-release or phase out the
> distribution of several product families. This does not affect current
> installations, copies you may already have, or support timetables.
> More information is available from the Microsoft Java Transition
> page.  The major product families that have been removed from MSDN
> Subscriber Downloads are:
>
> Windows 2000 DDK
> Windows 2000 Professional
> Windows 2000 Server
>
> On Sep 12, 3:23 pm, Dave English <[EMAIL PROTECTED]> wrote:
>
> > On 11 Sep, 15:14, "Marc-Antoine Ruel" <[EMAIL PROTECTED]> wrote:
>
> > > Everyone missed the #1 point. Beside politics, there's a primary issue.
>
> > > There is no way to buy a Windows 2000 license as of today. Due to 
> > > thesettlementof theSun-Microsoftcase,Microsoftcan'tlegallysell
> > > Windows 2000 license anymore. Ican'tget a buildbot on Windows 2000
> > > anymore. And wecan'tsupport a platform that wecan'ttest on a
> > > buildbot. And no, we won't use an old Pentium 120mhz as a buildbot. :)
>
> > > Thanks for your comprehension.
>
> > Surely you could do it from an existing MSDN subscription?
>
> > I don't know the legal position of Chromium vs. Google, but surely
> > Google must have existing MSDNs.
>
> > Volume licensing MSDNs at least are transferable between empoyees.
>
> > I'd imagine the dev/test use of a buildbot could fall with in the MSDN
> > licence.
>
> > IANAL, of course
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Chromium-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/chromium-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to