Windows 3.11 EMM386 error

April 20, 2011 at 07:24:22
Specs: Windows 7
Hello, I want to install Windows 3.11 on my USB, so I successfully installed MS-DOS 7.1 (I know, that Windows 3.1 can run under DOS 6.22, but I want FAT32 support, so I installed 7.1). Then I installed Windows 3.11 on it, but when it was going to boot, it showed me an PageOverCommit error, so I added line PageOverCommit=1 to system.ini and NOEMS line to config.sys. Now when I am trying to boot, it is showing me a bootscreen twice, but then MS-DOS prompt appear (C:/), and when I wait for while, it is showing me an error: EMM386 has detected error #o3 in an application at memory address 00B8:0BB4. To minimize the chache of data loss, EMM386 has halted your computer. Dor more information, consult your documentation. To restart your computer, press Enter. Then my computer freeze. Please, can someone help me solve this problem? Thank you for your answers :)

See More: Windows 3.11 EMM386 error

April 20, 2011 at 08:43:21
The latest DOS version compatible with Windows 3.11 was DOS 6.22. DOS 7.1 is not supported. I expect that is at least partly responsible for your problem.

Report •

April 20, 2011 at 12:31:47
Make sure that in CONFIG.SYS you are using the DOS versions of of both HIMEM.SYS and EMM386.EXE.



Also consider experimenting with UMBPCI.SYS in place of EMM386.EXE.

It all depends if your chip will accept it. Check the list on that link - most chipsets work. Since you are installing to a removable USB device, you are not guaranteed it will work on any machine you plug into.

UMBPCI is the same as turning off expanded memory with NOEMS - but it does the same thing much more effciently.

PageOverCommit errors occur when there is a memory conflict.

A USB stick is basically a RAMDISK, so I cannot see that having a FAT32 system is going to give you any more noticeable faster disk access. You would get more files on to the stick, but how many 16 bit (or win32s) programs do you intend to install into that drive?

Report •

April 20, 2011 at 18:03:28
try to exclude the range of 00B8-00B9 in your EMM386 line

Report •
Related Solutions

Ask Question