Unable to change Virtual Memory settings

Running Win 98 SE on an IBM ThinkPad A22e (Celeron 800) with 128 MB RAM.

I just installed a 4+ GB HDD, and partitioned it into 6 chunks: C is ~1.5 GB, D, E, and F are 1 GB, and G is leftovers, about 200 MB. My plan was to make G the swapfile.

When I go into the Virtual Memory settings dialog box, the only option that shows any free space is C, while in reality G is empty, D has about 500 MB free, and E & F each have about 750 MB free.

Can anyone point me to a fix?

 

Swap file must be on C: and/or another physical disk, not another partition on same disk as C:

 

Open your System.Ini file located in the windows folder with Notepad. Add these lines under the section labeled [386Enh].

[386Enh]
PagingDrive=G:
MinPagingFileSize=131072

Then reboot, you will have a 128 mb swapfile on G:, delete the old "Win386.Swp" file in the windows folder. If you want a different size, just multiply your choice by 1024 to use in the System.Ini file.

 

Not so... I had it in a similar setup on the old (now crashed) HDD.

 

Thanks, markp62. I'll give that a try this afternoon when I get home.

 

First time I tried, I appended your text to the existing 386Enh. Saved, closed, rebooted. After reboot, checked Virtual Memory. Unchanged!? Checked System.ini - my change was NOT there.

Second time, I inserted the text above the existing text. Saved, closed, maked file as Read Only for good measure, rebooted. After reboot, Virtual Memory still was set for "Allow Windows..." BUT the list for the other drives now showed a value for G (the intended swapfile drive). Previous checks of the drive list showed zero available on all drive but C.

The Virtual Memory settings would not retain my choice of G, though, even though it showed in the list as having available space.

 

Don't APPEND the text.

Look for an existing [386enh] section and insert the lines in that area.

If there are existing lines referencing
PagingDrive or MinPagingFileSize
replace them.

 

I wouldn't leave the system.ini file marked as read only. If you ever install a program or a device of some type that needs to put an entry in it, it'll fail and more than likely you'll have a messed up installation. Just something for you to think about.

 

When you insert the lines in under the [386Enh], this bypasses the Virtual Memory settings. It will say, 'allow window to ...', and your reported seeing G: for the intended swap file drive. This is normal.
Open Windows Explorer, and check the G: drive for a hidden file named Win386.Swp.

 

Gotcha. So ignore what it looks like the settings box is saying... the location of the swapfile is the proof.

Thanks!

 

I stand corrected! Maybe "must be" should be "recommended" ?
I am trying to understand why anyone(generically, not aimed at magi359, nor meant as a slam) would want to move swap file from C to another partition on same drive? I know there is no performance gain from this, in fact it slows perf somewhat (being that C is the closest to outer part of disk, faster read/write). Moving to another drive, other than OS is on, does increase performance (although should be on first partition on that drive as well (reason above)
I understand if C is too full, moving swap file to a partition with more room. But why set up small, multiple partitions and move swap from C on a new HDD??
Just trying to "learn" a little more
Appreciate any explanations, thanks, Joe.

 

When you have enough memory, it is a good idea to move the swapfile, and set it's minimum size. At default values, even though it isn't being used, windows will increase the size of the swapfile in case it is needed, like calling ahead for reservations at a cafe. The size will shrink and grow according to the whims of windows. With a MIN size of 128 mb there is little of this going on, freeing up your drive's platters for your digital use and increasing system performance.
I can look up my swap file on my 98Se partition, and see it hasn't been touched since I set it
Another reason is drive fragmentation. Defrag does not touch the swapfile, therefore files are scattered around it because the swapfile is fragmented.
When you create the swapfile on another empty partition with a MIN size, it is done in one swoop, creating little fragmentation in the process.
If you create it on C:, it may be physically created beyond your system and program files, or stuck in the middle of them.

 

A final note (from me, anyway):

I ended up adding both a MIN and a MAX setting. The PC ran oddly with just the Min setting, especially at a high number. I set Min at 1 and Max at 200 MB, and it ran OK.

After I got the HDD replaced, I set the swpafile in its own partition and it's running like a champ again.

Curious why the temp HDD gave me problems while adjusting the virtual memory, while the old (dead) and new HDD made the change with no arguments.

 

Glad to hear that you are running again.
BUT
You do not want to place a MAX on the swapfile. If windows ever needs more VM than you currently have assigned, you will get program failures and potentially data corruption.
Leave the MAX off, which will allow it to grow, if required.