My 167 GB SSD OS drive was starting to alert me on limited space left. So I moved my 15.9 GB pagefile.sys file (I have 16 GB RAM) to another drive and I'm looking to free up some space. Here are screenshots of my Program Files and Program Files (x86) showing what's on the C: drive for Sonar.
 
Questions:
1. Why is there such a big discrepancy between what I've got in the 64-bit section and the 32-bit section of Program Files. Is that normal for everyone?
 
2.  Is there a way to get some of that to my audio data drive? Or if better to not put it on that drive, to the drive where I've put the pagefile.sys file? If so, how?
 
3.  If I choose to NOT even have a pagefile.sys file, would that impact Sonar?
 
Thanks,
Chamlin

 
You can reduce the size of your pagefile.sys.  I also have 16gb of RAM but I set my pagefile to 4 GB and I'm sure I don't ever use anywhere near that.
 
You can also turn off hibernation, if it isn't already (you can still sleep).  I regained 12 GB by doing that.
 

You can also have more than one pagefile if you wish, each on a different drive (assuming you have more than one drive), and set them to any value as required (within limits though). But pagefiles are rarely needed these days anyway.
 

• How does one see whether pagefile.sys is even being used?
• And does sonar 64-bit load the approximately 10 GB on all systems? Can some of that be relocated?

chamlin

• How does one see whether pagefile.sys is even being used?

 
Windows Task Manager

You don't want to eliminate the paging device altogether, for two reasons. First, Windows uses it for its own purposes; second, it's a safety measure just in case you ever do run out of physical RAM (it can happen, even with 16GB). If the latter scenario ever does happen, Windows does not handle that situation gracefully and will crash on you.
 
Moving things out of the Program Files tree can be a headache. Some programs may stop working correctly, unable to find file dependencies. It'll take forever to figure out which things can be safely moved and which one's can't. Better to leave that stuff in place if you can.
 
The biggest disk-eater is Windows itself. You've probably got a bunch of old files from Windows updates that can be deleted. Temporary files also tend to pile up over time. I see you've got 6GB's worth of virtual machines on C: that you should be able to move to the other drive.
 
Check your virtual instruments. Many sample-based instruments want to store their libraries on C: and it's easier to let them rather than fight them. But they can all be relocated. Even little 'ol Dimension Pro takes up a lot of space, as does Studio Instruments, both of which store their libraries in the Cakewalk tree by default. Maybe you have SampleTank or Kontakt, both use a lot of disk space and both can be moved.

 
As Bit said: the pagefile is good to keep. One on the OS disk is required to create error files. Set the pagefile on the OS "disk" to the minimum suggested, and set the pagefile on the 2nd disk to system managed.
 
Also adjust the disk allocation for system restore. I have restore OFF for all but the OS disk.
 
Do a complete disk clean which includes deleting the windows update files (can be 600m) and delete all system restore points but the most recent. This can remove 4+ gig.

YouDontHasToCallMeJohnsonAs Bit said: the pagefile is good to keep. One on the OS disk is required to create error files. Set the pagefile on the OS "disk" to the minimum suggested, and set the pagefile on the 2nd disk to system managed.
 
Also adjust the disk allocation for system restore. I have restore OFF for all but the OS disk.
 
Do a complete disk clean which includes deleting the windows update files (can be 600m) and delete all system restore points but the most recent. This can remove 4+ gig.

Did the disk cleanup and gained 1.63 GB. Not bad for a days work in the salt mines! Thanks.
 
Didn't know there was a pagefile on the OS since I had moved it to an alternative disk. How do you find that?
 
The pagefile on the 2nd disk is system managed...thus it's over 16 GB. I don't really care since it's on a drive dedicated to...well...nothing. But Bitflipper's idea...

bitflipperYou don't want to eliminate the paging device altogether, for two reasons. First, Windows uses it for its own purposes; second, it's a safety measure just in case you ever do run out of physical RAM (it can happen, even with 16GB). If the latter scenario ever does happen, Windows does not handle that situation gracefully and will crash on you.
 
Moving things out of the Program Files tree can be a headache. Some programs may stop working correctly, unable to find file dependencies. It'll take forever to figure out which things can be safely moved and which one's can't. Better to leave that stuff in place if you can.
 
The biggest disk-eater is Windows itself. You've probably got a bunch of old files from Windows updates that can be deleted. Temporary files also tend to pile up over time. I see you've got 6GB's worth of virtual machines on C: that you should be able to move to the other drive.
 
Check your virtual instruments. Many sample-based instruments want to store their libraries on C: and it's easier to let them rather than fight them. But they can all be relocated. Even little 'ol Dimension Pro takes up a lot of space, as does Studio Instruments, both of which store their libraries in the Cakewalk tree by default. Maybe you have SampleTank or Kontakt, both use a lot of disk space and both can be moved.

Okay, I'll leave the program files stuff alone. My life is complex enough. :)
 
But the virtual machine idea is possible. I'll have to look into what that would entail. Would be nice to clear out the space though. Thanks!

how did you move it?  
Windows usually does not play well for this type of behavior.
control panel
system and security
system advanced
system settings
advanced tab
performance
   settings
     advanced
  virtual memory
    change
uncheck automatic  
for OS drive    custom size:  300 / 300    
    SET (gotta click set)
select second disk   
system managed    
   SET     OK,OK, OK,....