Received: from sloth.swcp.com (sloth.swcp.com [198.59.115.25]) by nacm.com (8.6.10/8.6.9) with ESMTP id TAA29466 for <executor@nacm.com>; Mon, 12 Jun 1995 19:10:41 -0700
Received: from iclone.UUCP (uucp@localhost) by sloth.swcp.com (8.6.9/8.6.9) with UUCP id UAA20367 for nacm.com!executor; Mon, 12 Jun 1995 20:10:40 -0600
Received: by mailhost (nextstep Smail3.1.29.0 #11)
id m0sLLDE-000YbmC; Mon, 12 Jun 95 19:56 MDT
Message-Id: <m0sLLDE-000YbmC@mailhost>
Date: Mon, 12 Jun 95 19:56 MDT
From: ctm@ardi.com (Clifford T. Matthews)
To: executor@nacm.com
Subject: proposed new pricing
Sender: owner-paper@nacm.com
Precedence: bulk
Hi Folks,
1.99n still isn't out. Sorry about that. However, as a separate
matter we are going to be unifying our price structure. Since I've
botched before, I'd like people to look at this and send comments
before we finalize it (when 1.99n ships in the next few days). Please
send your comments directly to me "ctm@ardi.com" instead of to this
list, unless you're absolutely sure you want other people on the list
seeing your commentary.
The E/NS prices are dramatically lower than what they have been of
late, although until 1.99<x> is available for NEXTSTEP, we won't be
actively selling E/NS. We've introduced a student price for
Executor/DOS and raised the Executor/Linux student price, but in
reality the student price buys you both E/D and E/L for the same
price. This is a discount for students buying E/D and a discount for
students who buy both E/D and E/L, but a price increase for students
who only want buy E/L.
Our original Linux prices were as low as they were because we thought
E/L would be a very rough product with no tech. support, but it's come
a long way and I think it is at parity with E/D, especially once our
SVGAlib port is available.
Our previous policy was that E/L users would be entitled to free 2.0.x
releases (but not 2.1, 2.2, etc.). Now we've made that policy all
inclusive, so E/NS and E/D owners will also be entitled to those free
updates. We'll have to recompute authorization keys before 2.0 comes
out.
Between the "=========="s is the proposed text that we'll put in our
new FAQ, README, unofficial WWW pages and license panels. Please let