Will someone please lay out a reasonable discussion of how the Expansion
Memory Fault error arises in PB 3.5?
Because of the size of the programs and the issues with OS/2 and so
so on I don't expect that it'll be demonstrable. However, in that
there are a very substantial number of switches and configuration
changes in OS/2 that can be applied to how upper memory is handled,
much like QEMM, it just might be possible I can do some good if I
only know enough to know where to look. In QEMM we had MPT and so
on to troubleshoot all of this stuff and curiously, it even works in
OS/2 DOS-VDM sessions if I recall right, at least for some of the things
one can debug.
I can understand a 'stable' error which shows up at some readily
visible 'limit' of this or that.
What I can't understand is why, of a half dozen programs all using
virtually the same libray modules and much of the same code, a
couple SMALLER ones will pop the error in the PB-IDE, yet LARGER
ones will not!
Nor do I understand why the PBC command line compiler will handle
all the compile jobs in question, including the SMALLER ones that
the PB IDE will not.
If someone will simply share the ways that this error can be popped
in the PB IDE, maybe I can debug the environment here. I'm not saying
in any way the PB is at fault, or anyone is at fault.
Thanks ..
------------------
Mike Luther
[email protected]
Memory Fault error arises in PB 3.5?
Because of the size of the programs and the issues with OS/2 and so
so on I don't expect that it'll be demonstrable. However, in that
there are a very substantial number of switches and configuration
changes in OS/2 that can be applied to how upper memory is handled,
much like QEMM, it just might be possible I can do some good if I
only know enough to know where to look. In QEMM we had MPT and so
on to troubleshoot all of this stuff and curiously, it even works in
OS/2 DOS-VDM sessions if I recall right, at least for some of the things
one can debug.
I can understand a 'stable' error which shows up at some readily
visible 'limit' of this or that.
What I can't understand is why, of a half dozen programs all using
virtually the same libray modules and much of the same code, a
couple SMALLER ones will pop the error in the PB-IDE, yet LARGER
ones will not!
Nor do I understand why the PBC command line compiler will handle
all the compile jobs in question, including the SMALLER ones that
the PB IDE will not.
If someone will simply share the ways that this error can be popped
in the PB IDE, maybe I can debug the environment here. I'm not saying
in any way the PB is at fault, or anyone is at fault.
Thanks ..
------------------
Mike Luther
[email protected]
Comment