[Prev][Next][Index][Thread]
Executor/DOS 1.99j BUGS
Hi Folks,
Executor/DOS 1.99j has major problems on some machines. There appear
to actually be at least two causes of trouble.
One problem is the new memory autodetection code can cause problems.
You can get around this bug by always specifying "-applzone" (note,
there is no "e" between the "l" and "z", because it stands for
Application Zone, not Apple Computer Zone) option.
executor -applzone 4096
will dedicate 4 MB to a section of memory that your programs will see
as the amount of memory the "Mac" on which they're running has
allocated for them. (Internally, we'll use more than 4 MB, because we
also have to have memory for our synthetic CPU, the graphics routines,
translation space, misc. buffers, and so on). We're looking into
what circumstances cause our new autodetect code to fail.
If that workaround doesn't help you, you may find that running
Executor from a DOS shell under Windows will help you. Something we
are doing around the time when we're checking out which disks you have
on your machine appears to have difficulties with "cwsdpmi" the free
DPMI provider that we're using. If you run under Windows, you get
Windows as a DPMI provider and the bug does not appear. We're working
with cws to find out whether it's a cwsdpmi bug or whether it's our
bug that just happens to only show up under cwsdpmi.
I apologize for the inconvenience. I personally spent many hours
testing E/D 1.99j before shipping it off and making the announcement.
However, I didn't turn a copy over to Vaune Fischer, our wonderful
technical support person, because it seemed to work so well and I knew
that we desperately needed a 1.99h replacement. One of the machines I
normally do testing on over here is away being repaired and another
one was in the process of getting groomed to be our FTP/WWW server.
It's always something.
I'll send more e-mail as we make progress.
--Cliff
ctm@ardi.com