🚀 go-pugleaf

Is anyone out there using Logitech 3.0 for large-scale development
projects ?

We have run into a fairly major problem with this product.
To wit, having compiled some 157 source modules, we then try to
link them together with m2l and receive the not-so-informative-as-
it-might-be message :

        FATAL Error: insufficient memory to link the program
        => heap overflow

This is compiling with /NOSYM, /O+ and a host of other options
that could conceivably reduce memory usage.  (The size of the
linked program is of the order of > 400k).

The point is, this all used to work with Logitech 2.0.  The irony
is that the super new Logitech linker, which is supposed to be able
to reduce memory consumption by not linking procedures that are
never called, does not seem capable of handling large programs.

Our guess is that m2l tries to build the executable image entirely
within main memory and fails.  The old linker was presumably
intelligent enough to build the image on disc.

The response from Logitech technical support, by the way, is
"to use overlays".  This, however, is not too easy in our particular
application that makes intensive use of multi-tasking, interrupts
and the like.

Has anyone run into the same problems ?  Is anyone using the rumoured
to exist Logitech 3.03 system ?  (If so, what are the bug fixes ?)

All information will be received most gratefully,

Cheers,
        - R.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    J. Robert Ward,
    Olsen & Associates, Seefeldstrasse 233, CH-8008 Zuerich, Switzerland

Tel.:       +41 1 552224
Bitnet:     robert%olsen.UUCP@cernvax.BITNET
Uucp:       ... {uunet,ukc,mcvax ... }!cernvax!olsen!robert
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~