Chuck Guzis wrote:
That's the approach that I'd take--except
I'd have the first one
write a temp file with all of the initialzed goodies and have the
second one read it in. It's dirty, quick and modular--and maybe
easier to debug.
Hey, pretty clever. Or, to save using disk as temp space, just have the
init program leave all that info in memory and pass the seg:ofs of the
struct to the 2nd portion of the code. If one chains to the other,
there's no fear of the data being overwritten.
--
Jim Leonard (trixter at
oldskool.org)
http://www.oldskool.org/
Help our electronic games project:
http://www.mobygames.com/
Or check out some trippy MindCandy at
http://www.mindcandydvd.com/
A child borne of the home computer wars:
http://trixter.wordpress.com/