QEMM Problem

Fic / Vb-601 version mi415
January 22, 2009 at 22:00:45
Specs: DOS/Windows98, PII-MMX 450MHz/512MB SDRAM
I installed QEMM97 recently. It works great, but I got some problems with the memory amount...

I only used this:

Thus it can safely provide about 124KB upper memory. However, somehow only 14MB EMS/XMS is available to the system (even using only RAM parameter)... When I entered MEM to check the memory amount, it only shows 15MB total RAM (When the QEMM is loaded, it says "Total memory available to QEMM: 14976K")...

I don't know where did the other 497MB RAM go... Did QEMM just reserved them from being used, or otherwise, they can still be used but are not displayed?

Besides, I'm not using QEMM when using Windows 98 because it will tell me that the program executed an invalid instruction (Probably because of this), thus the memory amount displayed in Windows 98 is not affected. Does this mean that QEMM only supports small amount of RAM(16MB, 32MB, 64MB), and will reduce the memory amount displayed when loaded with large RAM?

EDIT: I just discovered that the first problem was caused by the Memory Hole at 15M-16M. I disabled it, and now the total available memory for QEMM became 66472K... It can now recognize 65MB memory, but it still cannot recognize all the memory.

See More: QEMM Problem

Report •

January 23, 2009 at 00:01:37
what version qemm are you using? it looks like you ae using a version that only support xms2 specs. use a later version that is capable of xms v3.0 to see ram greater than 64mb.

Report •

January 23, 2009 at 22:07:34
QEMM97 (v9.0). I don't know if there's ever a better version that supports XMS3...

Actually, although it restricts DOS memory usage to 64+1MB, a lot of programs seems to be running more stable... (Actually, AFAIK, only QEMM and Helix's RM386 can provide 64MB EMS. Others, though didn't affect the total XMS, can only provide 32MB EMS)

For example, some old games like Corridor 7 (CD Version) only seems to be fully playable when using QEMM (The game crashes when playing videos when I load other extenders like JEMM), although it shows "Out of Memory" when trying to exit the program in-game, it doesn't affect in-game playability...

Maybe QEMM only supports XMS2 specs in DOS... It doesn't affect Windows programs, but they seem to work faster, and it provides additional RAM (Though MagnaRAM seems to drop down to zero if the physical memory is still enough, it can make my total RAM amount reach up to 545MB)...

I think it can be safe enough to use only RAM and ST:F parameter for QEMM to reach its best performance (For me, ST:M may cause screen mess-ups, though it can provide up to 180KB upper memory)...

Also, due to some reasons, the address D200-D3FF was used by system (I found it when loading JEMMEx), thus other memory managers, cannot claim as much as the amount of UMB it used to have...

Report •

January 24, 2009 at 08:24:51
that is an interesting setup. i tried qemm but was not really successful with it. i just use himem.sys from win98 and umbpci. if i need EMS i use emsmagic.com. i never had much use for emm386.exe anymore except when i use my sbpci soundcard.

Report •

Related Solutions

January 26, 2009 at 17:11:24
Use the program OPTIMIZE.EXE from QEMM and try , its like a MEMAKER from DOS , solve lost of problems ..

Report •

January 28, 2009 at 21:48:29

It was what I wrote at the first post. If this program was loaded (configured by using QEMM Control Panel in Windows) into Windows 98 the system will crash and tell me that the system executed an illegal instruction... This happened when I tried to boot when OPTIMIZING a Windows configuration.

When I tried to play Corridor 7 (CD Version)... it must be loaded with QDPMI to be played properly... If not, it crashes with Illegal Instruction. However, if QDPMI is loaded, some programs including Borland C++ 3.1 will crash... (Large games like Quake can only work without QDPMI, or it will say Out of Memory)

Yeah, whatever I do there will always be programs that will crash.

And besides, in order to boot both DOS and Windows I created multiple configurations. Using OPTIMIZE... I don't know if it supports multiple configurations that make it easier to recover if failed... (AFAIK QEMM Control Panel Optimize Settings support multiple CONFIG.SYS configurations)

I'm also wondering that if it was possible to integrate a XMS3-complaint XMS memory manager into QEMM. QEMM disallows other XMS memory manager loading probably because it has a built-in loader that is only XMS2-complaint(64MB)

Report •

January 29, 2009 at 23:26:06
that is really odd. isn't there a commandline option to enable xms3?

Report •

January 31, 2009 at 19:43:11
or try http://www.emsmagic.com/screens

Report •

February 6, 2009 at 23:43:22
Something strange happened since I replaced a better motherboard...

I installed 2x128MB SDRAM on that new motherboard and when it boots, QEMM loads a bit longer, saying that "Total memory available to QEMM: 261696K".

I don't know if BIOS affects the amount of RAM QEMM can recognize... Although when I use MEM to check the RAM amount it still displays 64MB XMS, it actually reads all the 255MB XMS and it produces 255MB EMS (AFAIK no other EMS manager can create such a big amount of EMS).

QEMM is really a complex thing... The new motherboard has an AWARD BIOS 6.00PG while the old one is an AWARD BIOS 4.50PG, and now it results different...

