It's been a long time since anyone has mentioned so many obsolete software
products in a single message. LOL
I can't help you out other than point out that the two memory standards
(DPMI and VCPI) pre-date Windows and *its* memory management and may never
be compatible. If they are compatible, great and good. It's an accident, but
a great accident. <g>
Wow ... what a blast from the past.
Quote:> Does anyone have tips for taming the operation of these two versions when
> running in a DVM under Windows 3.1? Here are the issues on an older (but
> much usable) 486 clocking at 133MHz with 64MB ram:
> FoxPro 2.0/LAN - uses VCPI as its memory managament interface. In native
> it starts fine in eXtended mode, using the 32MB of EMS being emulated in
> by EMM386. In Windows 3.1, however, no amount of EMS stated in the PIF
> will convince FOX.EXE that EMS is available to call FOXPROLX.EXE, so all I
> is usable free memory below 640K.
> FoxPro 2.6 - In native DOS is starts fine and allocates all available XMS
> its use. Calling FOX.EXE once again lets FoxPro determine that XMS is
> avaliable to run in eXtended mode and it in turn calls FOXPROX.EXE which
> exploits XMS. In Windows 3.1, however, if I allow any amount for XMS in
> PIF file settings, FoxPro 2.6 just ignores it and swallows up all the
> remaining XMS. My intent of course it to cap the amount of XMS FoxPro
> to a modest 8 or 10 MB.
> Any tips?
> On a side note, I try to run the same instances of FoxPro in a DOS box
> OS/2 WARP3. FoxPro 2.0/LAN can be taken off the table because it uses
> OS/2's DOS emulation only supports DPMI. FoxPro 2.6/DOS is another
> It will run in eXtended mode, but in this environment it refuses to use
> than 2Mb of the provided XMS, even though I state in the DOS settings that
> 16MB is available.
> Again, any tips? Or pointers to some reference information that discusses
> these configuration and tuning issues?