We spent a lot of time testing 1.99k over here. It is likely to fix
most, if not all of the major bugs that people have reported in 1.99k
(where major means unable to run on a configuration that formerly
supported Executor/DOS 1.99<X>). Still, we only have four different
flavors of PC (two of which are both from Dell), so there's a chance
that your particular configuarion will still have trouble.
I'm anxious to get feedback from people who try 1.99k out, since there
is a large computer show in Germany coming up and we need to decide
whether 1.99k is good enough to show. I'm hoping that it is, but
1.99j clearly wasn't. I think it's also probably time for us to put a
1.99<X> release out on SimTel, and with more feedback I can determine
whether 1.99k is good enough to be our first experimental release out
there.
There is no 1.99k release for Linux, even though internally we've
fixed the bug that was limiting the maximum screen size to be 640x480.
As has been the case for many releases, there is no 1.99k release for
NEXTSTEP. We're hoping that will change soon.
I haven't yet e-mailed all existing customers with e-mail addresses
their new serial numbers and keys, but I am planning on doing that in
the next few (i.e. 10) hours, assuming no other "fires" come up.
Again, if you've purchased Executor/DOS from us in the past and
haven't sent in your registration card, please do so. Thanks.
--Cliff
ctm@ardi.com
From owner-executor Wed Mar 1 16:16:23 1995
Received: (from majordom@localhost) by nacm.com (8.6.9/8.6.9) id QAA02432 for executor-outgoing; Wed, 1 Mar 1995 16:16:23 -0800
Received: from smtp.utexas.edu (smtp.utexas.edu [128.83.126.2]) by nacm.com (8.6.9/8.6.9) with ESMTP id QAA02427 for <executor@nacm.com>; Wed, 1 Mar 1995 16:16:21 -0800
Received: from mail.utexas.edu (mail.utexas.edu [128.83.126.1]) by smtp.utexas.edu (8.6.7/8.6.6) with ESMTP id SAA02772 for <executor@nacm.com>; Wed, 1 Mar 1995 18:13:12 -0600
Received: from Thommy.ots.utexas.edu (tplunk@slip-2-18.ots.utexas.edu [128.83.204.118]) by mail.utexas.edu (8.6.9/8.6.6) with SMTP id SAA13156 for <executor@nacm.com>; Wed, 1 Mar 1995 18:12:28 -0600
I have a class in Machintosh Assembly using Machintosh Assembly System.
Everything works decently, but the debuger. Is there a reason for this?
Where do I send a bug report? Is there another packages out there that
has an assembly debuger that works with executor/Linux? The Debuger
seems to work except the window to inset break points never comes up.
Thanks,
Travis Plunk
From owner-executor Thu Mar 2 07:49:51 1995
Received: (from majordom@localhost) by nacm.com (8.6.9/8.6.9) id HAA14514 for executor-outgoing; Thu, 2 Mar 1995 07:49:51 -0800
Received: from relay1.UU.NET (relay1.UU.NET [192.48.96.5]) by nacm.com (8.6.9/8.6.9) with ESMTP id HAA14509 for <executor@nacm.com>; Thu, 2 Mar 1995 07:49:47 -0800
Received: from sloth.swcp.com by relay1.UU.NET with SMTP
id QQyfil29932; Thu, 2 Mar 1995 10:49:45 -0500
Received: from iclone.UUCP (uucp@localhost) by sloth.swcp.com (8.6.9/8.6.9) with UUCP id IAA15565 for nacm.com!executor; Thu, 2 Mar 1995 08:50:52 -0700
Received: by mailhost (nextstep Smail3.1.29.0 #11)
id m0rkD1G-000YdkC; Thu, 2 Mar 95 08:42 MST
Message-Id: <m0rkD1G-000YdkC@mailhost>
Date: Thu, 2 Mar 95 08:42 MST
From: ctm@ardi.com (Clifford T. Matthews)
To: executor@nacm.com
Subject: Serial Number / Authentication Key status report
Sender: owner-executor@nacm.com
Precedence: bulk
Hi Folks,
We're a bit behind schedule getting the serial numbers and
authentication keys out. This was due to our problems with
Executor/DOS 1.99j and a new problem we found in Executor/Linux 1.99j.
The new problem is that student and educational serial number/key
pairs are not properly acknowledged in 1.99j. Instead you get a
message stating that the key does not correspond to the platform
you're using and as such it drops you back to demo mode. We've fixed
this in Executor/Linux 1.99k, but we haven't gotten E/L 1.99k out the
door yet.
We may not have all this straightened out until sometime this weekend.
Once all the code is tested and in place and our database has been
retooled, the new way of doing things should be much nicer.
In addition, we're working on some tools that will allow you to
download many fewer bytes when we release successive revisions. Right
now you have to pick up copies of files that haven't changed, or
haven't changed much, but in the future you'll be able to pick up some
binary diffs (considerably smaller than the old "transmog" files) from