[Prev][Next][Index][Thread]

1.99q7 released, fixes (hopefully) floppy + CD-ROM problems



Mat posted this to the Executor Interest and Executor Announce mailing
lists earlier today.  We just discovered that our gateway from the
Executor Interest mailing list to comp.emulators.mac.executor
newsgroup has not been working since early January.  Oops.

Here's Mat's message:

Subject: ANNOUNCE: 1.99q7 is released
Date: Wed, 28 Feb 96 14:32 MST

1.99q7 is a "bleeding edge" update for 1.99q.  You must already have
1.99q or later installed before you can install the 1.99q7 upgrade.

1.99q7 is now available in the subdirectories of
ftp://ftp.ardi.com/pub/BleedingEdge/ and its primary mirror,
ftp://vorlon.mit.edu/pub/ardi/BleedingEdge/.  Other mirror sites will
pick it up within the next few days.  Once most mirror sites have
1.99q7, we'll update our WWW pages so you can download 1.99q7 directly
from the ARDI web site.

New in 1.99q7:

        - Numerous disk problems are fixed, mostly under DOS.
          Floppies, CD-ROMs, and SCSI devices are all affected by
          these fixes.  Hopefully users that needed "-nosound" to
          access floppies reliably will find that is no longer
          necessary.
        - Obsolete command-line arguments have been removed.
        - A bug forcing some Executor/Linux users to use
          "-checknet 0" has been fixed.
        - More printing bugs are fixed.
        - We eliminated performance slowdowns introduced in 1.99q6
          (graphics and floating point).
        - We fixed a cursor bug preventing OpenProlog from working.
        - Executor now chooses better default memory settings for
          OS/2 Warp users.
        - Executor now avoids SoundBlaster-related hangs that were
          causing trouble on some systems.

In addition, DOS users can now say:

executor > crashlog

and, if Executor crashes, the traceback information will get written
to the file "crashlog".  No more worrying about that information
scrolling off the screen!  Emailing such traceback information to
bugs@ardi.com may help us track down why Executor crashed.

As always, we appreciate feedback.  We are especially interested in
feedback pertaining to disk access problems under Executor/DOS.

--Mat