🚀 go-pugleaf

In article <1991Jan30.050029.10638@bony1.bony.com> stevef@bony1.bony.COM (Steve Faiwiszewski) writes:
}
}I've been trying to use Spawno v2.0 which was posted on c.b.i.p a while ago.
}When linked to a program, Spawno allows spawning a dos shell while
}swapping the running program to XMS or to disk.  Two questions:

You probably want to get v3.0, which came around c.b.i.p about a month ago,
and adds EMS swapping while *reducing* the resident portion (down to 448
bytes for disk/XMS and 464 bytes for EMS).

}1) There are different object files supplied, one for each memory
}   model, except for Hugh.  Naturally, my application (using TC++)
}   requires the Hugh model since it has more than 64K of static data.  I
}   tried linking with the SPAWNVL.OBJ (for Large), but the linker
}   complains about "Group DGROUP exceeds 64K".  Is there any way around
}   this?

I did not include an OBJ for Huge model because of a fundamental difference
in segment layout compared to other models.  In Huge model, unlike any of
the other models, there is no BSS (uninitialized data segment), and there
are multiple near data segments (one for each module) requiring DS to be
reloaded by each and every function.  Maybe I'll incorporate the needed
additions in the next version, but don't hold your breath....

}2) My application also takes advantage of VROOM (overlays).  Does
}   anyone know if any incompatibilty problems between Spawno and VROOM?

While I haven't tried it, there should not be any problems if you use v3.0
(if VROOMM uses multiple DOS memory blocks, v2.0 won't quite work), as
SPAWNO writes out everything, calls the requested program, then puts 
everything back.



--
{backbone}!cs.cmu.edu!ralf  ARPA: RALF@CS.CMU.EDU   FIDO: Ralf Brown 1:129/3.1
BITnet: RALF%CS.CMU.EDU@CMUCCVMA   AT&Tnet: (412)268-3053 (school)   FAX: ask
DISCLAIMER?  Did  | It isn't what we don't know that gives us trouble, it's
I claim something?| what we know that ain't so.  --Will Rogers