Received: from smtp-gw01.ny.us.ibm.net (smtp-gw01.ny.us.ibm.net [165.87.194.252]) by nacm.com (8.6.10/8.6.9) with SMTP id DAA07369 for <Executor@nacm.com>; Thu, 6 Jul 1995 03:38:52 -0700
Received: from slip7-144.fl.us.ibm.net(129.37.7.144) by smtp-gw01.ny.us.ibm.net via smap (V1.3mjr)
id smaj8QDFW; Thu Jul 6 10:38:38 1995
Date: Thu, 06 Jul 95 06:36:07 EDT
From: rrs0030@ibm.net (Steve Sinnott)
Reply-To: rrs0030@ibm.net (Steve Sinnott)
To: Executor@nacm.com
Cc: bugs@ardi.com
X-Mailer: PMMail v1.1 UNREGISTERED SHAREWARE
Subject: E/D 1.99n & OS/2 failure
Sender: owner-paper@nacm.com
Precedence: bulk
I think the new version may have killed off OS/2 support. I'm trying at work right now, and I've tried it on 2 machines without success. Both failed with:
This occurs immediately after running. It switches to a Dos Full-screen, changes video mode, then goes back to OS/2 Workplace Shell. It doesn't seem to matter if there is a disk in A: or not, or even if it's Mac or Dos formatted.
Executor -info reports:
This is Executor version 1.99n, compiled Tue Jul 4 19:56:10 MDT 1995
CPU type is 80486 or better.
Unable to determine free DPMI memory.
Choosing 1.17 MB for applzone, 0.50 MB for syszone, 0.25 MB for stack
VESA-compatible video driver detected, VBE version 2.0
This is on a pair of 486-DX/2 66Mhz, 16 megs ram, 540 Mb HD (formatted HPFS on one, FAT on the other), and a Cirrus-Logic PCI video card (1 meg, 24-bit RAMDAC), running OS/2 Warp (not Connect). I have installed Univbe51, since the card has VESA 1.2, apparently (tried it without it, though). OS/2 is set up for 1024x768x256, if that matters.
Note that I have tried the different switches, mainly -applzone 2048, -applzone 4086, -stack 768, -syszone 1024, as well as variations and combinations thereof (about 30+) (Yes, I've been doing this for a couple of hours. Slow day). If I set -bpp 1, it changes the ebp=0001c147c and esp=001c108c only, so I assume that those are requested bit & screen values.
I have also tried varying the OS/2 application settings for the Dos window, including 8514_XGA_IOTRAP, mode restrictions, XMS memory, EMS memory, DPMI settings, etc, without success. Mainly I'm doing variations on the values in the FAQ (since that part seems very familiar <G>). I have also tried cleaning out the autoexec.bat, and going clean. I'd rather not try cleaning the config.sys yet.
I should have more information in a few hours when I try it on my standard (home) machine. These machines are using 3 different network protocols, etc, and theoretically that could interfere with Executor, but it hasn't in the past. I'll see what happens at home, and report back. Meanwhile, if anyone has any ideas, or if ARDI wants me to try anything specific (such as helping them to install their copy of Warp), let me know.