New
#390
Nothing that is out of order, just been following your picture guide instructions:
So unless something there is incorrect....or missing....
Also you've not answered what commenting out line 4 does... Or was that to fix the upgrade issue (and or renaming the name and description of each image bug) when I would type in * for when it asks which image I would update instead of doing them one by one and restarting your little updater each time for each image that needs to be updated?
- - - Updated - - -
Ok, got it all sorted now and combined both 32-bit and 64-bit ISOs using WHD with recovery mode checked and with boot with BIOS and UEFI selected.
Final size came to around 9.6GB, far bigger than even a dual layer DVD9 could fit! So used NTLite to convert the install.wim into install.esd, created an ISO and now it will fit on a single DVD9 disc!
However, booting with this results in an unpassable driver request screen(tested using virtual box and a native box):
I don't suppose you have this... "mysterious" missing driver it's requesting, do you that I could integrate and retry?
Ok, googled around and tried a different method - used a windows 10 boot.wim (by the way, do you have a 7Updater with sha2 support but for windows 10? I tried it and it gave me an error (naturally) so can't integrate the drivers into win10 boot wim so it would be equivalently updated as my win7 boot wim....) in place of the windows 7 boot.wim that I have. It bypasses this mysterious missing driver request and I could select any of the 19 operating systems I have on the disc! Wooo!
Recovery mode does not work. After installation of windows and then rebooting so it boots off the DVD and clicking on the same link here, It says the windows version is incompatible with the recovery disc I have. So that either means WHD failed making a working recovery and repair environment for 64-bit windows 7 or it doesn't work with install.esd. Need further testing...
UEFI boot mode also does not work, I tested with Virtual box and it skips towards shell with no option to press any button to start the setup....
- - - Updated - - -
K - update 2; did some more testing with the recovery environment(using windows 7 home basic 64-bit if it matters --Yes it does matter, since 32-bit version home basic has no problem getting into recovery mode.) and yeah, it doesn't work even with the normal install.wim file(win2k8 example too):
lol something already wrong with my 2k8 r2 installation:
But, I don't know if it's a bug or glitch but I still managed to get into the repair and recovery mode:
But you need to click here and then click next:
Then you'll get this window and click cancel:
And then finally here you can either cross out with that x at the top right corner or click cancel again:
And then you should be able to get to this:
Ok, back to the boot wim, if you got windows 10 equivalent version drivers for both x86 and x64 boot wim, I'd like that please or else I get:
Oh yeah and is there a way to increase the description character cap here:
It seems I can only add about 3 lines of description and no more... I wanted to also add details about individual versions and why choose this over the others bla bla thing just for my own sake.
- - - Updated - - -
Oh yeah, coming back here, WHD's AIO with BIOS and UEFI selected, has its own BOOTx64.efi but apparently doesn't work:
but using yours, almost works(at least it shows the screen where you can press any key to boot from the DVD) but still get the same winload.efi error with both virtual box and native box!
Upon checking, your version appears to be RTM (which is older) over the one WHD created (that is newer) which is ldr escrow whatever version that is:
Last edited by Win7fuser; 27 Aug 2021 at 09:23.
Quote
