🚀 go-pugleaf

In article <92094.143457U30471@uicvm.uic.edu> <U30471@uicvm.uic.edu> writes:
>  I'm developing an application in borland c++ 3.0.  I want to use
>overlays, and i followed all the instructions in the manual, and i
>get an overlaid module, but i am not sure of one thing.  The manual
>never states how the compiler breaks the program up into modules.  I
>have assumed that it breaks them up on the .obj file level( each
>.obj file being one overlay ) but later it states that more than
>one overlay segment may be created from one source file.  So
>which is it?!?  How do i tell the compiler which module is WHICH?
>
>  Thanks!
>
>
>--DAVE!!!

I just started using VROOOM overlays this week also, and have found
the Borland documentation severely lacking.  I went to the Computer
Literacy Bookstore to see if I could find any helpful info in any
Borland C books, but the only thing I could find was a chapter in
"Using Borland C++" (or something similar) which basically said exactly
what the documentation said but in different words.

If anyone out there has used overlays and has any helpful information
on setting a proper buffer size, swapping to EMS or XMS, or anything
at all related to VROOMM, I'd be very grateful (and I think DAVE!!! would too).
Also, if anyone can recommend any sources of information on VROOMM, that'd
be great.

One semi-helpful thing I've found is the map file generated by the linker.
It will show you the different segment labels and their code lengths,
which I assume could be handy in setting a good buffer size.

Surely someone has done this before :-)....

Lilly Tao	
ltao@netcom.com
GRiD Systems Corporation
Fremont, CA