Is there any way to move hiberfil.sys to another partition,..
in [Win32 Kernel]
|
Prev: MiniDumpWriteDump fails with error 0x8007012B (Only part of a ReadProcessMemory or WriteProcessMemory request was completed.)
Next: writefile(..) ERROR number =5 = Access is Denied, when writing to USB sector 0
From: Alan Carre on 5 Jul 2008 23:44 "Kerem G�mr�kc�" <kareem114(a)hotmail.com> wrote in message news:uYgKieO2IHA.3884(a)TK2MSFTNGP05.phx.gbl... > So my question is not abozt making the system faster by > moving hiberfil.sys to some other place, because in fact > it wont make anything faster, but the question is more about > whether this is possible or not. Is anyone going to answer this question? I also would like to know if it is possible. And boy would I would LOVE to turn on the hybernate feature! Unfortunately there's not enough space left on my boot partition (Ok, well there is, but *just barely*. hyberfile.sys would be 2Gigs on this machine unless i yank out my RAM - [which I refuse to do] leaving me with a piddly couple hundred megs. Which, strangely, seems to be the approximate magnitude of "free-space fluctuations" that occur regularly). Also, preemptively, I would like to point out, that there's absolutely NO speed increase booting up via. un-hybernate as everyone should know. It's *not* about speed. The advantage of un-hybernalte is entirely in the fact that you can resume whatever it was you were doing at the time of shutdown. And *that* is no small time-saver. Sometimes I have dozens of apps open and in the middle of editing documents in all of them (code, data, images, config files, database files, registry settings, etc etc etc) and somehow I'm supposed to remember all that and pick up where I left off ?!?!? Plus, even if I *could* remember where I was, I lose my undo/redo histories in every app. So it's impossible really, to get back to the original spot where you left off. But not with Hybernate(TM)! ;) - Alan Carre P.S. BTW: I have consistent power failures out here in the boon-docks... so it's not like I can just leave the machine on (in case someone were to suggest that as a *solution*). P.P.S. Kerem: "Swap file to USB" Wow! Who would've thought? You're a f&*%ing Genius! I wonder though... would a RAM drive really work (as someone "jokingly" suggested)? That would be even faster (and especially for me with 2Gigs available. You see, unfortunately XP is too stupid to realize that there's enough physical memory available to accomidate all tasks and instead decides to map otherwise available RAM addresses to some clumsy machine with gears and servo motors and little disks whizzing around. Great for long-term storage, but for real-time use? You know, I just don't get it...).
From: Smithsonian on 6 Jul 2008 12:04 Try doing a disk cleanup to get more space. From what I understand, you have more than one volume. If your not using all that space, try putting some back in your boot volume. You can try getting rid of un needed files. I belive disk cleanup will remove old hibernation files as long as you select that option. >> So my question is not abozt making the system faster by >> moving hiberfil.sys to some other place, because in fact >> it wont make anything faster, but the question is more about >> whether this is possible or not. I dont think so. "Alan Carre" <alan(a)twilightgames.com> wrote in message news:u3jWMqx3IHA.1200(a)TK2MSFTNGP04.phx.gbl... > "Kerem G�mr�kc�" <kareem114(a)hotmail.com> wrote in message > news:uYgKieO2IHA.3884(a)TK2MSFTNGP05.phx.gbl... > >> So my question is not abozt making the system faster by >> moving hiberfil.sys to some other place, because in fact >> it wont make anything faster, but the question is more about >> whether this is possible or not. > > Is anyone going to answer this question? I also would like to know if it > is possible. > > And boy would I would LOVE to turn on the hybernate feature! Unfortunately > there's not enough space left on my boot partition (Ok, well there is, but > *just barely*. hyberfile.sys would be 2Gigs on this machine unless i yank > out my RAM - [which I refuse to do] leaving me with a piddly couple > hundred megs. Which, strangely, seems to be the approximate magnitude of > "free-space fluctuations" that occur regularly). > > Also, preemptively, I would like to point out, that there's absolutely NO > speed increase booting up via. un-hybernate as everyone should know. It's > *not* about speed. The advantage of un-hybernalte is entirely in the fact > that you can resume whatever it was you were doing at the time of > shutdown. And *that* is no small time-saver. Sometimes I have dozens of > apps open and in the middle of editing documents in all of them (code, > data, images, config files, database files, registry settings, etc etc > etc) and somehow I'm supposed to remember all that and pick up where I > left off ?!?!? Plus, even if I *could* remember where I was, I lose my > undo/redo histories in every app. So it's impossible really, to get back > to the original spot where you left off. > > But not with Hybernate(TM)! ;) > > - Alan Carre > > P.S. BTW: I have consistent power failures out here in the boon-docks... > so it's not like I can just leave the machine on (in case someone were to > suggest that as a *solution*). > > P.P.S. Kerem: "Swap file to USB" Wow! Who would've thought? You're a > f&*%ing Genius! I wonder though... would a RAM drive really work (as > someone "jokingly" suggested)? That would be even faster (and especially > for me with 2Gigs available. You see, unfortunately XP is too stupid to > realize that there's enough physical memory available to accomidate all > tasks and instead decides to map otherwise available RAM addresses to some > clumsy machine with gears and servo motors and little disks whizzing > around. Great for long-term storage, but for real-time use? You know, I > just don't get it...). > > >
From: Alan Carre on 6 Jul 2008 13:24 "Smithsonian" <irc_smithsonian(a)hotmail.com> wrote in message news:E907CF1D-2790-4D9C-B81E-0D21791051C5(a)microsoft.com... > Try doing a disk cleanup to get more space. From what I understand, you > have more than one volume. If your not using all that space, try putting > some back in your boot volume. You can try getting rid of un needed files. > I belive disk cleanup will remove old hibernation files as long as you > select that option. Been there, done that... long time ago. The main problem is this concept of the "system drive" and what all that entails. Which is mainly, that certain functions can ONLY be done on the system drive (even though there's no logical reason for said limitation). For instance, if I want to install SP2 for VC2005, the installer MUST make a copy of itself under the "%SystemRoot%\downloaded Program Files" folder as a strange encrypted UUID extensionless file. Then, to proceed with the installation it MUST extract itself to "%SystemRoot%\Downloaded Installations\", this time as a folder containing an msi installer. Next, before installation, the system MUST create a system checkpoint under "%SystemDrive%\System Volume Information\" creating a 3rd copy of the 600 meg installer. Next, to proceed with the msi program the system MUST create another copy of the extracted files in %TMP% which MUST be under "%SystemRoot%\Documents And Settings\UserName\Local Settings\Temp", so now we're up to 1.8Gigs before we can begin copying files over to the other volume. Now all this would be OK if it were not for the fact that the installer MUST remian in-place or else the program cannot be uninstalled or patched or upgraded. Apparently we're allowed to dispense with the TMP part, and the 600 meg UUID un-extracted pre-download stuff, but we've still lost 1.2Gigs of space when installing onto a non-system partition. Of course we can purge the system checkpoint, which is what I normally wind up doing, and have no way to undo the process in the case where the installer botched it's attempt and could not remove itself automatically (which does happen, I gurantee you that). Anyway, I went through this painful process a few times and at one point, starting from 2.5Gigs my system drive was down to a mere 200megs before I decided the installer was not cognizant of the fact that it was about to self-destruct and take my computer down with it. Having no way to stop it's greedy march towards eating up every single byte on the HD I managed to get taskmanager up just in time and killed it. So now here I was, left with a demolished registry containing a malformed trillianth-order-complexity web of interconnecting references to non-existant COM objects, 150megs of space on the HD and clueless about how to proceed. First, I wanted to get the registry repaired. So that means running system restore. Well, do you know what it told me? "System restore requires at least 5% (or some number anyway) of space ON THE SYSTEM PARTITION in order to function". So there went that idea. I'm sure my registry is in shambles even as I write this, but there was nothing to do about it so I just deleted all of those "must-haves" and then tried the cleanup (nothing as usual) deleted anything I could find left on that drive that wasn't "system-related", and still I was below the required 5-6 Gigs to install the compiler (ON ANOTHER DRIVE!). Sorry for caps... it's very frustrating sometimes... Anyway, without options I resorted to the unthinkable: Start/Run - "psexec -s cmd.exe" and to hell with it. I walked directly into "System Volume Information" and wiped the f*$#er out. Retrieved over 5 Gigs of storage incidentally. And I also discovered a maze, I guess the skeletal remains, of system checkpoints dating back over 2 years, sitting there dead and forgotten. I didn't stop there though, I was on a roll! I deleted and deleted and deleted. Downloaded this, Installer that, Plugin this, $NtUninstalXXX$ that. All this useless junk sitting on my system drive, uninstallers for stuff I would never in a million years consider myself knowledgable enough to *install* let alone *uninstall*. Why would you uninstall a service pack? From the name? $NtUninstallKB946026$, ya I think I should uninstall that one... it juuust doesn't feel right.??? Anyway, sorry for the rant. Had to get that off my chest. Much like I'd like to get the OS off my "System Drive" ;) - Alan Carre
From: Pavel A. on 6 Jul 2008 17:20 Ugm. 2.5 GB is too little for the system drive. However... using directory junctions can help to move stuff away from the system partition, while it still logically remains part of it's directory tree. [ More on junctions: http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx ] Regards, --PA "Alan Carre" <alan(a)twilightgames.com> wrote in message news:O$AER043IHA.2580(a)TK2MSFTNGP06.phx.gbl... > "Smithsonian" <irc_smithsonian(a)hotmail.com> wrote in message > news:E907CF1D-2790-4D9C-B81E-0D21791051C5(a)microsoft.com... >> Try doing a disk cleanup to get more space. From what I understand, you >> have more than one volume. If your not using all that space, try putting >> some back in your boot volume. You can try getting rid of un needed >> files. I belive disk cleanup will remove old hibernation files as long as >> you select that option. > > Been there, done that... long time ago. The main problem is this concept > of the "system drive" and what all that entails. Which is mainly, that > certain functions can ONLY be done on the system drive (even though > there's no logical reason for said limitation). For instance, if I want to > install SP2 for VC2005, the installer MUST make a copy of itself under the > "%SystemRoot%\downloaded Program Files" folder as a strange encrypted UUID > extensionless file. Then, to proceed with the installation it MUST extract > itself to "%SystemRoot%\Downloaded Installations\", this time as a folder > containing an msi installer. Next, before installation, the system MUST > create a system checkpoint under "%SystemDrive%\System Volume > Information\" creating a 3rd copy of the 600 meg installer. Next, to > proceed with the msi program the system MUST create another copy of the > extracted files in %TMP% which MUST be under "%SystemRoot%\Documents And > Settings\UserName\Local Settings\Temp", so now we're up to 1.8Gigs before > we can begin copying files over to the other volume. Now all this would be > OK if it were not for the fact that the installer MUST remian in-place or > else the program cannot be uninstalled or patched or upgraded. Apparently > we're allowed to dispense with the TMP part, and the 600 meg UUID > un-extracted pre-download stuff, but we've still lost 1.2Gigs of space > when installing onto a non-system partition. > > Of course we can purge the system checkpoint, which is what I normally > wind up doing, and have no way to undo the process in the case where the > installer botched it's attempt and could not remove itself automatically > (which does happen, I gurantee you that). > > Anyway, I went through this painful process a few times and at one point, > starting from 2.5Gigs my system drive was down to a mere 200megs before I > decided the installer was not cognizant of the fact that it was about to > self-destruct and take my computer down with it. Having no way to stop > it's greedy march towards eating up every single byte on the HD I managed > to get taskmanager up just in time and killed it. So now here I was, left > with a demolished registry containing a malformed > trillianth-order-complexity web of interconnecting references to > non-existant COM objects, 150megs of space on the HD and clueless about > how to proceed. > > First, I wanted to get the registry repaired. So that means running system > restore. Well, do you know what it told me? "System restore requires at > least 5% (or some number anyway) of space ON THE SYSTEM PARTITION in order > to function". So there went that idea. I'm sure my registry is in shambles > even as I write this, but there was nothing to do about it so I just > deleted all of those "must-haves" and then tried the cleanup (nothing as > usual) deleted anything I could find left on that drive that wasn't > "system-related", and still I was below the required 5-6 Gigs to install > the compiler (ON ANOTHER DRIVE!). Sorry for caps... it's very frustrating > sometimes... > > Anyway, without options I resorted to the unthinkable: Start/Run - > "psexec -s cmd.exe" and to hell with it. I walked directly into "System > Volume Information" and wiped the f*$#er out. Retrieved over 5 Gigs of > storage incidentally. And I also discovered a maze, I guess the skeletal > remains, of system checkpoints dating back over 2 years, sitting there > dead and forgotten. I didn't stop there though, I was on a roll! I deleted > and deleted and deleted. Downloaded this, Installer that, Plugin this, > $NtUninstalXXX$ that. All this useless junk sitting on my system drive, > uninstallers for stuff I would never in a million years consider myself > knowledgable enough to *install* let alone *uninstall*. Why would you > uninstall a service pack? From the name? $NtUninstallKB946026$, ya I think > I should uninstall that one... it juuust doesn't feel right.??? > > Anyway, sorry for the rant. Had to get that off my chest. Much like I'd > like to get the OS off my "System Drive" ;) > > - Alan Carre > >
From: David Craig on 6 Jul 2008 17:21
Is there something that says you have to use the current hard drive with the partitions as they currently exist? What is wrong with Partition Magic? New hard drive? Both? "Alan Carre" <alan(a)twilightgames.com> wrote in message news:O$AER043IHA.2580(a)TK2MSFTNGP06.phx.gbl... > "Smithsonian" <irc_smithsonian(a)hotmail.com> wrote in message > news:E907CF1D-2790-4D9C-B81E-0D21791051C5(a)microsoft.com... >> Try doing a disk cleanup to get more space. From what I understand, you >> have more than one volume. If your not using all that space, try putting >> some back in your boot volume. You can try getting rid of un needed >> files. I belive disk cleanup will remove old hibernation files as long as >> you select that option. > > Been there, done that... long time ago. The main problem is this concept > of the "system drive" and what all that entails. Which is mainly, that > certain functions can ONLY be done on the system drive (even though > there's no logical reason for said limitation). For instance, if I want to > install SP2 for VC2005, the installer MUST make a copy of itself under the > "%SystemRoot%\downloaded Program Files" folder as a strange encrypted UUID > extensionless file. Then, to proceed with the installation it MUST extract > itself to "%SystemRoot%\Downloaded Installations\", this time as a folder > containing an msi installer. Next, before installation, the system MUST > create a system checkpoint under "%SystemDrive%\System Volume > Information\" creating a 3rd copy of the 600 meg installer. Next, to > proceed with the msi program the system MUST create another copy of the > extracted files in %TMP% which MUST be under "%SystemRoot%\Documents And > Settings\UserName\Local Settings\Temp", so now we're up to 1.8Gigs before > we can begin copying files over to the other volume. Now all this would be > OK if it were not for the fact that the installer MUST remian in-place or > else the program cannot be uninstalled or patched or upgraded. Apparently > we're allowed to dispense with the TMP part, and the 600 meg UUID > un-extracted pre-download stuff, but we've still lost 1.2Gigs of space > when installing onto a non-system partition. > > Of course we can purge the system checkpoint, which is what I normally > wind up doing, and have no way to undo the process in the case where the > installer botched it's attempt and could not remove itself automatically > (which does happen, I gurantee you that). > > Anyway, I went through this painful process a few times and at one point, > starting from 2.5Gigs my system drive was down to a mere 200megs before I > decided the installer was not cognizant of the fact that it was about to > self-destruct and take my computer down with it. Having no way to stop > it's greedy march towards eating up every single byte on the HD I managed > to get taskmanager up just in time and killed it. So now here I was, left > with a demolished registry containing a malformed > trillianth-order-complexity web of interconnecting references to > non-existant COM objects, 150megs of space on the HD and clueless about > how to proceed. > > First, I wanted to get the registry repaired. So that means running system > restore. Well, do you know what it told me? "System restore requires at > least 5% (or some number anyway) of space ON THE SYSTEM PARTITION in order > to function". So there went that idea. I'm sure my registry is in shambles > even as I write this, but there was nothing to do about it so I just > deleted all of those "must-haves" and then tried the cleanup (nothing as > usual) deleted anything I could find left on that drive that wasn't > "system-related", and still I was below the required 5-6 Gigs to install > the compiler (ON ANOTHER DRIVE!). Sorry for caps... it's very frustrating > sometimes... > > Anyway, without options I resorted to the unthinkable: Start/Run - > "psexec -s cmd.exe" and to hell with it. I walked directly into "System > Volume Information" and wiped the f*$#er out. Retrieved over 5 Gigs of > storage incidentally. And I also discovered a maze, I guess the skeletal > remains, of system checkpoints dating back over 2 years, sitting there > dead and forgotten. I didn't stop there though, I was on a roll! I deleted > and deleted and deleted. Downloaded this, Installer that, Plugin this, > $NtUninstalXXX$ that. All this useless junk sitting on my system drive, > uninstallers for stuff I would never in a million years consider myself > knowledgable enough to *install* let alone *uninstall*. Why would you > uninstall a service pack? From the name? $NtUninstallKB946026$, ya I think > I should uninstall that one... it juuust doesn't feel right.??? > > Anyway, sorry for the rant. Had to get that off my chest. Much like I'd > like to get the OS off my "System Drive" ;) > > - Alan Carre > > |