VOGONS

Search

Common searches

Memory management problem

Topic actions

First post, by Timbi

Posted on 
User metadata
Rank Newbie
Rank
Newbie

All three samples share same HDD image, I wish I could set the 86Box/PCem to make the memory management similar to how it is done in DOSBox X.

Config.sys
DEVICE=C:\WINDOWS\HIMEM.SYS
DOS=HIGH,UMB
DEVICEHIGH=C:\WINDOWS\EMM386.EXE RAM
DEVICEHIGH=C:\WINDOWS\COMMAND\DRVSPACE.SYS /MOVE
DEVICEHIGH=C:\WINDOWS\COMMAND\DISPLAY.SYS CON=(EGA,,1)
COUNTRY=048,852,C:\WINDOWS\COMMAND\COUNTRY.SYS
devicehigh=C:\WINDOWS\cwdinit.exe /A
FILESHIGH=25
LASTDRIVEHIGH=F
BUFFERSHIGH=30
STACKSHIGH=9,256
FCBSHIGH=4

Autoexec.bat
@ECHO OFF
PROMPT $P$G
PATH=C:\;C:\NC;C:\WINDOWS;C:\WINDOWS\COMMAND
SET BLASTER=A240 I9 D3 T4
LH MODE CON CODEPAGE PREPARE=((852) C:\WINDOWS\COMMAND\EGA.CPI)
LH MODE CON CODEPAGE SELECT=852
LH KEYB PL,,C:\WINDOWS\COMMAND\KEYBRD4.SYS
LH SMARTDRV.EXE C 1024 512
LH MOUSE.COM
LH NC.EXE

Testing done with command mem /c /p
config:
16MB of RAM
Pentium 1 90MHz
All the shadowing is off in BIOS in 86Box/PCem

In DOSBox X the high memory seems to be better managed, most of drivers is loaded to high as expected. I'm hoping I can configure the rest to work similar to this. Loading some games as Bumpy with insufficient lower memory results with heavy display artifacts. Even though I can run the game after unloading some of the drivers, I wonder if it is possible to keep it clean and nice as in DOSBox X.
I know I'm not using other tools to manage memory right now, but it seems the problem is in the settings I cannot figure out.

The language is not English but I'm sure it is intuitive enough.

Attachments

  • results.jpg
    Filename
    results.jpg
    File size
    332.5 KiB
    Views
    722 views
    File license
    Public domain

Reply 2 of 5, by Disruptor

Posted on 
User metadata
Rank Oldbie
Rank
Oldbie
Timbi wrote on 2023-11-13, 09:52:

I beg for help. Anyone? My post was very polite.

If you do not need EMS, try to replace "RAM" in CONFIG.SYS' EMM386 line with "NOEMS".
Try to create a boot menu for the configurations where you really need EMS.

And try to get rid of DRVSPACE. I'm sure you won't need it.

And, why do you have so few UMB?
It looks like 18 KB (+64 from EMS page frame).
Check for more usable upper memory areas with MSD.
Try to include them with I= settings.

Reply 3 of 5, by Gmlb256

Posted on 
User metadata
Rank l33t
Rank
l33t

86Box and PCem attempts to make a more accurate representation of computers than DOSBox (and DOSBox-X which is a fork). The emulated Socket 7 motherboard should normally have the region C800-EFFF available for UMB and the EMS page frame, provided that a period correct video card was selected.

As Disruptor said, try to include them with I= parameter in EMM386 and if you don't need EMS at all then add NOEMS as well to obtain more UMB.

VIA C3 Nehemiah 1.2A @ 1.46 GHz | ASUS P2-99 | 256 MB PC133 SDRAM | GeForce3 Ti 200 64 MB | Voodoo2 12 MB | SBLive! | AWE64 | SBPro2 | GUS

Reply 4 of 5, by weedeewee

Posted on 
User metadata
Rank l33t
Rank
l33t
Timbi wrote on 2023-11-13, 09:52:

I beg for help. Anyone? My post was very polite.

After reading your post. I guess your question is, why is the amount of free memory so lacking in pcem and 86box? .

To which,
i guess,
the simplest answer would be
86box and pcem emulate a real computer, dosbox-x emulates an optimized dos environment.

Right to repair is fundamental. You own it, you're allowed to fix it.
How To Ask Questions The Smart Way
Do not ask Why !
https://www.vogonswiki.com/index.php/Serial_port

Reply 5 of 5, by Timbi

Posted on 
User metadata
Rank Newbie
Rank
Newbie

Thanks for your answers, I will try these techniques to see what can be done to give it shape.

Disruptor wrote on 2023-11-13, 13:02:

Try to create a boot menu for the configurations where you really need EMS.

Yes, it is good idea, but I have already menu with DOS CD, DOS [EMS] and WINDOWS. I will add NOEMS option soon.

weedeewee wrote:

why is the amount of free memory so lacking in pcem and 86box? .

From now on, I fixed the problem partially by changing machine type to Super Socket 7 with ASUS P5A. I'm guessing that its newer BIOS allows to have more memory.

I also changed mouse driver to newer version (also Microsoft) mouse.exe. mouse.com seemed to produce memory conflicts specifically for PCem and 86box, but not with DOSbox, I don't know why, but

dosbox-x emulates an optimized dos environment.

might be the answer here.

Here is how it been with the old mouse driver mouse.com
I couldn't load mouse.com driver together with mode codepage and keyb and ncmain. If I excluded one of these, the game worked fine and it seems like low bottom memory wasn't the case, but memory errors caused by the mouse driver (but it was fine in DOSBox with the same driver).
I have included picture how the game looked on VGA. With EGA it was black and red.

It is now solved and I hope this topic will help the other people, who will encounter same problem.

Attachments

  • with mouse.jpg
    Filename
    with mouse.jpg
    File size
    126.49 KiB
    Views
    553 views
    File license
    Public domain
  • works.jpg
    Filename
    works.jpg
    File size
    138.77 KiB
    Views
    553 views
    File license
    Public domain
Go to top of page Go to top of page
Back to DOS
Close window
Close window