🚀 go-pugleaf

In article <559@shograf.COM> jim@shograf.COM (jim morris) writes:


   From article <1545@tekig7.MAP.TEK.COM>, by alanr@tekig5.PEN.TEK.COM (Alan N Rovner):
   > In article <11880003@hpdmd48.boi.hp.com> pfulghum@hpdmd48.boi.hp.com (Pat Fulghum) writes:
   >>
   >>Has anybody had any luck getting bcx and 386MAX 5.0 or 5.1 to work together.
   >>
   >>I run 386MAX 5.1 and when I run bcx my machine reboots!!
   >>
   > 
   > I have tried this too, and while my machine doesn't do anything drastic like
   > reboot, I do get an error message about an incompatible memory manager
   > is installed.  I guess BCX incorporates its own DOS extender or memory manager
   > that's incompatible with 386^max.

   Well this is STRANGE...
   I have 386MAX 5.1, and when I run BCX it runs fine, it even manages to use
   VCPI to get the Expanded memory 386MAX is managing, and convert it to
   extended, (At least the get info says I have 4Mb when I have only
   reserved 700k extended memory).

   . . .

Even without any fancy memory manager like 386^MAX, bcx seems to consistently
crash my machine. The setup: Northgate 486/33 w/ 8 megs, standard Windows/
Himem/Smartdrv, no interesting TSRs. If I go into bcx and rearrange or add
editor windows, I am almost guaranteed to quickly die with a global protection
fault. Something (the DOS extender, I assume) issues some messages about not
being able to remove TKERNEL.EXE (this is bcx's memory manager) and then
either locks up the machine (sometimes beyond even the reach of the
three-finger salute) or leaves it with no available application memory. Does
this sound familiar to anyone?

Pat