What's in your CONFIG.SYS / AUTOEXEC.BAT ?
What is the output of MEM /C /P ?

Uhh...try MEM to see how much memory you have free and look at the largest MS-DOS program you can run. If not enough, you could edit you config.sys and autoexec.bat files, add EMM386.EXE to config.sys and load the drivers high. IIRC, DOS has a program called MEMMAKER.EXE that will do these for you. I heard Win98 comes with this program, but it's not automatically installed. Maybe someone else here can tell you where it is. If that doesn't give you enough memory, try Googling and downloading and installing QEMM97 and running its OPTIMIZE program.

Harry Potter wrote on 2024-07-04, 14:05:

add EMM386.EXE to config.sys and load the drivers high. IIRC, DOS has a program called MEMMAKER.EXE that will do these for you. I heard Win98 comes with this program, but it's not automatically installed.

A good manual configuration on Win98 (no fiddling with memory offsets, just regular stuff like load EMM386 with NOEMS, and load TSRs high) gives more free memory than MEMMAKER on DOS 6.22.

What commands would I use for this?

Cursed Derp wrote on 2024-07-04, 15:14:

What commands would I use for this?

You have been asked already to provide your configuration files and current memory status by dr_st so we can tell you, but you ignored it.

Here's the results of mem /c /p. I'll send the Autoexec and config.sys soon.

Here's my autoexec and config.sys

Uhh...you didn't successfully attach the memory layout, but I don't see anything bad in your configs. If you really want more Conventional memory, you should be able to get away with adding "I=B000-B7FF" to EMM386.exe's command line. This can use the default mono graphics buffer as UMBs and was there on my first PC's DOS setup. If that doesn't help, try QEMM97.

Here's the memory layout

I see no Upper memory. I just realized why: you need to specify "RAM" on EMM386's command line. This will tell EMM386 to enable UMBs. Try it out, and post the results. 😀

Should I type "emm386.exe ram"?

Umm...I was wrong: you have the switch, and DOS= seems to be right. I'm looking at some EMM386 docs right now to see what's wrong. If you want, the link is https://info.wsisiz.edu.pl/~bse26236/batutil/ … elp/EMM386S.HTM. I had a similar problem with a recent Win98SE tower: when I used "I=B000-B7FF," that's all I got. 🙁 I had to include "I=E000-E7FF," as QEMM's MANIFEST indicated E000-EFFF as free, and specifying more locked the system. 🙁 I will continue studying your configs and try to see what's wrong.

BTW, try adding V to EMM386's command line and publish the results. V will tell EMM386 to display full diagnostics upon startup.

I just noticed a problem with your config.sys: the first [common] section is split in two lines, so maybe MSDOS is not interpreting the section as a common section. Try to fix it and see what happens. 😀

BTW, you have a lot of drivers loaded. In the end, you might want to try QEMM. It makes a lot more UMB memory available, and if that's not enough, provides two Stealth modes to add to memory by using ROM space for more by switching ROM memory in upon access then switching it out afterwards and back to RAM there.

If you're using Win98's DOS mode, I think you can load some DOS resources high by adding "high" to the resources' names. For example, "FILESHIGH=" will put the FILES data into UMBs. I don't think you can specify in which area to load them, though. 🙁 Try it out!

Where would I put the "FILESHIGH="?

Just replace "FILES=" with "FILESHIGH=." It should be put there after EMM386 is loaded. Did you try the typo fix to your config.sys yet?

Yeah I tried the typo fix. I also added emm386 to the config.sys after the dos=high line. Then I changed files=30 to fileshigh=30. The game still janks out though. I might try qemm. I'm burning it to a cd right now.