Hi, sorry, I do use QEMM but not PC-DOS. Well, I do. PC-DOS 3.30 because it was excellent working with 80s software! 😃
For modern things I do use MS-DOS 6.2x and Novell DOS 7.

Okay.. thanks I think 😀 .. I was thinking last night that I should try another version and boot off FDD with a local CONFIG.SYS and see how that goes. I'm wondering if it's a memory map difference in the PS/2 MCA systems ..or? Hmm. Still investigating.

I don't do a lot of gaming unfortunately. My 'thing' generally is messing around in C/C++, Assembler, Fortran, Pascal and COBOL, and running business apps to do things. Hence the need for QEMM9. We're all different, don't judge :>

Quite puzzling.

Hi again, sorry for the late reply!
No no, there's nothing wrong with using PC-DOS, it's very good!
The users over there at vcfed forums seem to use it quite often, I remember.
It's just that I have no clue how to help, because I'm on MS-DOS 6.22 rather. 🙁

That's because I have issues with concentrating myself on something and want to learn to operate at least one DOS "right".
That's why I limit myself to using just a few of them (I barely use legendary MS-DOS 5 because it lacks things like F5/F8 on boot up and doesn't know all external commands yet).

Best regards,
Jo22

PS: Helix Multimedia Cloaking has DPMI functionality, too and ships with a few small drivers.

Info: Re: DOS Memory maximization

It might be an alternative, maybe, if you just need DPMI and lots of conventional RAM.
It can be combined with QEMM, too. I can provide some example configurations.

Edit: There's also an ancient LIMulator called "Above Disc" that can provide LIM 4 EMS via chipset/386/swap file.
Version 4.0d might be compatible with MS-DOS 5/6 already.
For games it's not good, but for programming maybe..

Hi again. I've just checked, PC-DOS 7.1 is from 1999-2003 and QEMM 97 is from 1997 (obviously) ?
If so, then maybe QEMM/DOSDATA.SYS being older simply isn't aware of the internal structures of this PC-DOS yet ?
Or maybe there are patches of some sort ? 🤷
https://en.wikipedia.org/wiki/IBM_PC_DOS#7.10

Could reproduce the problem. Working fix for me was to run these steps:

• unopt (only needed if it is still in an optimize phase)
• optimize/nd (=No DOS up)
• Add parameter "BOOTENABLE:N" to the QEMM386.SYS line in the CONFIG.SYS (maybe not needed if you don't get an error about fastboot during booting)

Probably this problem is caused by the fact that newer PC-DOS versions also wants to put DOS in upper memory by itself.

You're Awesome! That's brilliant. Thank you!

P.S. Digging the Larry avatar. Made me smirk.

uridium wrote on 2025-01-31, 06:08:

You're Awesome! That's brilliant. Thank you!

You're welcome. 😀 Did you also needed to add BOOTENABLE:N to the config.sys?

No ..interestingly. Hmmm. *Frown*