RE: The Most Oppressive Clause in Microsoft's EULA...

From: Chuck Davis (ChuckDavis_at_discussions.microsoft.com)
Date: 10/14/04


Date: Wed, 13 Oct 2004 18:31:03 -0700

We already have copyrights that persist.

The following is from this site:
http://www.copyright.gov/circs/circ1.html#noc

A work that is created (fixed in tangible form for the first time) on or
after January 1, 1978, is automatically protected from the moment of its
creation and is ordinarily given a term enduring for the author's life plus
an additional 70 years after the author's death.

Rant as you will. If you had created something of value, you would certainly
want to collect a income base on its market value, you might even want your
ofspring to benefit.

"democratix" wrote:

> ....and typical of proprietary software in general:
>
> *******
> * Limitations on Reverse Engineering, Decompilation and
> Disassembly. You may not reverse engineer, decompile, or
> disassemble the SOFTWARE, except and only to the extent that
> such activity is expressly permitted by applicable law
> notwithstanding this limitation.
> *******
>
> In effect:
>
> If you want to get some end-use out of these instructions, you can run
> them on your computer, but you're not allowed to figure out what your
> computer is doing when it runs them.
>
> Sorry, let me read that again to make sure I understood it...
>
> You are not allowed to figure out what your computer is doing!
>
> .... that's what I thought.
>
> At any time now or in the future that you set your computer to run
> these instructions, any parts of that computer which may reveal useful
> information about what it's actually doing, become our sovereign
> property, and we say you can't touch or look at them.
>
> I hate to break it to the corporations, but it's my computer and I'll
> learn whatever I want from it, and use that knowledge however I see
> fit. The only reason I bought the hardware in the first place is to be
> able to investigate what it does, and manipulate it to my own
> purposes, and no one is going to convince me that they own an
> instruction. I find it insulting they would even try.
>
> Owning intsructions, ha, how absurd. Next we'll have copyrights that
> persist even after the artist is dead.
>



Relevant Pages

  • The Most Oppressive Clause in Microsofts EULA...
    ... reverse engineering. ... Decompilation and ... >disassemble the SOFTWARE, except and only to the extent that ... >If you want to get some end-use out of these instructions, ...
    (microsoft.public.windowsxp.basics)
  • Re: Create menu for instruction on how to use database when opened for the first time
    ... form the first time they open the database ... to read through instructions for how to ... on using HTML pages (not Microsoft's HTML Help) for displaying user help at ...
    (comp.databases.ms-access)
  • Re: [PHP] question
    ... this the first time that I have posted a question here and I have ... If you are accessing it through HTTP then the comments on the filesize manual page contain good instructions for getting the Content-Length from the response. ... If you're using FTP then the ftp-sizefunction will give you what you want. ...
    (php.general)
  • Re: R-click create new Word doc (not docx)
    ... instructions in the article, except replace steps 3 and 4 with these: ... first time but is gone the second time. ... (Although I don't really understand the compulsion to use Word 2007 but ...
    (microsoft.public.word.customization.menustoolbars)
  • Re: Making OE 6.0 Default e-mail client
    ... meantime I've managed to get round it. ... Have just followed your instructions ... For the first time, Outlook Express appeared ... > Make certain to include the quotations marks and the space between the ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)