Page file needed on OS drive?

[parsec]

Re: Page file needed on OS drive?

I see what you mean (I think) but I don't see the difference. The non-C drive I set the FFox cache to, exists when I set the cache location in FFox, as well as the folder on that drive. The drive letter does not change, it is D: when I set the cache location, and D: when I reboot. Sure, if I changed drives in the PC, and the folder did not exist, then I would need to set it correctly.

Hmm, maybe that's it, I should NOT create the folder before I set it, and let FFox do it. Off to try that...

[parsec]

Re: Page file needed on OS drive?

Nope, still doesn't work. Every reboot removes the string I entered for the cache file location. Seems like that is done on purpose, or maybe is a bug, but I know better than to jump to that conclusion.

[profJim]

Re: Page file needed on OS drive?

I'm running the older 3.6.xx FireFox version and it has no problem using my existing D:\Cache-FF folder every time it starts. It sounds like FireFox has a hissy fit if it doesn't find the different cache folder location when it starts up, so it just defaults to its normal cache folder location on the C: drive.

This wasn't a problem with the DataRamDisk software when I set it to save the ram disk's contents at shut down and to load the saved proprietary image file when the system starts up. I stopped using the ram disk when it failed to start several days after it was installed. I wanted my ram disk to have a swapfile, TEMP folder, and cache folders for FireFox and Internet Explorer. I wanted all three folders to be empty at start up.

The main reason I stopped using DataRamDisk software was that it took four minutes to create a saved image file for my nearly empty 2GB ram disk.

Clear as mud?

[parsec]

Re: Page file needed on OS drive?

I'm running the older 3.6.xx FireFox version and it has no problem using my existing D:\Cache-FF folder every time it starts. It sounds like FireFox has a hissy fit if it doesn't find the different cache folder location when it starts up, so it just defaults to its normal cache folder location on the C: drive...

Clear as mud?

I've done it both ways, with the cache file on another drive created first, and then tried to let it create it on it's own. The problem occurs with a reboot regardless.

For example, I create a cache folder on the D: drive for FFox. Check the Properties, 0 bytes.

Start FFox, set the cache to the new location. Quit FFox, and start it again. Go to a site or two. Check the FFox cache folder, several MBs in size. Open the folder, and it is filled with folders, etc.

Later reboot the PC. Start FFox, check my setting for the cache folder, it is now blank, unset. Before I noticed this, I would use the PC normally for days. I happened to look at the folders on the FFox cache drive, and I see the last accessed date of the cache folder is days ago. Start up CCleaner, and see I have a huge FFox cache folder on the C: drive, which I had deleted when I created the cache on the other drive. I know that FFox still uses the C: drive for other things, so I don't expect nothing from FFox on the C: drive.

So create the cache folder, set the path to cache folder in FFox, restart FFox, and it uses the cache folder I created, it grows in size and is loaded with entries.

Restart the PC, path setting in FFox is cleared (blank) and the cache folder I created is no longer used by FFox, although it is there and full of files and folders.

Just had a thought, I'll check it...