click-click Posted October 21 Posted October 21 (edited) @JFX or anyone with and idea. I have 2 usb SSD flash drives that are set up to boot either BIOS or UEFI. Both have 2 partitons and the layout is 100MB FAT and the other NTFS for VHDs and wim files. I have a laptop that has CSM support and allows both BIOS and UEFI booting. The priority is Legacy first and UEFI 2nd. One flash works as it should and uses the BIOS boot BCD when booting. The other drive for some reason always ends up using the EFI BCD. I must have done something to that flash that causes this, but I don't know what. Both BIOS and EFI BCDs are pretty much identical on both flash drives. Any idea what's causing the boot process to use EFI instead of BIOS for that flash? Edited October 21 by click-click
Antonino Posted October 21 Posted October 21 (edited) Just outta curiosity, do u have your mobo environment set to full UEFI, full bios or hybrid (CSM)? Edited October 21 by Antonino
click-click Posted October 21 Posted October 21 1 hour ago, Antonino said: Just outta curiosity, do u have your mobo environment set to full UEFI, full bios or hybrid (CSM)? Did you not read my post above? CSM support for both with priority Legacy 1st and UEFI last. I tried a few things such as renaming the EFI directory as EFI_ and that is the only way up to now to make it use the BIOS boot BCD. As soon as I rename it back to EFI, it reverts to UEFI for the boot. The only other difference between the 2 flash drives is 128GB vs 256GB. The other thing I did was to restore the 100MB partition from the working 128GB flash to the other flash and that crashes. If I let WinNTSetup update the BCDs, the crash issue is resolved, but it still defaults to booting EFI
Antonino Posted October 21 Posted October 21 (edited) in my experience, which is about non-usb booting, always with bios and just a few times with uefi, the only differences I have had between the two is in the last window (the setup one), which entailed my leaving it set to BIOS in the former case (all mbr) and setting it to ALL in the latter case (boot disk gpt with the uefi partitions and vhd os mbr, intact as it has always been). u can try setting winntsetup to UEFI, but i suggest u do it when it fails in ALL (hybrid) mood. if u do not succeed, I suggest u ask jfx or wimb, who should be more conversant than me. in general, I can tell you that the main thing for booting is the bcd of the carrier boot disk, not the bcd of the os vhd, which can stay the same as it is in bios. Edited October 22 by Antonino
j7n Posted November 1 Posted November 1 What is the copy "Mode" listbox with entries for Wimboot and Compress. I don't see a help-file that describes them. I can see that some would enable compression, which is much extra work for the computer, and that the default choice is blank. And they have traffic signal indicators. It's a big lousy that the latest version is x64 and requires NT6, meaning I can't launch it from an XP boot CD to install Windows 10. I must first install Windows 7 to use it.
Antonino Posted November 1 Posted November 1 (edited) the wimboot function is a wimb legacy, some sort of a collector (vhd) of pointers to a base wim file working simultaneously, as all vhd content practically points to it. the innovation of this latest mode u mentioned has the wim file in its own "belly" system volume information, if u wish. but exactly on the same wavelength as urs in the post aboe, even further strain would be placed on the cpu, at the cost of time as well. because it is much quicker in full-vhd mode. as for the os legacy, my friend virgus would pretty much sympathize with u, as he dows some stuff that needs windows vista, xp and 7. me, I am fine with 10 and 11, so my experience with legacy is mostly confined to whatever he tells me. only 1 thing I do requires 7 and I remember installing an ad hoc vhd a couple of times, but it would just take minutes - not a big deal. Your specific case, I remember virgus mentioning it too some weeks ago. Edited November 1 by Antonino 1
Antonino Posted November 1 Posted November 1 anyway check with ramsey at zone94.com xp patch and you will know better.
king8358 Posted November 20 Posted November 20 How to automatically load the registry and SRS driver into the target system when installing the system using WinNTSetup
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now