Jump to content











Photo
- - - - -

Mini Windows made with WinNTSetup

mini-vhd

  • Please log in to reply
163 replies to this topic

#126 alacran

alacran

    Platinum Member

  • .script developer
  • 2633 posts
  •  
    Mexico

Posted 2 weeks ago

I made a new review of my lines added to SySWoW.txt and now they are only 91 lines (all repeated lines and all files in SySWoW folder that don't have a respective file with same name present also in System32 folder were removed).

 

After removing all files that are not in the list anymore LibreOfficePortable and lz4_compressor are still working fine.

 

Also (on-line) cleared all Event Viewer Logs just before reboot, (as I now do after filedisk booting a MinWin VHD), and ran again Win_Reduce_Trusted-62, re-capture and re-apply using VHD_WIMBOOT_Trusted-67, and I got a good reduction in sizes, compared to the sizes in post No. 122

 

MinWin-10x64-LZX.vhd Used size In NTFS partition is now 906 MB was 936 MB  >>>  reduction 30 MB

MinWin-10x64-WB.vhd Used size in NTFS partition is now 57.2 MB was 58.6 MB  >>>  reduction 1.4 MB  (Gain doesn't seem very notorious, as in this case all reduced files are pointers and not real files).

MinWin-10x64.wim Size is now 812 MB was 840 MB  >>>  reduction 28 MB

 

 

For readers convenience I attached here following files:

 

Modded_SySWoW (2022-07-30).7z    Password = alacran

 

Clear_Event_Viewer_Logs.7z   Password = alacran

 

NOTE: I recommend to always run Clear_Event_Viewer_Logs.bat as admin just before shout down the MinWin OS when filedisk booting to remove all event logs, not required when Rambooting, or if the OS will be re-captured and re-applied as in WimBootCompress.ini [ExclusionList]  this two lines take care of that:

\Windows\System32\winevt\Logs\*
\Windows\System32\winevt\TraceFormat\*

 

JFYI - CCleaner has an option to clear all Event Viewer Logs, it still works fine in Win7 but it doesn't work anymore in Win10.

 

alacran

Attached Files


  • wimb and Tokener like this

#127 alacran

alacran

    Platinum Member

  • .script developer
  • 2633 posts
  •  
    Mexico

Posted 2 weeks ago

@ wimb

 

I think it will be good if you can add Clear_Event_Viewer_Logs.bat (mentioned in previous post), to the Custom_Command.cmd present in your Win_Reduce program, this can help to mitigated the acumulated garbage files in our MinWin VHDs after filedisk booting.

 

Not required in Mini VHDs as the folder \Windows\System32\winevt doesn't exist there.

 

EDIT:

This request was replaced by an easier approach mentioned in post No. 129

Just adding following line to Custom_remove_files.txt:   \Windows\System32\winevt\Logs\*.*

 

alacran


  • wimb likes this

#128 ericgl

ericgl

    Frequent Member

  • Expert
  • 340 posts
  •  
    Israel

Posted 2 weeks ago

alacran,

 

I would like to contribute something.

Attached is my BAT file for clearing event logs.

It works on Windows10 1809 or newer, due to use of a special ESC char, which Win10/11 CMD can use.

 

*If you open the file to view the code, use Notepad++, not Windows Notepad. It contains a special ESC character which Notepad++ displays properly.

I have also added an explanation of what the codes do in the comments inside the file.

 

The beauty of it is that the output on the CMD is nice and clean.

The clearing of the event logs is shown on the same line until finished.

Hope you'll find it useful.

 

EDIT1: Obviously, you'll need to right-click and run it as admin. I haven't added the code inside the file to check for admin privileges.

EDIT2: It is normal for some event logs to fail from getting cleared.

Attached Files


  • Tokener likes this

#129 alacran

alacran

    Platinum Member

  • .script developer
  • 2633 posts
  •  
    Mexico

Posted 2 weeks ago

@ wimb

 

I think it will be good if you can add Clear_Event_Viewer_Logs.bat (mentioned in previous post), to the Custom_Command.cmd present in your Win_Reduce program, this can help to mitigated the acumulated garbage files in our MinWin VHDs after filedisk booting.

 

Not required in Mini VHDs as the folder \Windows\System32\winevt doesn't exist there.

 

alacran

 

@ wimb

 

Forget about this.

 

I think it is easier to just add following line to Custom_remove_files.txt:

 

\Windows\System32\winevt\Logs\*.*

 

EDIT: Tested and I can confirm it is working very fine for off-line remove Event Logs.
 

 

@ ericgl

 

Hi Eric, thanks for your suggestion, I will test it.

 

About Clear_Event_Viewer_Logs.bat I have used it from 7 to 10 v2004 and it works great, I assume it should work fine also on 11 but haven't tested.

 

alacran



#130 alacran

alacran

    Platinum Member

  • .script developer
  • 2633 posts
  •  
    Mexico

Posted 2 weeks ago

JFYI
 
About the issue (making un-bootable a MinWin VHD) after using CATTrim on a MinWin VHD having installed SVBus driver, JFX posted a solution in this post:

 

Spoiler

 

He also included in the post a link to SVBus driver v1.3

I already downloaded it but haven't tested it yet.

 

JFX solution worked fine, but I found several additional *.log files (that never existed before) are created in catroot2 after off-line apply CATTrim and reboot

 

And I commented this:

 

 

Hi JFX

Thanks for the link to svbus_1.3, just downloaded it, but haven't tested it yet.

 

I can confirm adding this lines to Tools\CATTrim.ini solves the issue.  Now my MinWin with SVBus installed is capable of filedisk boot and Ramboot again if using CATTrim.

 

But I noticed after apply it, several additional *.log files (that never existed before) are created in catroot2 after off-line apply CATTrim and reboot:

 

C:\Windows\System32\catroot2\edb00001.log
C:\Windows\System32\catroot2\edb00002.log
C:\Windows\System32\catroot2\edb00003.log
C:\Windows\System32\catroot2\edb00004.log
C:\Windows\System32\catroot2\edb00005.log
C:\Windows\System32\catroot2\edb00006.log
C:\Windows\System32\catroot2\edb.log
C:\Windows\System32\catroot2\edbtmp.log

 

Each one is 2 MB (total 16 MB on first boot), so if filedisk booting all this garbage accumulates every boot, not when Rambooting as all this garbage is created on Ram every boot.

 

IMHO and with all due respect to you my friend, CATTrim command works fine, but it's not really useful to reduce the OS size and future growup, on the contrary it induces the accumulation of more garbage.

 

Of course as always it depends of user preferences to apply CATTrim to his/hers OS or not.

 

alacran

 

 

 

EDIT: JFX answer from this post: https://msfn.org/boa...ls_1223071_menu

 

 

@ alacran

 

These log files are just temporary, shutdown of cryptsvc will delete them.

 

alacran


Edited by alacran, A week ago.
New info was added


#131 alacran

alacran

    Platinum Member

  • .script developer
  • 2633 posts
  •  
    Mexico

Posted A week ago

JFYI

 

From: https://msfn.org/boa...ls_1223102_menu

 

 

Just finished testing all features available in the MinWin version created with WinNTSetup v5.25, all useful things are available and open fine, including Event Viewer, Task Manager, Services Management, MS Config, PowerShell, etc.

 

And all ornamentary and superfluous things including the (CR)Apps are removed.

 

Congratulations my friend you did a fantastic work.

 

Only thing I don't like of MinWin is during first boot after installation it takes a very long time to arrive to the desktop.   And during long periods it doesn't seem to be doing anything as the HD led is not flashing, but if pressing the Caps Lock or Num Lock Keys they work fine, so we can confirm it is not blocked so It is better to be very pacient, but I would like to know what the hell is the PC doing all this time when the HD led is not flashing.

 

By the way the lines added into Modded_SySWoW (2022-07-30) can be edited by commenting or deleting !\Windows\SysWOW64\mshtml.dll to squeeze a few more MB, (17.2 MB uncompressed, 7.34 MB if Compact LZX compressed).

 

Without losing the capability to run LibreOfficePortable and lz4_compressor, but doing it we lose the capability to read the HTML (.chm) help files into 32 bits programs.

 

alacran

 

 

Attached some pictures from Rambooting my 512 MB MinWin-10x64-WB.vhd

 

alacran

Attached Thumbnails

  • 1.png
  • 2.png
  • 3.png


#132 alacran

alacran

    Platinum Member

  • .script developer
  • 2633 posts
  •  
    Mexico

Posted A week ago

For readers convenience I attached here:

 

Modded_SySWoW_2022-08-01.7z   Password = alacran

 

Where !\Windows\SysWOW64\mshtml.dll line is now commented to save in our MinWin VHD 17.2 MB (uncompressed) or 7.34 MB (if Compact LZX compressed).

 

If you need to read HTML (*.chm) help files into 32 bits programs, just uncomment the line.

 

alacran

Attached Files



#133 alacran

alacran

    Platinum Member

  • .script developer
  • 2633 posts
  •  
    Mexico

Posted A week ago

JFYI

 

I want to share with all of you the following test.

 

PREAMBLE:

 

Until now all my MinWin VHDs were manually made as very frecuently I use certain sizes not available in VHD_WIMBOOT, and making them manually also allows me to name them as I prefer, so far all my MinWin VHDs have a 100 MB FAT-32 First Primary Active Partition..

 

Our fellow devdevadev asked me to check if a MBR - Bios/UEFI VHD made using WinNTSetup is capable to Ramboot in MBR/CSM and UEFI environments by means of respective version of grub4dos + SvBus driver.

 

NOTE: ONLY partition layout available in WinNTSetup to make a 2 partitions MBR initialized VHD, bootable in Bios/UEFI environments is having the FAT-32 Active Primary Partition as second partition.

 

Using as source my MinWin-10x64.wim captured with VHD_WIMBOOT as Wimboot LZX compressed (size 812 MB), that already has SVBus driver installed, and it is the same used in all my recent MinWin VHDs.

Made a 1 GB VHD named MinWin-WB.vhd by means of WinNTSetup:

  1. VHD MBR partitioned, fixed size.
  2. FAT-32 Second Primary Active Partition 100 MB, named ESP
  3. NTFS First Primary Partition the rest of the space.

 

PROCEDURE:

  1. Decided to make a Wimboot mode installation as it requieres only a very small VHD and the WIM file is applied in just a few seconds.
  2. Tried to install into the VHD, (NTFS partition), my MinWin-10x64.wim in Wimboot mode using WinNTSetup, it failed to install several times, and always gave me a message saying that wimlib_extact_image 0xF2: Failed to open a file, please see attached photo (it is pending to find the cause of this failure yet).
  3. Then used wimlib-clc program by Tokener to install MinWin-10x64.wim into the NTFS partition on the VHD in Wimboot mode, all was made perfectly fine.
  4. After this in an elevated command prompt I created the boot files/folders into the EFI (FAT-32) partition, required for Ramboot.
  5. I intentionally omited create the external boot files/folders into the HD.
  6. Using BootIce edited both BCDs into ESP partition first in Easy mode enabling Detect HAL and Kernel and boot in Test Mode, and disabling Metro boot manager, and latter in Professional mode added the option LoadOptionsString = DISABLE_INTEGRITY_CHECKS.

 

After this I just created the grub4dos entries:

MBR menu.lst:
 
I created the enty using same commands as usually, but in this case root is (hd-1,1) where the bootmanager resides now.

 

Applies to a Wimboot VHD located into internal HD (present case)

title MinWin-WB.vhd - SVBus  RAMDISK  - 1 GB - map as (hd)
find --set-root --ignore-floppies /MinWin-WB.vhd
map --top --mem /MinWin-WB.vhd (hd)
map --hook
root (hd-1,1)
chainloader /bootmgr
 

Applies to a Wimboot VHD located into a external USB device.

title MinWin-WB.vhd - SVBus  RAMDISK  - 1 GB - map as (hd-1)
find --set-root --ignore-floppies /MinWin-WB.vhd
map --top --mem /MinWin-WB.vhd (hd-1)
map --hook
root (hd-1,1)
chainloader /bootmgr

 

UEFI menu.lst:

I created the enty using same commands as usually, in this case I didn't need to edit the commands.

title MinWin-WB.vhd - SVBus  RAMDISK  - 1 GB - map as (hd)
find --set-root --ignore-floppies /MinWin-WB.vhd
map --mem --top /MinWin-WB.vhd (hd)
chainloader (hd-1)

It Rambooted very fine in MBR/CSM and also in UEFI


CONCLUSIONS:

As long as using the right commands in respective menu.lst, it doesn't matter if the Fat-32 ACTIVE Prinary Partitition is the second partition.
 
Even if latter is found the cause of the failure in WinNTSetup, and there is found a way to use it to apply my MinWin-10x64.wim that already has SVBus installed for second installation, I assume the BCDs created by WinNTSetup will have to be edited, if not as SVbus driver is not signed by MS the VHD will not be capable to filedisk boot or Ramboot.

 

EDIT: From: http://reboot.pro/in...422#entry221523

 

New SVBus_v1.3 signed was just uploaded.

 

v1.3 uses a different certificate that is not blacklisted so far, so there is no need to edit all the internal and external BCDs

 

 

 

PENDINGS:

 

Find the cause of the issue that caused that WinNTSetup wasn't able to apply my MinWin-10x64.wim captured with VHD_WIMBOOT to the VHD.

 

I need to check if VHD_WIMBOOT program by wimb is capable or not to install my MinWin-10x64.wim into a VHD created by WinNTSetup, having the FAT-32 Active Primary Primary Partition as second partition.

 

If it works fine doing this task, maybe there will be no need to manually edit the BCDs using BootIce. And also maybe could be no need to create manually both menu.lst entries

 

alacran

Attached Thumbnails

  • Failure.png

  • devdevadev likes this

#134 alacran

alacran

    Platinum Member

  • .script developer
  • 2633 posts
  •  
    Mexico

Posted A week ago

VHD_WIMBOOT program by wimb is not capable to install my MinWin-10x64.wim into a VHD created by WinNTSetup, having the FAT-32 Active Primary Partition as second partition, please see attached photo.

 

alacran

Attached Thumbnails

  • VHD_Wimboot.png


#135 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 16047 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted A week ago

Does that depend on the order of the positions of the partitions on disk or on the order of the partition entries in the MBR partition table?

 

Reference:

http://reboot.pro/in...showtopic=17984

 

 

:duff:

Wonko



#136 alacran

alacran

    Platinum Member

  • .script developer
  • 2633 posts
  •  
    Mexico

Posted A week ago

A  temporary re-order of the partitions before use VHD_WIMBOOT program doesn't seems to me as a good alternative.

 

Because all enties into BCDs, grub2 config file and menu.lst use the partition order number.

 

alacran



#137 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 16047 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted A week ago

It wasn't an alternative, it was a question, the answer might (or might not) be useful to understand what happens.

 

And I never hinted for the swap to be temporary, the BCD shouldn't be sensible to the order of partitions in the partition table, grub.cfg and menu.lst should, but since the partition entries are swapped those would be fine.

 

If you prefer, did devdevadev ask for the FAT32 partition on disk being the second one on disk or in the partition table? (and WHY? :dubbio: I mean what is the reason for having the FAT32 partition second?[1])

 

:duff:

Wonko

 

 

[1] given that most installs have been with the FAT32 partition first (both on disk and in partition table), is there a particular reason why this swap is wanted/needed?


  • antonino61 likes this

#138 alacran

alacran

    Platinum Member

  • .script developer
  • 2633 posts
  •  
    Mexico

Posted A week ago


If you prefer, did devdevadev ask for the FAT32 partition on disk being the second one on disk or in the partition table? (and WHY? :dubbio: I mean what is the reason for having the FAT32 partition second?[1])

 

:duff:

Wonko

 

 

[1] given that most installs have been with the FAT32 partition first (both on disk and in partition table), is there a particular reason why this swap is wanted/needed?

 

Because that's the ONLY partition layout available in WinNTSetup to make a 2 partitions MBR initialized VHD, bootable in Bios/UEFI environments.

 

I tought it was clear when I said in post No. 123

 

 

Our fellow devdevadev asked me to check if a MBR - Bios/UEFI VHD made using WinNTSetup

 

I fell sorry to say this my friend but your questions demonstrate your lack of knowledge in the use of recent versions of WinNTSetup.

 

EDIT: To make things more clear for non advanced users of WinNTSetup I edited Post No.123 and also added following NOTE

 

NOTE: ONLY partition layout available in WinNTSetup to make a 2 partitions MBR initialized VHD, bootable in Bios/UEFI environments is having the FAT-32 Active Primary Partition as second partition.

 

alacran



#139 alacran

alacran

    Platinum Member

  • .script developer
  • 2633 posts
  •  
    Mexico

Posted A week ago

I alredy informed JFX about the issue in WinNTSetup when trying to apply the MinWin-10x64.wim.

 

From this post: https://msfn.org/boa...ls_1223217_menu

 

 

Hi my friend.

 

I found an issue in v5.25, from my post: http://reboot.pro/in...e=6#entry221512


 

Tried to install into the VHD, (NTFS partition), my MinWin-10x64.wim in Wimboot mode using WinNTSetup, it failed to install several times, and always gave me a message saying that wimlib_extact_image 0xF2: Failed to open a file, please see attached photo (it is pending to find the cause of this failure yet).

 

Then used wimlib-clc program by Tokener to install MinWin-10x64.wim into the NTFS partition on the VHD in Wimboot mode, all was made perfectly fine.

 

 

For the complete info please read the full linked post.

 

Additional info that can be useful for you:

 

wimlib-clc has pre-set the parameter --recover-data in apply Tab.

 

Perhaps you are not using in WinNTSetup the parameter --recover-data in wimlib during apply.

 

--recover-data parameter emulates the way Dism works during apply.

 

And as a MinWin VHD had many cuts (per design), it is very possible the main source of the issue, and using the parameter --recover-data could help solve the issue (in case you are not usig it).

 

alacran

 

 

alacran



#140 adric

adric

    Frequent Member

  • Advanced user
  • 172 posts

Posted A week ago

JFYI

 

My W10x64_LZX.vhd (MinWin) used space is 1.04 GB, installed in a 2 GB single NTFS partition VHD, plese see attached photo.

Programs installed: Classic Shell, 7-zip and Sumatra PDF, also added Remote Regedit.
 

 

alacran

Sorry for the OT, but does Remote Regedit work like RunScanner from Paraglider?

Sadly, RunScanner no longer works from W10 LSTC (19044). Where can I get Remote Regedit. to give it a try?

Thanks
 



#141 alacran

alacran

    Platinum Member

  • .script developer
  • 2633 posts
  •  
    Mexico

Posted A week ago

It is in fact RunScanner from Paraglider.

 

You can go to this  post  for info and download it.

 

alacran



#142 alacran

alacran

    Platinum Member

  • .script developer
  • 2633 posts
  •  
    Mexico

Posted A week ago

I jut tested SVBus_v1.3 signed, and it is working fantastic.

 

For forum members and reader convenience it was uploaded to Downloads Section of the forum to keep it handy.

 

It allowed me to filedisk boot and Ramboot without the need to edit all BCD files.

 

.Download link to the forum Downloads Section: http://reboot.pro/in...ds&showfile=625

 

alacran


  • devdevadev and antonino61 like this

#143 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 16047 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted A week ago

I fell sorry to say this my friend but your questions demonstrate your lack of knowledge in the use of recent versions of WinNTSetup.

 

 

Ah well, it is good to be called ignorant in the morning, not that I ever claimed to know anything about WinntSetup use, let alone in recent versions, but actually no, I don't believe you feel sorry, 

 

 

:duff:

Wonko



#144 alacran

alacran

    Platinum Member

  • .script developer
  • 2633 posts
  •  
    Mexico

Posted A week ago

JFYI

 

I alredy informed JFX about the issue in WinNTSetup when trying to apply the MinWin-10x64.wim.

 

alacran

 

He said he will fix it in next version.

 

Following info is specially focused to non-advanced users, so I appologizy if this is boring for advanced users.

 

As for now WinNTSetup is not capable to Apply a MinWin WIM file to the NTFS partition of a mounted 2 partitions VHD.

 

And also VHD_WIMBOOT currently doesn't allow to install a WIM file to the NTFS partition of a 2 partitions VHD having the FAT-32 Primary Active Partition as second partition.

 

Only remaining options are:

 

In GUI:

 

Use wimlib-clc

 

In command line:

 

Use wimlib, I will use following examples to explain the commands required.

 

 

1 - Appling a WIM image index in Wimboot mode to the NTFS partition of a mounted VHD:

 

"Your Path to wimlib_x64 folder\wimlib-imagex.exe" apply "D:\Wimboot\MinWin-10x64.wim" 1 J:\  --wimboot  --recover-data

 

Where:

 

Your Path to wimlib_x64 folder  = Self explanatory.

 

wimlib-imagex.exe  =  Self explanatory.

 

apply "D:\Wimboot\MinWin-10x64.wim" 1  =  Apply D:\Wimboot\MinWin-10x64.wim index 1
 

J:\  --wimboot  --recover-data  =  To drive J:\  in Wimboot mode using --recover-data parameter.

 

 

2 - Appling a WIM image index in Compact LZX mode to the NTFS partition of a mounted VHD:

 

"Your Path to wimlib_x64 folder\wimlib-imagex.exe" apply "D:\Wimboot\MinWin-10x64.wim" 1 J:\  --compact=lzx --recover-data

 

Where:

 

Your Path to wimlib_x64 folder  = Self explanatory.

 

wimlib-imagex.exe  =  Self explanatory.

 

apply "D:\Wimboot\MinWin-10x64.wim" 1  =  Apply D:\Wimboot\MinWin-10x64.wim index 1
 

J:\  --compact=lzx  --recover-data  =  To drive J:\  in Compact LZX mode using --recover-data parameter.

 

 

To create the boot files/folders into the FAT-32 partition we can use this commands:

 

In an elevated command prompt run following commands, but edit them first as required.

 

bcdboot C:\Windows /s S: /f ALL

C:\Windows = Where Win is installed (just change C: for the letter of Windows OS partition as seen on the running OS or WinPE)

/s S:: = Where the boot files/folders will be installed (just change S: for the letter of your System Reserved partition as seen from the running OS or WinPE)

/f ALL Installs MBR + UEFI boot files/folders (can be omited if not required and only those that apply will be installed)

 

Alternatives to /f ALL:

 

/f BIOS        /f UEFI

 

 

alacran


  • devdevadev likes this

#145 adric

adric

    Frequent Member

  • Advanced user
  • 172 posts

Posted A week ago

It is in fact RunScanner from Paraglider.

 

You can go to this  post  for info and download it.

 

alacran

That has the same regscanner.exe (1.0.0.28) that I use. I launch it with the following parms similar to what you are doing:

D:\ThinApps\RunScanner64.exe /t 0 /ll /sd /y /m+  %windir%\regedit.exe

It works great launching and editing from W7/W8/W10(1607), but the regedit hook fails on an offline registry when launched from my W10 LTSC 21H2(19044) system. The systems I mentioned belong to my multi-boot setup and the offline systems can all be accessed by the current active system.

 

I'm at a loss right now how to get this working on LTSC.  The error below happens trying to edit an offline W10 (1607)

registry from LTSC 21H2. Has anyone built a minwin using an LTSC install.wim?

 

I guess this discussion doesn't belong here, but most of the threads about this tool are ages old. I can start a new thread if requested.

Attached Thumbnails

  • runscanner.jpg


#146 alacran

alacran

    Platinum Member

  • .script developer
  • 2633 posts
  •  
    Mexico

Posted A week ago

@ adric

 

I will answer you on this topic: Useful info for WinPEs, Wimboot and Compact installs

The place where is the info related to Remote Regedit. to avoid more off-topic posts here.

 

alacran



#147 alacran

alacran

    Platinum Member

  • .script developer
  • 2633 posts
  •  
    Mexico

Posted A week ago

JFYI

 

I will share here some info that could be useful for some of you.

 

Going back to have the FAT-32 partition as the first partition:

 

in Mini VHDs or MinWinVHDs, having in mind the main goal is save space I consider a 100 MB FAT-32 is excessive an a waste of space, that will be better used to increase the size and free space available of the NTFS partition.

 

On previous test building Mini VHDs I used a 32 MB FAT-16 ID: 0E partition, and I was able to make it work, but having certain troubles with the VHD when re-mounting it, and VHD_WIMBOOT doesn't work with VHDs created this way, so this approach was not the best option.

 

I found that if using a 40 MB FAT-32, ID: 0C, works very fine, and there is not any issue to latter re-mount the VHD to serve it.

 

And VHD_WIMBOOT is able to work fine with this VHD, to re-capture and re-apply.

 

Also found if we use lz4-compressor to externally compress the VHD, the FAT-32 partition allows us to get an smaller lz4 compressed VHD that if using a FAT-16 partition.

 

I assume this is because a FAT-32 partition is compressed better than a FAT-16 partition.

 

To make things easier for non-advanced users I attached here a set of command files and their respective TXT files, that can be used to easily build:

  • 5 GB to be used for first installation of MinWin in Compact lzx Mode using WinNTSetup.
  • 0.5 and 1 GB good for Wimboot VHD,
  • 1.5 and 2 GB good for LZX VHD,

But they need to be edited before use, with the current right paths that will be used in the user machine before use them.

 

Attached Create_VHD.7z   Password = alacran

 

The current info of my MinWin VHDs is:

 

MinWin-10.wim  >>>  842 MB

 

MinWin-10-LZX.vhd  >>>  1.5 GB

 

MinWin-10-LZX.vhd.lz4  >>>  946 MB  >>> 61.59 % of original size.  Only Ramboot capable using grub4dos (MBR and UEFI versions).

 

MinWin-10-WB.vhd  >>>  512 MB

 

MinWin-10-WB.vhd.lz4  >>>  19.6 MB  >>>  3.83 % of original size.  Only Ramboot capable using grub4dos (MBR and UEFI versions). It is loaded to Ram in WARP SPEED, I had no way to measure the time to do it.

 

Plese see attached pictures. On MinWin-10-WB.png left is just installed, right is when Rambooted and used it for some time.

 

alacran

Attached Thumbnails

  • VHD_F32-40MB.png
  • MinWin-10-WB.png

Attached Files


  • devdevadev likes this

#148 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 16047 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted A week ago

You should be able to create a 33-34 MB FAT32 partition, if 6 or 7 MB make a difference.

 

:duff:

Wonko



#149 alacran

alacran

    Platinum Member

  • .script developer
  • 2633 posts
  •  
    Mexico

Posted A week ago

Yes, but it seems a 40 MB FAT-32 is the smallests supported by VHD_WIMBOOT.

 

alacran



#150 ericgl

ericgl

    Frequent Member

  • Expert
  • 340 posts
  •  
    Israel

Posted A week ago

A bit off-topic:
I managed to get a complete list of all UWP apps available on the MS Windows Store repo (as of 2022-08-04) - The list is in the attached file.
You can use the winget install [app_ID] or winget upgrade [app_ID] commands to install via CMD or Powershell.
You will need to add Windows Package Manager (DesktopAppInstaller) to WinPE in order to use the winget command.
It is very convenient when you wish to install many apps in one go, in batch file.
 
 

 

Maybe I should start a new topic... :dubbio:

Attached Files


  • devdevadev likes this




5 user(s) are reading this topic

0 members, 5 guests, 0 anonymous users