Out of Memory Error

Bob Longford · Post by **Bob Longford** » Sun Oct 01, 2000 9:24 pm

I'm running Windows 98 Second Edition. Old version of Pacific War runs fine. Matrix version gives an out of memory error when I try to access aircraft assignment on carriers in port or task force display. Can't change the assignment of my aircraft! Any suggestions?

Vonbrown · Post by **Vonbrown** » Sun Oct 01, 2000 10:37 pm

Originally posted by Bob Longford:
I'm running Windows 98 Second Edition. Old version of Pacific War runs fine. Matrix version gives an out of memory error when I try to access aircraft assignment on carriers in port or task force display. Can't change the assignment of my aircraft! Any suggestions?

I spoke to soon in my previous post and for this I hang my head in shame.
I am running WIN2000 Pro and I am experiencing the very same thing. I have checked the properties of PAC.EXE and everything is set to auto. I would have hoped that this would allow WIN to allocate memory with no problems as the original PACWAR runs fine. Is this a problem with THE MATRIX PROJECT?

sapperland · Post by **sapperland** » Sun Oct 01, 2000 10:38 pm

I get the same thing. Another thread talked about optimizing memory but I have not tried it.

Cmdrcain · Post by **Cmdrcain** » Mon Oct 02, 2000 12:04 am

Originally posted by Bob Longford:
I'm running Windows 98 Second Edition. Old version of Pacific War runs fine. Matrix version gives an out of memory error when I try to access aircraft assignment on carriers in port or task force display. Can't change the assignment of my aircraft! Any suggestions?

Guys, can you try this:

start up your Pc, pick the MS-DOS prompt
shortcut, type MEM in Dos, tell us what you see.

My shortcut to Ms-dos is set to give me 610K memory free, I have had no problems
so far no out of memory, no errors looking at plane groups.

This Updated version maybe Iffy if less 610K free in your dos box.

sapperland · Post by **sapperland** » Mon Oct 02, 2000 5:11 am

I have 568 free, so there-in lies my problem.
Its been a long time since I messed with DOS

Kermit · Post by **Kermit** » Mon Oct 02, 2000 1:50 pm

In response to Vonbrown's question for Win2000 - here's a copy of what I posted in a different thread...

1. copy autoexec.nt and config.nt from %systemroot%\system32 to the pacwar installation dir
2. REM out everything in the copied files
3. Create a new shortcut to pac.exe & click on the advanced button under the program tab
4. Adjust the paths to the autoexec.nt and config.nt files to the edited ones in the pacwar dir
5. problem solved!

This worked for me and several others round here under 2000 - basically it's everything the Matrix guys have been saying from the start - definately a case of RTFM (or in this case the release notes!)

frank1970 · Post by **frank1970** » Mon Oct 02, 2000 2:31 pm

Try memmaker!
Go to Dos - type memmaker- the other things run automatically.

Cmdrcain · Post by **Cmdrcain** » Mon Oct 02, 2000 9:16 pm

Originally posted by sapperland:
I have 568 free, so there-in lies my problem.
Its been a long time since I messed with DOS

568K likely woould give you problems with the old version too, thats low considering it's best if had 600K at least.

You are talking of the Dos box, not Memory booting up in Ms-dos mode since booting in Ms-dos mode can be different then using Dos box.

if dos box, your msdos prompt settings arent loading likely drivers into high mem

aglozier · Post by **aglozier** » Tue Oct 03, 2000 12:19 am

I have found the problem with running Pacific War under Win 2000. The shortcut (PIF) files that get installed with the game are screwed up. You need to delete them. There's one called "PAC" in the Pacific War directory and another called "Pacific War DOS Start" in the Windows start menu. If you want a new shortcut in the start menu, just drag "PAC.EXE" to it to create a new one.

The bad shortcuts cause some drivers to
be loaded in low memory instead of high memory. This results in only 583K of memory instead of 633K of memory. My guess is that the bad shortcuts are for Win 9X and are not compatible with Win 2000.

George

sapperland · Post by **sapperland** » Tue Oct 03, 2000 3:02 am

I used to know every trick in the book for DOS. But over the last 10 years I have forgotten most of it.
Cmdrcain,
I will try booting in DOS and see what I get.
Memmaker that Frank suggested could help also.

Bing · Post by **Bing** » Tue Oct 03, 2000 6:45 am

Originally posted by sapperland:
I used to know every trick in the book for DOS. But over the last 10 years I have forgotten most of it.
Cmdrcain,
I will try booting in DOS and see what I get.
Memmaker that Frank suggested could help also.

Memmaker did not survive in the DOS remake that comes with Windows 98. Believe DOS 6.22 last time it was available, I can verify it is not there in DOS 7.0. There are other ways to increase conventional memory, however.

Bing2

frank1970 · Post by **frank1970** » Tue Oct 03, 2000 11:15 am

I kept a copy of my old Dos on Disks and copied the important files into the new Dos folder.

Bob Longford · Post by **Bob Longford** » Wed Oct 04, 2000 2:55 am

Thanks to everyone for the help. Actually, I have since found a helpful site on the net
<http://pages.hotbot.com/arts/gorx/windows.html>. Took the following Config.sys from it and had to download a DOS mouse driver to call in Autoexec.bat. Now I kick off a DOS session with almost 600K free lower mem and PacWar runs fine!

Thanks again and hope this helps others.

DEVICE=C:\WINDOWS\HIMEM.SYS /TESTMEM:OFF
DOS=HIGH,UMB
DEVICE=C:\WINDOWS\EMM386.EXE noems frame=none I=B000-B7FF
DEVICEhigh=C:\WINDOWS\IFSHLP.SYS
BUFFERShigh=13
FILEShigh=40

Vonbrown · Post by **Vonbrown** » Sat Oct 14, 2000 2:04 pm

Originally posted by Kermit:
In response to Vonbrown's question for Win2000 - here's a copy of what I posted in a different thread...

1. copy autoexec.nt and config.nt from %systemroot%\system32 to the pacwar installation dir
2. REM out everything in the copied files
3. Create a new shortcut to pac.exe & click on the advanced button under the program tab
4. Adjust the paths to the autoexec.nt and config.nt files to the edited ones in the pacwar dir
5. problem solved!

This worked for me and several others round here under 2000 - basically it's everything the Matrix guys have been saying from the start - definately a case of RTFM (or in this case the release notes!)

Sorry guys, but this is not working for me.
I see no mention of mem configs or problems in the manual or the release notes.
Have tried this config, but I get a warning box telling me that this is not set up to run MS-DOS or Windows programs. I chose to ignore, but the program still does not run.
The only problem I am having is accessing air units on carriers. I think I will just go back to the original and wait for Matrix's new game of the Pacific War.
Thanks guys for the help and MATRIX RULES THE GAMING WORLD! Keep up the good work!

brisd · Post by **brisd** » Sat Oct 14, 2000 9:22 pm

I am using Windows ME (installed just this week) and currently have only 572K in DOS. I have tried both changing CONFIG.SYS to as suggested above and either REM'ing out AUTOEXEC.BAT or deleting it entirely. When I reboot the pc something is restoring the old files of config.sys of ZERO bytes (no lines) and the old autoexec.bat. Does anyone have any ideas where I can disable this restore feature. I have a basic knowledge of DOS and Win95 but just starting to learn WIN ME. Thanks in advance, the new game is beautiful!

Brian