S
Scott Edwards
In the last few days, I've managed to learn quite a bit about the
vista bootmanager. I've tried various approaches to using grub4dos
(grldr, grub.exe), freeldr.sys (reactos ntldr replacement) and other
sun dry things.
One of the common errors I get is:
The selected entry could not be loaded because the application is
missing or corrupt.
I clearly know the application is there. However, how does bootmgr
decide if it's corrupt or not? What are the requirments of the boot
application, in order to load from bootmgr and continue on? Eg, why
does winload.exe work? (neverminding the clear "Well Microsoft made
it..." answer)
There are no other partitions on the disk. Launching grldr from NTLDR
via boot.ini works flawless on all NT based Windows releases I've
tested. I'm looking to do a similar thing in vista without requiring
a previous release of Windows to be used. grldr can load files into
memory off NTFS, so there's no need to use a seperate partition.
Thanks in advance.
Scott
vista bootmanager. I've tried various approaches to using grub4dos
(grldr, grub.exe), freeldr.sys (reactos ntldr replacement) and other
sun dry things.
One of the common errors I get is:
The selected entry could not be loaded because the application is
missing or corrupt.
I clearly know the application is there. However, how does bootmgr
decide if it's corrupt or not? What are the requirments of the boot
application, in order to load from bootmgr and continue on? Eg, why
does winload.exe work? (neverminding the clear "Well Microsoft made
it..." answer)
There are no other partitions on the disk. Launching grldr from NTLDR
via boot.ini works flawless on all NT based Windows releases I've
tested. I'm looking to do a similar thing in vista without requiring
a previous release of Windows to be used. grldr can load files into
memory off NTFS, so there's no need to use a seperate partition.
Thanks in advance.
Scott