Re: hibernation file location
- From: John Hensley <resqware@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 16 Jun 2007 16:54:01 -0700
"Don Burn" wrote:
I guess I am trying to understand why you think this works? The hiberfile
is written by OS using the dump file mechanism and has nothing to do with
int 13h. I have not looked at the startup so this may have value here, but
when the system is running it is going to doing the hiberfile to boot disk.
With XP and 2K the hiberfile is read into memory by NTLDR which can only
access the file via ROMBIOS int 13h. Of course when the OS is running it
could write the file onto any drive during hibernation. NTLDR only searches
for the hiberfile on the actual boot drive so writing it anywhere else would
appear to make it inaccessible.
Though it is common to load the non-bootstrap components of the OS from a
non-int 13h accessible drive using an ntbootdd.sys mini-port driver, I am
assuming NTLDR doesn't search anything other than the actual boot drive since
the presence of a valid hiberfile prevents boot.ini from being processed and
thus any information about the actual system drive would not be available.
A good overview of how NTLDR processes the hiberfile can be found in chapter
5 of "Windows Internals 4th edition".
I doubt the int 13h on restart even, since with Vista Microsoft allows
filter drivers on the hiberfile read / write path. I have not seen the
spec on how the filters are done, so I do not know whether a filter could
change the drive.
I suspect that the changes to Vista necessary to support BitLocker and BCD
would allow Vista to locate the hiberfile on any drive but I doubt Microsoft
would document such behavior because it would be a giant security hole on a
BitLocker system.
Don Burn (MVP, Windows DDK).
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply
"John Hensley" <resqware@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B65D5E48-5C19-4F5C-8FCF-009B7446BB7F@xxxxxxxxxxxxxxxx
These suggestions are based on the assumption that you only want to do
this
on your own co
It is possible to trick Windows into using a second drive to hold the
hiberfile if the second drive is accessable through the ROMBIOS int 13h
interface at boot time.
If the ROMBIOS supports booting from the second drive you will only need
to
put the bootstrap files from root directory of the original boot onto the
second drive, update the boot.ini file on the second drive so that it
loads
Windows from the first drive and then change the ROMBIOS to boot from the
second drive.
If the ROMBIOS does not support booting from the second drive you can
still
might be able to make it work by putting a BOOTSEC.DAT file on the boot
drive
containing a modified boot sector from the boot partition on the second
--
John Hensley
www.resqware.com
"Andrew Sha" wrote:
Is there a way to re-assign the hibernation file to be located on a hard
drive that is not the system (boot) one?
TIA
- Follow-Ups:
- Re: hibernation file location
- From: Norman Diamond
- Re: hibernation file location
- From: Don Burn
- Re: hibernation file location
- References:
- Re: hibernation file location
- From: Don Burn
- Re: hibernation file location
- Prev by Date: Re: Creating virtual midi loopback driver
- Next by Date: DbfPrint
- Previous by thread: Re: hibernation file location
- Next by thread: Re: hibernation file location
- Index(es):
Relevant Pages
|
