Mail Archives: djgpp/2011/05/12/15:42:43
As I write this I'm still scanning the FAQs and docs for the answer. I installed Ver 1.12 so I could experiment with Desqview/X development stuff. I think I have everything configured correctly as suggested from various docs and sources. So I"m running out of memory during the linking phase.., this was not an issue with V2.03 even though I would never be able to get a successful completion. I have plenty of resources to work with here, so what's the deal?
Q: So, what in my environment have I not configured correctly now that I"m using go32? I have tried to compile ~\demos\Xeyes inside and outside DVX. I get the same result (memory exhausted) during linking.
I have a good install and ~\samples\Hello.c compiles just fine with "tryit". I've a Dell Latitude Cpia with 128Mb ram to work with. The following environment statements are in place.
QEMM is configured as suggested with DOS partially high. I've got 634k before running DVX and 565 with DVX loaded. About 5k conventional left over. Everything is loaded high. (VCPI=123,000+/- k) I have plenty of Extended and Expanded (pooled), but no high ram available when in DVX. It is supposed to be fully allocated, I think.
2MB ramdrive on G:\tmp
4MB disk cache with smartdrv
I'm just looking for a successful X Client compile so I can move forward with programming. So.....,
Q: When do I have to have QDPMI configured, if at all using V1.12.
Q: Do I have use go32 to compile V1.12 protected mode programs, or both (compile and run) even though I am using QEMM?
Since I am using QEMM97 & DVX, I'm trying to understand when I have to use one or the other. Please set me straight on this. It will help me clear up these uncertainties.
Thanks.
jw
- Raw text -