Hm. You could save your autoexec.bat/config.sys and start MemMaker.
It supports Windows 2.x/3.0/3.1x and after it did the optimizations, you can restore your old files.
After this, Windows should behave better. I tried this in order to make Windows 2.03 and 3.0 (Real-Mode) aweare of EMS..
If that doesn't work, I'd give Qemm7 or that Helix program a chance.
PS: Do you have got an ethernet card installed ?
- If yes, please make sure it isn't using the region of memory (UMA) that Windows tries to use.
Edit:
noshutdown wrote:i have a question here:
Microsoft Windows version 3.1, in both standard and 386 enhanced mode, allocates the memory that it uses from the XMS driver.
The only exception occurs when you run Windows in standard mode because standard mode Windows can allocate memory from a Virtual Control Program Interface (VCPI)
provider (server) or a DOS Protected Mode Interface (DPMI) provider. Please note that standard mode has this capability, but 386 enhanced mode does not.
since dpmi is faster than xms, does this mean that standard mode is faster than 386 enhanced mode?
Not sure if I can answer this, but..
a) Yes, Standard Mode is usually quicker in practice. It is favoured by Windows 3.1 if it is being run on a 386 class computer that is low on memory (less than ~2MiB).
b) OS/2 also had got a special version of Win 3.x (Win-OS/2) that was an DPMI client instead of a DPMI host. That way, it could bypass the XMS interface.
c) There are two Standard Modes in Windows 3.1x (non-WfW). One uses the kernel286/dosx on 80286 PCs, the other one uses kernel386, but without all the virtual stuff (VXDs, swap file etc.)
d) Enhanced Mode of Windows contains the analogue of EMM386. That's why it has trouble in coexisting with other memory managers (those from EMS cards etc).
Except with those that are Windows-aware or provide APIs that Windows can use to get its memory from.
- The core issue is that memory managers do take control of Protected-Mode (V86) and thus Windows can't take over. It has to cooperate with them somehow.
Edit:
"Standard Mode" refers to an operating mode of Windows. On a 286 it uses krnl286/dosx and 16-Bit Protected-Mode (no V86, 64KiB segments), on 386+ it uses krnl386 and 32-Bit Protected-Mode.
"386 Enhanced Mode" refers to an operating mode of Windows. It uses 32-Bit Protected-Mode with V86 and Paging (4KiB segments).
"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel
//My video channel//