Report •

February 24, 2009 at 18:42:57
When I was on Dos I had Qemm version 8.0 and in one of Qemm's manuals it had a "switch" you added to the Config.sys that allowed you to access memory over the amount it would normally allow. Does anyone know what command was that was added to the Qemm386.sys line in the Config.sys file?
I loved Qemm but in these newer computer systems with megs and megs of ram memory I could hardly get it to work and I could NEVER get it to acknowlege the higher amounts of memory. I had a program called Autodesk Animator Pro that used memory in a different way (I think it was called Pharlap, or someting like that) and whenever I tried to access Autodesk Animator Pro with the "Qemm386.sys /ram" line added to the config.sys mycomputer would re-boot on me. Would LOVE to get that problem resolved.

Report •

April 14, 2009 at 05:27:39
It's a long time...

Since I updated my motherboard into a new one, EPoX 8KTA3PRO with an AMD Athlon XP processor (due to some other problems in that old Tekram board) and installed 2 x 512MB SDRAM (so I have 1GB)... I got another problem.

Whatever I do, QEMM can only recognize about 256MB of XMS. Using its USERAM won't work. As FreeDOS' MEM.COM can view all the memory, the other 768MB were reserved as Used.

PS, if I use SETXMSTO with QEMM it will say function 2F4309 is not supported. That means QEMM cannot support the standard of HIMEM 3.09+ or it works in a different way, according to XMSDSK manual... it seems that QEMM only matches the standard of 256MB XMS...

Also, I found it's still allowed to load a XMS manager before QEMM386 but it will become useless as QEMM's XMS management is prior to your XMS manager.

There's something strange: If you set USERAM parameter in KB, like USERAM=524288, USERAM=786432... you'll find that you will get less XMS than usual. Usually you'll find that you'll get less XMS if you use a value higher than or equal to 524288.

And I'm wondering if there have ever been an EMS manager that beats QEMM... with all its functions and better compatibility. QEMM bears a lot of incompatibilities, though nearly all today's disk caching software works in its UMB. And QEMM only works in MS-DOS. It won't load in ROM-DOS and FreeDOS Kernel 2036 (Only shows an intro screen with your registration information but it doesn't actually load into memory and function), and it will crash immediately after loaded in FreeDOS Unstable Kernel 2037 even without loading any drivers after that. I have reported this to FreeDOS bug tracker recently.

So... if anyone have discovered a way to break the 256MB XMS barrier... post it down here.

EDIT: There's no use. You can crash your computer immediately, if you load a XMS manager, set a ramdrive as large as the reserved space in the top part, and then load QEMM386.

Maybe this can ring a bell: QEMM can only provide 255MB of EMS, and the amount of available XMS must be the same amount as the EMS, so it automatically reserves the memory after 256MB prior to everything, so the QEMM386 only detects 256MB total memory. Once I find JEMM386 good, but soon I find it can only provide the exact same amount of UMB as regular EMM386 (generally it should provide 63KB with EMS, but since A300-A7FF, probably, is used as Adapter RAM, it's not accessible and can only provide 48KB, which ended up my FreeDOS boot with EMS only has about 540K conventional memory), and its FASTBOOT function is not very compatible with my EPoX 8KTA3PRO that can cause my computer to crash. I cannot use UMBPCI on that AMD chipset board since it cannot support ISA-DMA and PCI busmastering, which forced me to put those network and caching drivers which cost about 60-70K conventional memory. into low memory area.

Report •

June 7, 2009 at 01:23:43
You can also try using the ExDOS 2009 software. One of the things it fixes is the whole memory issue. They have a nice memory manager module.

Report •

July 14, 2009 at 04:22:30
But the thing is, can ExDOS be used on real DOS?

Actually I had a computer that is used for modern programs and with only Windows XP installed. It can be helpful if I use it there. But I don't think it can be helpful for real-DOS environments...

I don't know whether some current DOS EMS managers such as JEMM386, FreeDOS' EMM386, can support those things in the future... (I'm not thinking about Datalight's ROM-DOS since QEMM won't load on that system, and FreeDOS will crash after loading it if I install the Kernel 2037, and it won't load in current Kernel 2036)

Also, the QEMM seems to format the first 255MB XMS if loaded in a MS-DOS compatible OS when loading it into memory. (Unformatted area will be reserved and will not be seen by the system itself, but things like FreeDOS' MEM could still report all the XMS since they're actually there even they were reserved.) It then puts the system into some kind of protected mode that only allows the data being read from or written to the formatted XMS area and will result in error if data was accessed to XMS outside the formatted area, or will result in reboot if a program that requires EMS accesses XMS area (Actually only 32MB EMS are real, and the rest are simply XMS but can be used as EMS... but somehow the QEMM would sometimes reboot the computer without warning if the XMS area is accessed instead of the real EMS area).

That seems to be why Windows 98 cannot be loaded when QEMM is loaded, and things like Creative's SB16 Emulation program would result in rebooting the system without warnings...

Report •

Ask Question