PLEX86  x86- Virtual Machine (VM) Program
 CVS  |  Mailing List  |  Download  |  Successes  |  In the Media  |  Newsgroups

When should I really defrag 589


Your Ad Here

Your Ad Here

Another alternative is to automatically delete the swapfile at shutdown, then you don't have to worry about it fragmenting over time. Takes a few extra seconds to shutdown, and a few extra seconds to rebuild it a boot, but worth it (and good security too).

It's in the registry at hklm-system-current control set-control-session manager-memory management-ClearPageFileAtShutdown=1

Personally, I've also always put the swapfile on a drive of it's own, on systems where I've had room for a second drive. All the 'experts' have told me it's bad for Windows to not have the swapfile on c:, but have never given me a coherent explanation why. Yes, I know it means you can't do a memory dump on critical error, but so what ? I've never needed to do a core dump on a windows system, and even if I did, I wouldn't know what to do with it anyway.

When should I really defrag 590
I've **NEVER** heard of anyone saying, as a blanket statement, that it's a "bad thing" to have the swap file anywhere...

- FM -



Your Ad Here

List | Previous | Next

When should I really defrag 590

alt.sys.dell talk from Newsgroups.

dell sx270's randomly won't boot