Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.
is it better to have your swap file on your main harddrive "c" or is it best to fave it on a faster second harddrive such as "d"? i ask the c drive only has a 2 meg cache and the d is a 8 meg cache.
it goes on the fastest connection... typically this is your fatest drive, but if you are using that drive heavily for other things it may not be the case.
but in general.. yes, on the fastest drive you've got
Keep the smallest sized swapfile posssible on your bootdrive and create the main swapfile on you fastest hard drive. This is in case the drive with the main swap crashes you will still be able to boot into xp from the minimum swap on the main HD.
The performance difference is when a swap file is on the non system partition where the windows system files are loaded. Putting a swap file on both drives is good. Windows some how knows to use the one off the system partition first. Unless you have low ram or max memory use, you probably wont notice much difference either way. Recommend you set up a second cache on your D drive...its easy to do.
If I have two HDs, I usually put the swap file in the fastest partition on the second drive. I set aside about 1 or 2GB logical drive just for swap file and TEMP directories. I try as much as possible to keep my C: drive from being frequently written.
.bh.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.