HP3000-L Archives

January 1997, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Ken Kirby <[log in to unmask]>
Reply To:
Date:
Wed, 29 Jan 1997 09:50:08 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (72 lines)
Hi Art,

Ok, I expected this. I got similar arguments here as we discussed this
in one of our impromptu hallway staff meetings. Remember, the rule here
is: I should only pay for one copy of the software per machine running
that software.

Art Bahrs wrote:
>
> Hi Ken,
>     Not to play Devil's Advocate ... tho I am known for doing that :)
>
>     How do you feel about the fact that we have to buy one licence for Windows
> for every user that will be loading Windows from a network file server???
>
>     Is this that much different from MPE/iX ???

Ahh, the file server argument! Note in this example that, while the
software is stored on only one machine, it is actually run on each
workstation that uses it. Therefore, each machine is running a copy of
the program. When you run a program in MPE/iX, it runs on ONE HP/3000,
not several workstations. Your workstation only provides you with a
window to access the HP/3000. Once again, one copy, one machine.

>
>     I don't think I support Tier Pricing ... but User Pricing makes sence... as
> this is how I buy most of our PC software :)

Another common misconception. Answer me this: the last time you bought
PC software for your home, did they ask you how big your family is?
Let's say it was a game in which several people could participate
concurrently, such as Monopoly or Wheel of Fortune. Did they ask you how
many friends and neighbors you were expecting to come over and play it
with you? Once again, you bought a license for one copy per machine, not
one copy per concurrent user.

>
>     On the concept of the couple with a newborn having to pay more for the new
> "passenger" ... remember that most people (myself included) replace the car with
> something bigger and designed for kids when comes along!
>
>     So, they do end up stopping by the dealership to support that new passenger
> and it does cost more :) hehehe :)

Nice try, but it won't fly. In my analogy, the car represents the
software, and the passengers the users. Using the same comparisons, the
situation you describe involves scrapping an older piece of software
that no longer meets your needs and replacing it with newer technology
that will. Yes, you should pay for something brand new. But you
shouldn't have to pay twice for your old jalopy!

>
> Art "Now if only MPE/iX were also a GUI :) " Bahrs
> +-------------------------------------------+------------------------------+
> | Oregon Health Sciences Foundation         |The views here are no one's,  |
> | Art Bahrs, Manager of Information Services|  least of all, mine!         |
> | President, HP Oregon Regional Users Group (ORERUG)                       |
> +-------------------------------------------+------------------------------+
> | And the men who hold high places must be the ones to start.              |
> +--------------------------------------------------------------------------+
> | [log in to unmask] 'The Professor' Work: (503) 220-8333 Fax: (503) 228-9588 |
> +--------------------------------------------------------------------------+

Let me say it one more time:

Each phone call costs one quarter.
No matter how big the phone booth is.
No matter how many elephants are in it.

--Ken Kirby
  Vanderbilt University

ATOM RSS1 RSS2