>Hi Ed Rauh,
>
>Thanks for responding.
>Is it possible to keep windows swap file on the ram drive?

It would be incredibly silly to do unless the RAM drive were not allocated from main memory (IOW, the swap file is used primarily to deal with running out of physical memory, so you're taking memory away from the main memory pool and creating a small RAM drive. You'd be losing available memory in the operation because of overhead. If you had a RAM drive allocated from memory that was otherwise not available as main system memory, like some of the stuff like JTree and SSD used to offer (add-on boards that emulated EMS from a long time ago) it would make sense; if you're allocating a RAM drive, you'd be better off not allocating the RAM drive and giving the memory back to Windows.

For Win95/Win98, I'd simply allocate the Windows swap file on the biggest, fastest drive I had. I tend to create a separate FAT16 partition on one of my drives in the 300-500MB range and put the swap file on that partition with nothing else, preallocating it on the empty drive to a pretty big value (the Win98 box here has a 380MB partition for the swap file, and I've got it preallocated to a minimum and maximum size of 350MB; that way, the swap file won't get fragmented and no overhead for maintaining the FAT tables as the swap file grows and shrinks is encountered. And I don't get the annoying message from Win98 telling me that disk space is getting low there...)

With NT, swap file setup is more involved; I tend to allocate a swap file on each physical drive or stripe set (it does not make sense to allocate a swap file per logical drive) which improves system performance measurably. There's a good discussion of NT swap file settings on John Savill's NT FAQ page.

It is not advisable to run with virtual memory disabled under any of the operating systems, since there are things that the swap file is used for besides swaping programs.