I tried booting from the C: partition 4 with umbr + reg fix and same issue - no hibernate.
I have written up experiments so far http://www.rmprepusb...s/bios_gpt_boot
Would be nice to get Hibernate working!
Posted 11 February 2017 - 03:09 PM
I tried booting from the C: partition 4 with umbr + reg fix and same issue - no hibernate.
I have written up experiments so far http://www.rmprepusb...s/bios_gpt_boot
Would be nice to get Hibernate working!
Posted 11 August 2017 - 03:03 AM
AIO Boot now supports installing Grub2 on GPT disks including both HDD and USB. After installing Grub2, you can boot the GPT disk in Legacy BIOS mode. Windows Boot Manager does not support booting into Legacy BIOS mode on GPT disks. AIO Boot uses wimboot, which consumes more RAM.
Posted 19 November 2017 - 04:24 AM
I tried booting from the C: partition 4 with umbr + reg fix and same issue - no hibernate.
I have written up experiments so far http://www.rmprepusb...s/bios_gpt_boot
Would be nice to get Hibernate working!
I found a important registry value which controls BCD system store is vaild.
A dword named TreatAsSystem with value 1 in HKLM\BCD00000000\Description is very important.
After adding this value, bcdedit and all other BCD editors included built-in boot and failure recovery works.
But Hibernate is not working, wake PC with correct FirmwareBootDevice value will result in a clean boot, wake PC with unmodified FirmwareBootDevice value will result in a recovery screen(press enter is necessary to get a clean boot).
Now the only way to get hibernate working is vhd.(edit:maybe i should put boot files in a separate partition?)
UPDATE:
Hibernate is fully working after i put boot files in a separate partition with the modification of FirmwareBootDevice. No need to re set FirmwareBootDevice every wake up, only clean boot needs. Windows will not load BCD after wake up, you should load manually.
Edited by nightrain, 19 November 2017 - 05:22 AM.
Posted 19 November 2017 - 05:36 AM
UPDATE3:I found a important registry value which controls BCD system store is vaild.
A dword named TreatAsSystem with value 1 in HKLM\BCD00000000\Description is very important.
After adding this value, bcdedit and all other BCD editors included built-in boot and failure recovery works.
But Hibernate is not working, wake PC with correct FirmwareBootDevice value will result in a clean boot, wake PC with unmodified FirmwareBootDevice value will result in a recovery screen(press enter is necessary to get a clean boot).
Now the only way to get hibernate working is vhd.(edit:maybe i should put boot files in a separate partition?)
UPDATE:
Hibernate is fully working after i put boot files in a separate partition with the modification of FirmwareBootDevice. No need to re set FirmwareBootDevice every wake up, only clean boot needs. Windows will not load BCD after wake up, you should load manually.
UPDATE2:
I found a interesting fact. while HKLM\BCD00000000\Description\KeyName was not BCD00000000 (usually bcdboot and bcdedit will set external BCD store's Description\KeyName to BCD00000001,BCD00000002..., and bcdedit will remove the TreatAsSystem value while the store is external store), you don't need to load BCD store manually after wake up while Description\KeyName is not BCD00000000.
Maybe windows will unload the bcd store with Description\KeyName=BCD00000000 while system goes into hibernate?
Edited by nightrain, 19 November 2017 - 05:45 AM.
Posted 20 November 2017 - 05:20 AM
Would hibernation work with the AIO method that @devdevadev posted about? Or is it untested as of yet? Would it be possible to test it in a VM instead of doing a real/live installation? I've noticed that whenever I install Windows to a VM hibernation doesn't seem to be available. I think maybe it's because Windows detects it's booted from a VHD, perhaps some other image type (like VDI or VMDK, etc) would work better. Then again, booting from a VHD in real/live mode doesn't seem to allow hibernation either. This is one of the few reasons why I would rather not boot from an image file on a real, permanent install.
Posted 20 November 2017 - 10:40 AM
By the limitations of Microsoft VHD Controller driver, Windows do not support hibernate the system which stored to a vhd.
The only three ways to get hibernate working are:
1: Use the map command of GRUB4DOS, do not install Windows entirely to the VHD, install boot files to the VHD, when the VHD is attached, hibernate works.
If you use "VHD Attach" and make its service loaded before TrustedInstaller (by service dependencies), Windows Update works perfectly.
If you use "TotalMounter" to mount VHD and do not use Microsoft's driver. You can use every features in Windows included Metro Boot Selection Screen (but expect WinRE, WinRE need a custom WinRE.wim file to mount vhd, and modify winload.efi to winload.exe in BCD is necessary).
like this:
timeout 0 menu /bootmgr.vhd find --set-root /Windows/bootmgr.vhd map /Windows/bootmgr.vhd (hd0) map (hd0) (hd1) map --hook root (hd0,0) chainloader /bootmgr
2: Use Firadisk driver, do not install Windows to a VHD, do not install Windows entirely to the VHD, install boot files to the VHD, everything works thanks to Firadisk driver(you still need a custom WinRE image), the only disadvantage of Firadisk driver is Firadisk driver has no digital signatures.
See my previous post below:
http://reboot.pro/to...ndpost&p=193161
3: Use superfloppy to get Windows booting, then load BCD hive and modify three registry keys to get BCD loaded properly:
To modify HKLM\BCD00000000\Description\*, you need to modify permission.
HKLM\BCD00000000\Description\KeyName=BCD00000000 HKLM\BCD00000000\Description\TreatAsSystem=(dword)0x1 HKLM\SYSTEM\CurrentControlSet\Control\FirmwareBootDevice=multi(x)disk(y)rdisk(z)partition(w)
You can not put boot files in system drive in this superfloppy way, otherwise you can not wake up. Ways 1&2 are OK in every situations.
Edited by nightrain, 20 November 2017 - 10:45 AM.
Posted 18 December 2017 - 01:03 AM
Posted 21 December 2017 - 10:46 PM
Yes, a "repair installation" fails.However, I could not apply a "feature update" like 1709, as it is really a system version upgrade.
When it reboots in order to apply update, it starts to rollback my system.
[Execute.PostOOBE]
0=\$WINDOWS.~BT\Sources\SetupHost.exe /Media /Success /ClientId Media360 /ReportId 0785d7a0-de3a-48b3-975a-2d98044a7705
[Execute.RollbackOnline]
1=\$WINDOWS.~BT\Sources\SetupHost.exe /Media /Rollback /ClientId Media360 /ReportId 0785d7a0-de3a-48b3-975a-2d98044a7705
Do you get a file SetupPlatform.ini at all?[Execute.PostOOBE]
0=\$WINDOWS.~BT\Sources\SetupHost.exe /Media /Success /ClientId Media360 /ReportId 0785d7a0-de3a-48b3-975a-2d98044a7705
[Execute.RollbackOnline]
1=\$WINDOWS.~BT\Sources\SetupHost.exe /Media /Success /ClientId Media360 /ReportId 0785d7a0-de3a-48b3-975a-2d98044a7705
Posted 22 December 2017 - 02:36 AM
Yes, a "repair installation" fails.
Actually I wonder, you got a rollback at all.
I really don't know for sure. The first reboot (after windows prepared the update), Windows starts and I can see just a flash of a windows terminal window before it reboots (the "working on updates" should follow).
After that windows reboots and it normally starts a rollback procedure. With VHD solution, my boot will loops trying to start installation or rollback. I need to rebuild BCD (either booting with ISO or inside normal Windows after booting with wimboot).
With external USB, it can rollback and return to Windows.
Windows setup refuses to upgrade at all here. Without UEFI firmware and GPT disk, setup refuses at online "feature update" 1709 or a <1709 DVD>\setup.exe.
Anyway let's compare a BIOS MBR upgrade example.
bootsequence {7254a080-1510-4e85-ac0f-e7fb3d444736}
device ramdisk=[C:]\$WINDOWS.~BT\Sources\SafeOS\winre.wim,{b9586286-e526-11e7-83f0-e946df80e7d6}
There is a file D:\$WINDOWS.~BT\Sources\SafeOS\ReAgent.xml
<OperationParam path="$WINDOWS.~BT\Sources\SetupPlatform.exe /execute Install:\$WINDOWS.~BT\Sources\SetupPlatform.ini"/>
And C:\$WINDOWS.~BT\Sources\SetupPlatform.ini
I wonder, texted but not tested set RollbackOnline to Success.
What happens at a BIOS GPT disk?
Do you get a file SetupPlatform.ini at all?
Can you edit your local SetupPlatform.ini and set RollbackOnline to Success? What happens?
Or, there are anoter aproaches with a additonl real / fake / virtual UEFI hardware.
Attach a new GPT disk and the exiting hard disk to a virtual machine (VMware,Virtualbox).
I guess bootmgr was working fine for me. WIndows seems to be loaded. It is setup process that aborted my installation.
Sorry but I'll not be able to play args anymore as I got it working. I just adopted the UEFI emulation solution. It's quite simple and I think the cleanest of all. Windows works, all updates, including feature, works. I did not tested hibernation but it might work as well.
Thinking on using this same HD in a future PC (with UEFI), I created a UEFI SYSTEM partition.
It saved my day. On WIndows ISO installation, I just mapped this system partition (A:) using diskpart and installed the bootmgr to it forcing UEFI mode:
bcdboot C:\Windows /s a: /f UEFI
As I dual boot with Linux, I have grub2 as boot manager. I just created this simply entry:
menuentry 'Tianocore' --class tianocore --class os $menuentry_id_option 'tianocore-memdisk' { insmod part_gpt linux16 /usr/lib/syslinux/memdisk initrd16 /boot/tianocore/tianocore.img }
Where tianocore.img comes from this old repo (I really could not find a prebuilt image at the current repo). It boots, looks for an valid UEFI partition and boots windows (the only UEFI OS). It just works.
I just wonder why tianocore could not find my WIndows DVD. It did tested my USB devices for a storage, so it would only be a matter of copying all DVD files to a USB drive.
In summary (considering that I already have grub2 in use):
I do recommend "UEFI emulation" for long-term installation (that will need feature updates). For temporary installations with short live that does not need updates, wimboot is very clean.
Posted 22 December 2017 - 05:39 AM
Thanks for the feature upgrade example.I got it working. I just adopted the UEFI emulation solution.
Posted 22 December 2017 - 09:15 AM
But, given that the Tianocore image works fine on your hardware (cannot say if it does on *all* hardware), if I get this right one could boot "normally" from the BIOS and have the UEFI booting via Tianocore ready, using it only when an upgrade is *needed*?
Kinda of an "emergency" alternative boot method?
Wonko
Posted 27 December 2017 - 09:16 PM
diskpart.exe sel disk N clean convert gpt create par efi size=100 format fs fat32 label="EFI" create par primRemark:
sudo gdisk /dev/sda n 3 34 2047 EF02 sudo mount /dev/sda1 /mnt sudo grub-install --force --boot-directory=/mnt /dev/sda.
Disk /dev/sda: 67108864 sectors, 32.0 GiB
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 67108830
Number Start (sector) End (sector) Size Code Name
1 2048 206847 100.0 MiB EF00 EFI system partition
2 206848 67106815 31.9 GiB 0700 Basic data partition
3 34 2047 1007.0 KiB EF02 BIOS boot partition
sudo gdisk /dev/sda r p o h 2 yInstall Windows to the hybrid partition.
menuentry "GPT Partion boot: /Windows/boot.vhd" { insmod part_gpt linux16 /boot/syslinux/memdisk harddisk raw initrd16 (hd0,gpt2)/Windows/boot.vhd } menuentry "Win 10 setup /bootmgr - hybrided MBR partition required" { set root='(hd0,gpt2)' ntldr /bootmgr boot } menuentry "grub4dos" { linux16 /grub/grub.exe }.
Posted 28 December 2017 - 12:22 PM
@cdob
Semi-random idea, maybe useful, maybe not.
How large is the .vhd? (like 100 Mb or so, but could be even less, right?)
Is it contiguous (or can it be made so)?
I mean, IF it is RAW AND IF it is contiguous, one could make a direct mapping in the (hybrid) MBR for the extents of the .vhd.
Wonko
Posted 22 November 2018 - 02:26 PM
Given a 64 bit Windows 7 and up:http://www.msfn.org/...comment=1142954
should work at a 4 TiB disk, not tested. Remember to backup the disk.
Start within first 2 TiB LBA, partiton size below 2 TiB
67106815 - 206848 = 66899967
Grub4dos chainloaded:
partnew --active (hd0,0) 7 206848 66899967
Grub4dos writes the protective partition too.
Why you mentioned grub4dos partnew code for your 32GB GPT disk while it seems to useful only in case of > 2TB MBR HDD. Is it not a bit confusing....?? Is partnew command trick also part of your hybrid approach for > 2TiB GPT HDD ? or mentioned just for >2TiB MBR HDD as a side note ?
New game:
Kinda of an "emergency" alternative only BIOS boot method: temporary hybrid MBR
should work at a 4 TiB disk, not tested. MBR or GPT ???
Will hybrid approach also valid for 4TB GPT USB-HDD ? You had mentioned >2TiB MBR limit stuff at the end of your GPT Hybrid approach. AFAIU, Jaclaz suggested grub4dos partnew command for >2TiB MBR HDD not for >2TB GPT or Hybrid HDD ? I want to test above Hybrid-MBR approach in 4TiB GPT USB-HDD so that GRUB2 will work in 4 TiB GPT ?.
Should I also consider >2TiB workaround of partnew during GPT partitioning of 4TiB USB-HDD ?
cdob , Please suggest GPT Hybrid-MBR partitioning for 4TiB USB-HDD. Should I also consider >2TiB partnew workaround of Wonko in Hybrid Windows Partition ?
Posted 22 November 2018 - 03:29 PM
Is it not a bit confusing....??
It wasn't until you made it so by mis-mix-quoting cdob.
There is very little actually confusing in the original post.
1) a new approach was proposed by cdob
2) this new approach has been tested succesfully by cdob on a 32 GiB disk
3) it is the (educated) guess of cdob that this same new approach might work on 4 TB disks
4) the new approach has NOT been tested on 4 Tib disks
5) what jaclaz proposed on msfn (and cdob quoted) is simply that the 32 bit width of the MBR fields DOES NOT imply a 2 TiB disk limit, rather a 4 TiB disk limit if a "special" partitioning (2 partitions, each slightly below 2 TiB[1]) is used, AS LONG AS the OS supports it, results in that thread suggest that while XP won't work with this scheme, Windows 7 32 bit (and presumably and reasonably also Windows 7 64 bit) will
6) since the built-in tools in Windows 7 WILL NOT allow to create easily this partitioning scheme, jaclaz suggested to use grub4dos partnew (as an easy way to create that scheme, he could have suggested *any* hex/disk editor)
Wonko
[1] actually *any* number of partitions, as long as they ALL fit in the first 2 TiB + 1 (and one only) other partition till the end of the disk (or 4 TiB, whichever comes first).
Posted 22 November 2018 - 08:07 PM
That's a different device: a external device, not a internal disk.4TiB USB-HDD
Posted 23 November 2018 - 06:10 PM
A 4TiB USB hard disk reports most likely 4KiB per sector, seldom 512 bytes per sector.
Target 4TiB USB-HDD show bytes per sector as follows-
LogicalBytesPerSector : 512
PhysicalBytesPerSectorForAtomicity : 4096
PhysicalBytesPerSectorForPerformance : 4096
FileSystemEffectivePhysicalBytesPerSectorForAtomicity : 4096
Device Alignment : Aligned (0x000)
Partition alignment on device : Aligned (0x000)
Performs Normal Seeks
Trim Not Supported
Not DAX capable
Not Thinly-Provisioned
Can I try your GPT Hybrid approach in above type of 4TiB USB-HDD ? Any Hope ? Is it possible to install Grub2 in 4TiB HDD of 512 bytes per sector ? If so please suggest GPT Hybrid-MBR partitioning scheme for 4TiB USB-HDD...
Regards....
Posted 11 December 2018 - 04:14 PM
Posted 11 December 2018 - 04:40 PM
I'd like to know whether anyone has managed to find a way to install windows NT 6.* / 10.* using a GPT type disk on a system with bios firmware?
May be you also enjoy these difficult! stuff ?
https://www.sevenfor...-mbrs-duet.html
https://www.aioboot....pt-legacy-bios/
http://cmindnotes.bl...pt-disk-in.html
https://www.rmprepus...s/bios_gpt_boot
http://reboot.pro/to...-14#entry198148
http://reboot.pro/to...-15#entry205269
http://bbs.wuyou.net...read&tid=409654
Posted 11 December 2018 - 05:54 PM
Read post #356 by nightrain again.I could try using dism to install the svbus driver to the offline windows and try again
Posted 11 December 2018 - 06:08 PM
I could try using dism to install the svbus driver to the offline windows and try again - Setup may then be able to access the BCD store in the mapped floppy image - preferably file backed so that any edits made to the store are persistent. Alternatively I could try svbus with a small file backed .vhd containing a BCD store.
Any thoughts or suggestions?
If you are into experiments, and have time, do check the experimental approach here:
http://reboot.pro/to...e-9#entry193947
Heck, it had 475 downloads (but not the ONLY one that I was interested it at the time, by cdob), and no (meaningful) report.
Basically it makes the contents of the underfloppy also exposed/mappable as VHD, and in your case, nothing prevents from making a very small GPT partition for sectors 63-2047, see:
http://reboot.pro/to...e-4#entry186428
Of course it is your responsability to find a way to "hook" the VHD, svbus is very promising .
Consider how the 63-2047 range was born out of the requirements of the original scope (not modifying a "normal" GPT disk) but there is no need (in the case of a special made GPT disk to have the first partition start on 2048, so you could make a larger dedicated partition and place in it, besides the grldr and menu.lst a "normal" .vhd.
Wonko
Posted 11 December 2018 - 07:42 PM
map (hd0,2)/bootmgr.vhd (hd0) map (hd0) (hd1) map --hook root (hd0,0) chainloader /bootmgrI was able to successfully complete the Windows installation - several reboots were required.
Posted 11 December 2018 - 08:37 PM
@devdevadevMay be you also enjoy these difficult![/size]
stuff ?[/size]
https://www.sevenfor...-mbrs-duet.html
https://www.aioboot....pt-legacy-bios/
http://cmindnotes.bl...pt-disk-in.html
https://www.rmprepus...s/bios_gpt_boot
http://reboot.pro/to...-14#entry198148
http://reboot.pro/to...-15#entry205269
http://bbs.wuyou.net...read&tid=409654
Posted 11 December 2018 - 08:47 PM
Good.
Used bootlace.com --gpt command to install Grub4Dos code to the GPT disk (used dd.exe and a Windows 98 boot disk in QEMU then wrote the sectors back to the GPT disk).
I did a quick check inside bootlace.com, I am adding the info on the other topic:
http://reboot.pro/to...nd-gpt-support/
so it has less risks of getting "lost" in this looong thread.
Wonko
Posted 11 December 2018 - 10:41 PM
Quite the challenge. No luck yet....As a addional comlexity layer:
try a Windows 10 update installation too, this is the challenge nowadays.
Compatibility report (saved to your desktop) This upgrade path is not supported. Please close Setup and relaunch from the root of the media or go back and pick a different installation choice.Attempted to upgrade from Windows 7 Ultimate to Windows 10 (1809) Pro initially. Retried and selected Windows 10 (1809) Home edition. Both versions/editions of Windows 10 resulted in the same compatibility report error message.
ahci
Boot methods & tools →
Boot from USB / Boot anywhere →
another BIOS without AHCI switchStarted by mcluskyism , 04 Jun 2023 ahci, bios, bootmgr, grub4dos |
|
|
||
Boot methods & tools →
Boot from USB / Boot anywhere →
Tutorials →
Testing UEFI booting on a only Bios PCStarted by alacran , 23 May 2021 uefi, bios, aio_boot |
|
|
||
Groups →
Community forum →
Requests →
I think I bit off more than I can Chew.....(and that's WITHOUT teeth, too!)Started by Kapt Blasto , 01 Jul 2020 g4d, 4k, gpt, legacy bios, uefi and 5 more... |
|
|
||
Groups →
Security →
Forensics →
GPT disk offsetStarted by Tokener , 14 Aug 2019 gpt, offset |
|
|
||
system
Groups →
Project forge →
System_InfoStarted by wimb , 06 Jun 2019 system, usb, gpt, mbr, bios, uefi |
|
|
0 members, 1 guests, 0 anonymous users