Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Simultaneous Scheduling Priority
#41
OK, here's the mystery.  You showed me the WinPE produced after the HBS build of your ISO.  I actually looked at the contents of the OPE files delivered (using 7z as well).  7z shows both OPEs (delivered by the two different downloaders) as Win10-based... kinda weird.

I then let HBS build its WinPE through the Emergency Disk process (twice using two different installations) and VOILA, the one produced by the downloader marked "latest" indeed produced a Win11-based WinPE, even though 7z showed its OPE contents to be Win10.  The one produced by the v2 downloader produced a Win10-based WinPE.

I have no idea why 7z showed the OPE contents to be Win10 when it produces a Win11 WinPE via HBS.

I would suggest renaming your downloaders accordingly (to avoid confusion)... "v2" & "Latest" don't really coordinate well... maybe indicate the Base WIM being used to produce it.

As far as the OPE files and 7z... take a quick look yourself, maybe just to measure my sanity a bit  Huh  This is most likely a 7z issue of some sort when looking at OPE files.
Reply
#42
The other weird thing... although OPE is not supposed to be a supported format within 7z... it opens it anyway and shows contents dating from some different FileSet.


I'll not use it anymore for this purpose...
Reply
#43
I guess I'm nosy... is there a reason your OPE downloader doesn't just issue the baseline WIM rather than this OPE thing (of which I know nothing about), maybe a licensing issue?  Curious...
Reply
#44
(03-29-2025, 01:07 AM)Froggie Wrote: OK, here's the mystery.  You showed me the WinPE produced after the HBS build of your ISO.  I actually looked at the contents of the OPE files delivered (using 7z as well).  7z shows both OPEs (delivered by the two different downloaders) as Win10-based... kinda weird.

I then let HBS build its WinPE through the Emergency Disk process (twice using two different installations) and VOILA, the one produced by the downloader marked "latest" indeed produced a Win11-based WinPE, even though 7z showed its OPE contents to be Win10.  The one produced by the v2 downloader produced a Win10-based WinPE.

I have no idea why 7z showed the OPE contents to be Win10 when it produces a Win11 WinPE via HBS.

I would suggest renaming your downloaders accordingly (to avoid confusion)... "v2" & "Latest" don't really coordinate well... maybe indicate the Base WIM being used to produce it.

As far as the OPE files and 7z... take a quick look yourself, maybe just to measure my sanity a bit  Huh  This is most likely a 7z issue of some sort when looking at OPE files.

7ZIP just extracts the first file in the OPE file, which is the WINPE for X86 that is based on Windows 10, since Microsoft no longer offers new WINPEs for X86.
Reply
#45
(03-29-2025, 01:17 AM)Froggie Wrote: The other weird thing... although OPE is not supposed to be a supported format within 7z... it opens it anyway and shows contents dating from some different FileSet.


I'll not use it anymore for this purpose...

The OPE simply stores multiple files consecutively, which should be the reason why 7ZIP is able to open it, but only the first file.
Reply
#46
(03-29-2025, 01:22 AM)Froggie Wrote: I guess I'm nosy... is there a reason your OPE downloader doesn't just issue the baseline WIM rather than this OPE thing (of which I know nothing about), maybe a licensing issue?  Curious...

This has nothing to do with licensing, it's just that OPE saves the X86/X64 and ARM64 WINPE files into one file for the convenience of the user, besides WINPE is not just a WIM file.
Reply
#47
Thanx for all that info!  I feel "enlightened!"  Idea
Reply
#48
(03-29-2025, 10:56 PM)Froggie Wrote: Thanx for all that info!  I feel "enlightened!"  Idea

You are welcome. In fact we should thank you for helping us so much.
Reply
#49
It's a labor of love... your product has moved along nicely since its inception and is now positioned to do very well into the future.

Best of luck!
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)