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

E/D 1.99k needs a mouse driver + memory issues



Hi Folks,

Executor used to be polite when you tried to run it without a mouse.
It would tell you that it required a mouse and then exit.  However,
due to a bug in 1.99k (and probably in 1.99j and 1.99i, as well),
Executor is much less polite.  If you try to run it without a mouse
driver you'll just get a register dump.

I believe this may be one reason why Executor has run in a DOS box on
some OS/2 systems but not others.  If Executor dies upon startup in a
Windows or OS/2 DOS box, you may want to check to see if there is a
mouse driver that you can run, prior to running Executor.  The
built-in Windows and built-in OS/2 mouse drivers are *not* used by
Executor, so don't be lulled into a false sense of security.

If you have only 4 MB RAM in your PC, you will probably have to not
run a disk cache (like Smart Drive) when running Executor.  Lately
we've been working on Executor/DOS's memory footprint since we once
again have a 4 MB machine that we can test on.  The first thing we
noticed was that our disk cache had to go.  Most of the other
observations are things that we can do better in future versions of
Executor to squeeze more bytes out of systems with less memory.

As I've mentioned before, I'm about to leave town for ten days, but
everyone else (Vaune, Mat, Cotton and Bill) will still be here, so as
long as your e-mail is sent to one of our aliases and not to me
directly, things should run smoothly in my absence (perhaps *too*
smoothly and they won't take me back).

	--Cliff
	ctm@ardi.com


Follow-Ups: