public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David Schwartz" <davids@webmaster.com>
To: "Lew Wolfgang" <wolfgang@train.sweet-haven.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: The latest Microsoft FUD.  This time from BillG, himself.
Date: Fri, 29 Jun 2001 19:50:36 -0700	[thread overview]
Message-ID: <NOEJJDACGOHCKNCOGFOMIEFOCDAA.davids@webmaster.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0106291817090.5284-100000@train.sweet-haven.com>


Lew Wolfgang wrote:

> It is something that I read somewhere.  If memory serves, Microsoft
> will allow two installs on the same CD-key.  Note that this is
> different from the old MS key manager, all you had to do there
> was enter the CD-key.  There were no real-time checks on how
> many times it was installed.

	You mean they will allow to overlapping installs. That is, you have
permission to run the software on two machines. This says nothing about
their enforcement scheme.

> This http://two.digital.cnet.com/cgi-bin2/flo?y=eBwm0Hm1h0U0c7G0A4
> says, "In the case of Office XP, people can install the software on two
> computers, such as a desktop PC and a laptop. But the second
> installation requires a phone call to obtain the 44-key unlock code."

	So the first time you install it, you can do it the easy way. After that,
you need to call them to get the code. For all we know, it's as simple as,
"I'm the purchaser and I'd like to install it again".

> The question remains, "How many times will Microsoft let you install?"
> I'll test the process starting on Monday.  I have an Office XP that
> has been installed once.  I'll try it again without giving my name
> and keep trying until I reach the limit.  I'll say that I'm having
> problems with my disk crashing or something.  I'll report my findings
> here.

	That's precisely the question, and we have no answer. It is becoming more
and more obvious to me that statements such as "If the CD key is used again
they just refuse to send the final key" are sheer speculation mixed with a
small dose of FUD.

	More likely, Microsoft will display escalating suspicion with each install,
especially if they are in close time proximity or widely varying physical
locations (or other suspicious patterns). If they find out that a key is
definitely being abused, they will stop issuing unlock codes for it. In
other words, they will cause great inconvenience for pirates and little
inconvenience for legitimate users.

	DS


  reply	other threads:[~2001-06-30  2:51 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-21 13:00 The latest Microsoft FUD. This time from BillG, himself Jesse Pollard
2001-06-28 22:02 ` Pavel Machek
2001-06-29 19:41   ` Lew Wolfgang
2001-06-30  1:10     ` David Schwartz
2001-06-30  1:45       ` Lew Wolfgang
2001-06-30  2:50         ` David Schwartz [this message]
2001-06-30  7:24           ` Lionel Elie Mamane
2001-06-30 14:22             ` Dmitri Pogosyan
2001-06-30 17:04               ` [OT] " Daniel Phillips
     [not found] <fa.hs4no6v.h0k6ok@ifi.uio.no>
2001-06-30 15:38 ` Ted Unangst
2001-07-02  5:14   ` Greg Rollins
     [not found] <87009604743AD411B1F600508BA0F95994C8DF@XOVER.dedham.mindsp eed.com>
2001-06-29 19:47 ` Android
  -- strict thread matches above, loose matches on Subject: below --
2001-06-29 19:11 Clayton, Mark
2001-06-29 18:05 ` Rob Landley
2001-06-22 12:36 Holzrichter, Bruce
     [not found] <51FCCCF0C130D211BE550008C724149E01165690@mail1.affiliatedhealth.org>
2001-06-21 18:21 ` Rob Landley
2001-06-25 18:05   ` Andreas Bombe
2001-06-26 11:46     ` john slee
2001-06-28 22:27   ` Pavel Machek
2001-06-29 20:02     ` Paul Fulghum
2001-06-20 22:53 Wayne.Brown
2001-06-21  7:59 ` Daniel Stone
2001-06-20 20:42 Miles Lane
2001-06-20 21:33 ` Rik van Riel
2001-06-20 22:31   ` Daniel Phillips
2001-06-20 19:53     ` Rob Landley
2001-06-21  8:50       ` Henning P. Schmiedehausen
2001-06-21 16:41         ` Rob Landley
2001-06-20 22:09 ` Alan Cox
2001-06-20 22:33   ` Larry McVoy
2001-06-20 22:51     ` Alan Cox
2001-06-20 23:02     ` Jonathan Morton
2001-06-20 23:04     ` William T Wilson
2001-06-20 23:07     ` Khalid Aziz
2001-06-21  8:46       ` Henning P. Schmiedehausen
2001-06-21 13:48         ` Daniel Phillips
2001-06-21 17:32           ` Miles Lane
2001-06-20 23:16     ` Richard Gooch
2001-06-20 23:20     ` Daniel Phillips
2001-06-21  0:46     ` Michael Bacarella
2001-06-21 14:20       ` chuckw
2001-06-21  8:37     ` Henning P. Schmiedehausen
2001-06-21 16:25       ` Rob Landley
2001-06-21 22:37         ` Michael Bacarella
2001-06-21 22:49           ` Alan Cox
2001-06-22 11:08             ` Rob Landley
2001-06-22 18:33               ` Kai Henningsen
2001-06-28 22:33                 ` Pavel Machek
2001-06-21 12:57     ` Helge Hafting
2001-06-20 23:34   ` Alan Olsen
2001-06-21 10:07   ` Paul Flinders
2001-06-21 12:57     ` Rik van Riel
2001-06-21 14:01       ` Alan Cox
2001-06-23 16:29         ` watermodem

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=NOEJJDACGOHCKNCOGFOMIEFOCDAA.davids@webmaster.com \
    --to=davids@webmaster.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wolfgang@train.sweet-haven.com \
    /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