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.8.9 / 3.9 Beta 4

Recommended Posts

Posted (edited)
1 hour ago, JFX said:


Hmm, the x86 version had a bug, should be fixed now.
The only requirement is Win7 or newer and an attached WofADK driver. 

 

Ok, thanks. I will retest it as soon as possible. 
 

Quote

 For the legacy boot menu, I think it would be to dangerous to
make an option for it.

I disagree here. Aside that the modern boot menu is more dangerous on its own ( a bootloader which waits for the entire OS loaded is the antimatter lacks one of its main purposes).

But assuming this is my personal/debatable opinion, surely turning an existing legacy menu in something ifferent w/o asking/warning IS more dangerows than abiding to the existing setting.

So, IMHO, if you don't want to add a GUI option to not confuse the less skilled users, make it available as a winntsetup.ini option (seem a fair compromise to me),but what you should really consider is to abide to the existing setting.

Assuming no explicit choice is made rom the gui/ini, if the bootloader is metro, leave it metro, if it's legacy, leave it legacy .

Edited by T-S

Share this post


Link to post
Share on other sites

Posted (edited)

I did not change it, it's a per boot entry option.
If you use bcdboot to add an entry, it will use the template from the selected OS.

Will consider an ini option for this.

Edited by JFX

Share this post


Link to post
Share on other sites
Posted (edited)

I have just tested (again) : installed W10 cloude on a native vhdx on  my backup notebook. Bootloader was legacy, turned to be metro.
 

The default template from single os, shouldn't be taken in account, unless the installed os is the only os on disk and the bootloader is installed freshly.

If the bootloader is preexisting and already populated, an item should be added to it and nothing else should be changed, seems pretty obvious to me. 

If it was for me I wouldn't even touch the default os and or the timeout, although that would have pros and cons depending the situation.

 

Edited by T-S

Share this post


Link to post
Share on other sites
Posted (edited)

@JFX

I tried your tool WofCompress. I got a corrupted winload.exe error when i tried booting from the compressed VHD.  Maybe your program does not handle filters of type *winload.*.
*winresume.* ?

Also the uncompress option does not work. I wanted to uncompress and compress again by excluding winload.exe explicitly

Edited by agni
correct username

Share this post


Link to post
Share on other sites

Hmm, yes there is something wrong with the exclusion.
But there is a much bigger problem with the hardlinks in WinSxS.

Share this post


Link to post
Share on other sites

Beta 2 is ready! it brings a new compact mode none.

This mode will only add wofadk driver and create a WimBootReCompress.ini
that will be used by the WofCompress tool.

Share this post


Link to post
Share on other sites

@JFX

I see that you have updated WofCompress as well - http://jfx.cwcodes.net/

What are the new changes ? Were you able to fix the hardlinks and the exclusion list issues ?

Share this post


Link to post
Share on other sites

Well, it should work now, at least I successfully used it to recompress a Win 7 and 8.1,

Share this post


Link to post
Share on other sites

Thanks. I tested it and it works fine.

Can you add a warning or error if the wofadk services is not running ?

 

Share this post


Link to post
Share on other sites
Posted (edited)

Sure, WOF driver version check added.

Edited by JFX

Share this post


Link to post
Share on other sites
On 28/04/2018 at 9:10 PM, JFX said:

I did not change it, it's a per boot entry option.
If you use bcdboot to add an entry, it will use the template from the selected OS.

Will consider an ini option for this.

+1 for bootlegacy in ini

Share this post


Link to post
Share on other sites
On 16.5.2018 at 12:07 AM, Sonic said:

+1 for bootlegacy in ini

Ok, added to Beta 4.

[Options]
LegacyBootMenu=1

Will disable fastboot and the metro style boot menu.

  • Like 2

Share this post


Link to post
Share on other sites

Another features request, if anyone is interested too ( in .ini ) :

Quote

; As my computer deploy .wim for others computers, I don't want WinNTSetup mount my current EFI boot partition
IgnoreMountPartitionGUID=\\?\Volume{eae15a21-6ccf-4c11-8270-b3beac326d3a}\
; In compact mode, apply wim can fit into 8Go VHD but WinNTSetup says "Not enough space"
IgnoreFreespace=1

:wub:

Edited by Sonic

Share this post


Link to post
Share on other sites

Hmm, I already removed the free space check for wimboot and compact (expect the new NONE) mode.

 

Quote

[Options]
NoBootMount=1

 

Share this post


Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Recently Browsing   1 member

×