Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


JFX

WinNTSetup v3.9.4 / 4.0 RC1

Recommended Posts

Posted (edited)
On 10/1/2019 at 3:09 PM, JFX said:

Sure \Boot and \EFI folder should be decompressed, I'll add this.
But why you want this for drivers in Windows 10 too?

It is file bootmgr and file Boot\BCD that definitely need to be decompressed for booting VHD with grub4dos from RAMDISK in WimBoot mode.
Decompressing the whole folder \Boot and \EFI is not needed and would take more free space from VHD and increase the time to load VHD into RAM.

Booting with VHD in WimBoot mode from USB on various hardware can be improved when drivers are real files instead of WOF pointers.
It is used to make a Portable Windows 10 Operating System in VHD booting in WimBoot Mode and located on Portable SSD connected via USB.
But since Apply with wimgapi in WinNTSetup gives trouble in decompression of Windows 10 drivers, I think it is better NOT to add such option in WinNTSetup.

We can use Apply with wimlib using WIM file Captured with wimlib and modified Windows\System32\WimBootCompress.ini
if we want to have decompressed drivers in Windows 10 VHD booting in WimBoot mode.

Edited by wimb

Share this post


Link to post
Share on other sites

For Unattend the option right-click to open that file in notepad does NOT work anymore in 4.0 Beta 6/7/8

  • Like 1

Share this post


Link to post
Share on other sites

Thanks for version 4.0 RC1 which solves the Edit option for unattend.xml  :)

Did some testing with Apply of latest Win10 install.wim from Microsoft followed by wimlib Capture and then Apply in WimBoot mode using wimgapi.

It seems the RC1 version corresponds to the 4.0 Beta 8 version and everything is working as expected
and OK as long as the internal Windows\System32\WimBootCompress.ini is not modified.

Edited by wimb

Share this post


Link to post
Share on other sites
2 hours ago, yaschir said:

@JFX
 

I have BOOTICE v1.3.4 Portable. You can use it if necessary. I'm adding link here because it might be useful. :)

https://yadi.sk/d/1sG-x58J0iTaTw

Check from here:

to here:

 

jaclaz

 

  • Upvote 1

Share this post


Link to post
Share on other sites
21 minutes ago, jaclaz said:

Check from here:

to here:

 

jaclaz

You are right. I didn't notice.

 

Share this post


Link to post
Share on other sites

just discovered wimgapi (gimagex/winntsetup/dism) can support 54 non empty lines in [ExclusionList]

WimLib doesn't have this limitation.

is possible to add "None" compression to capture ? for large windows + data backup it's faster.

Edited by Sonic

Share this post


Link to post
Share on other sites

WinNTSetup v3.9.4 / 4.0 RC1 when install windows 10 all model error Registered Owner and Registered Organization error name display thanks edit this bug

Share this post


Link to post
Share on other sites
15 hours ago, Sonic said:

just discovered wimgapi (gimagex/winntsetup/dism) can support 54 non empty lines in [ExclusionList]

There is no such limit, but the ExclusionList section  should not be bigger than 32KB.

 

15 hours ago, Sonic said:

is possible to add "None" compression to capture ? for large windows + data backup it's faster.

Already supported on command line, will be added to GUI next version.

  • Like 1

Share this post


Link to post
Share on other sites

possible to add windows license type detection(in local windows installation tab)? from bios key

it save time to check, which version should b apply. eg. coresinglelanguage / pro

Share this post


Link to post
Share on other sites

No, license type detection would require to add a lot non redistributable MS files.
Just copy the key and use a PIDKey check tool.

Share this post


Link to post
Share on other sites

@JFX

Any plans on adding .ffu images to WinNTSetup, or maybe for future version 5.

Quote

To capture, deploy, and mount FFU images with DISM, you'll need to work in a Windows 10, version 1709 or later, or WinPE for Windows 10, version 1709 or later environment.

Source: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/deploy-windows-using-full-flash-update--ffu

Quote

Xpress-Huffman is used by default when an FFU is captured with DISM

Source: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/wim-vs-ffu-image-file-formats

FFU image format: https://docs.microsoft.com/en-us/windows-hardware/manufacture/mobile/ffu-image-format

alacran

Edited by alacran

Share this post


Link to post
Share on other sites
6 hours ago, alacran said:

Any plans on adding .ffu images to WinNTSetup, or maybe for future version 5.

I thought about it for version 4, but it would have required some GUI changes.
So it was to much work for a feature nobody cares about.

Maybe for version 5 (in a few years) ...

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...