Jump to content











Photo
- - - - -

Compact mode installs

compact mode

  • Please log in to reply
36 replies to this topic

#26 alacran

alacran

    Gold Member

  • .script developer
  • 1436 posts
  •  
    Mexico

Posted A week ago

I almost forget to comment this:

 

Some time ago I made a Compact 4K install on a VHD, and recapture it using wimlib on a new WIM file with wimlib standard LZX compression, latter I wanted to make a new install from this WIM file to take advantage of all removed (CR)Apps and other modifications made to the initial WIM used when first install, but this time an standard install without compression on a new big size VHD, to my surprise the files were installed compressed with Compact 4k as they were before.

 

So if you think your WIM file used for your final Compact install may be usefull some time in the future for an stardard install, better keep it safe, or you will have to start from scratch making a new lite WIM.

 

alacran


  • antonino61 likes this

#27 alacran

alacran

    Gold Member

  • .script developer
  • 1436 posts
  •  
    Mexico

Posted A week ago

@ Wonko

 

This is what I got

 

Total Free bytes = 2.891754150390625 GB

 

This info is right as Explorer reported 2.89 GB free.

 

alacran

Attached Files



#28 antonino61

antonino61

    Silver Member

  • Advanced user
  • 711 posts
  •  
    Italy

Posted A week ago

Maybe there is after all some issues with hidden or filesystem files and what not.

 

Another (easier) way try:

fsutil volume diskfree I:

 

:duff:

Wonko

this is what I got:

Attached Files



#29 alacran

alacran

    Gold Member

  • .script developer
  • 1436 posts
  •  
    Mexico

Posted A week ago

Some time ago a friend from MDL forum sended me to  test his final version of this usefull commands, they worked fantastic and they are now included in another tool he was improving.

 

All commands do is add links to the contex menu of PC link located on desktop, and the Explorer contex menu, but those links are very usefull to save several steps in many cases, the link names applied are localized on each system lang, also included commansd to remove the links if required. They need to be run as admin.

 

I want to share with you this commands, see attached 7-zip.

 

NOTE: Good from 7 to 10

 

alacran

Attached Files


  • wimb likes this

#30 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted A week ago

@ Wonko

 

This is what I got

 

Total Free bytes = 2.891754150390625 GB

 

This info is right as Explorer reported 2.89 GB free.

 

alacran

Good :), so this is the "right" way.

One day, when we have some spare time, I would be curious to know why you convert byte data into fractional GB (which are actually GIB). :unsure:

The output of the command is 3104997376.

The data in the image posted 3104997376 bytes 2.89 GB.

Check.  :thumbsup:

The only (minor, very little) issue is that unlike the GUI, the command does not provide directly the "used bytes" (which can be obtained anyway by subtracting free byte from total bytes).

 

this is what I got:

 

Alacran's report is useful as - if read together with the image in this post:
http://reboot.pro/to...talls/?p=215547

 

confirms that fsutil volume diskfree gets the "right" anount of free bytes, in the sense as "same as volume right click->Properties  in GUI".

 

A comparison with "nothing" does not help much. :dubbio:

 

:duff:

Wonko



#31 alacran

alacran

    Gold Member

  • .script developer
  • 1436 posts
  •  
    Mexico

Posted A week ago

Good news wimb just released VHD_WIMBOOT Version 3.0, now also capable to make Compact mode installs at 4X or LZX compression.

 

 

Update VHD_WIMBOOT Version 3.0
 
- Extra Mode Options:  APPLY       WIM File in Normal or WimBoot Mode or Compact Mode with XPRESS4K or LZX Compression
- Extra Mode Options:  CAPTURE WIM File in Normal or WimBoot Mode with XPRESS4K or LZX Compression 
- wimlib 1.13.2   https://wimlib.net/
- in WimBoot Capture file makebt\WimBootCompress.ini is used and copied to WIM folder Windows\System32  (property of wimlib wimboot)
  and in Normal Capture  WimBootCompress-Normal.ini is used as config file but Not copied - https://wimlib.net/m...wimcapture.html
 
Download: VHD_WIMBOOT-30  Or from GitHub VHD_WIMBOOT-30  
 

Manual:  pdf.gif  VHD_WIMBOOT.pdf   785.98KB   2 downloads

 

post-9517-0-45036400-1595821458_thumb.jp

 

From this post: http://reboot.pro/to...-10#entry215557

 

Just tested it recapturing my 6 GB VHD, copmpresed LZX and Reduced using cdb command base_winsxs.cmd, as said on a previous post the used espace on it was 3.1 GB, see: http://reboot.pro/to...ls/#entry215543

 

It was recaptured to a LZX compressed W10x64_MX_1.wim 2.42 GB and latter reapllied in Compact LZX mode to a 3.8 GB W10x64_MX_1.vhd having 2.91 GB of used size before firs boot, this size will vary a little after booting it, but right now it has 912 GB of free espace, see attached photo.

 

alacran

Attached Files


  • wimb likes this

#32 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted A week ago

here it yields file and folder counts, not lists.

Before I forget, possibly this (among the various nice Gammadyne tools):
https://www.gammadyne.com/cmdline.htm

https://www.gammadyn...line.htm#sizeof

 

Might be useful to both list and count.

 

And - while I am at it - gpatch:

https://www.gammadyn...line.htm#gpatch

might be useful as a replacement for hexalter (which homepage is MIA).

 

:duff:

Wonko



#33 wimb

wimb

    Platinum Member

  • Developer
  • 2904 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted A week ago

 

It was recaptured to a LZX compressed W10x64_MX_1.wim 2.42 GB and latter reapllied in Compact LZX mode to a 3.8 GB W10x64_MX_1.vhd having 2.91 GB of used size before firs boot, this size will vary a little after booting it, but right now it has 912 GB of free espace, see attached photo.

 

 

Very good figures for your Mini Win10x64  and Apply in Compact LZX Mode

 

For me some work to do according to your instructions

Before first install, first thing is remove all (CR)Apps and other unwanted things from the original WIM file using MSMG Toolkit,  in order to reduce  your WIM file used for installs.

 

but my present Mini 10x64 is already promising

 

M_04_2020-07-26_191217.jpg

  • alacran likes this

#34 alacran

alacran

    Gold Member

  • .script developer
  • 1436 posts
  •  
    Mexico

Posted A week ago

Your actual figures look very fine to me, I decided to start all this test with 10x64 Edu as many teachers and studends may have the possibility to activate it on the KMS service of the high school or college, then once legaly activating the first install, it is totally portable. An option to legaly activate the Home or Pro versions could be using your MS account, but I haven't tested this option.

 

Of course you have to be very careful when removing packages from the original WIM in order to don't have troubles latter, or you will have to repeat all the procedure. There is not a guide for this because all user needs are different.

 

Also the WIM and final VHD sizes depend a lot of additional installed software.

 

alacran



#35 alacran

alacran

    Gold Member

  • .script developer
  • 1436 posts
  •  
    Mexico

Posted A week ago

Wel, it is time to also talk about 7, 8.0, 8.1 and 8.1 Update 1 and their Compact and Wimboot installs capabilities.

 

8.1 Update 1: This was the first version having native Wimboot installs capability by means of the new wof.sys driver. I ran my first Wimboot test on this OS, and by extention it is also capable to Compact Installs, wof.sys driver (new versions) is same drive used by 10 to handle Compact Installs.

 

All the other mentioned OSs are not capable to run natively from a Compact and Wimboot install, but this is very easily solved if during first install using WinNTSetup we select Mode: CompactNONE, WinNTSetup will take care to install the wofadk.sys driver on the new install.

 

How this works:

 

When we download WinNTSetup and extract it to a folder and then run it for the first time it request user permision to download some files from MS servers, and wofadk.sys driver is one of them, it is stored on WinNTSetup\Tools\x64\DISM folder and on WinNTSetup\Tools\x86\DISM folder to use it when required.

 

But at the same time (if required by the OS) it also copies the driver (x86 or x94 version as required) to Windows\System32\drivers and  creates a new service on our current OS,  to load the driver every boot, making the OS now capable to make Wimboot and Compact install by means of WinNTSetup.

 

Then this way 7, 8.0 and 8.1 will be capable to run from a Winboot or Compact install, thanks to JFX the author of WinNTSetup.

 

Take a look close to the bottom right corner of the attached photo.

 

alacran

Attached Files



#36 alacran

alacran

    Gold Member

  • .script developer
  • 1436 posts
  •  
    Mexico

Posted 4 days ago

You can also create Junction Links on Wimboot or Compact Installs, if the need arise:

 

See: http://reboot.pro/to...nks-on-windows/



#37 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 3 days ago

You can also create Junction Points on Wimboot or Compact Installs, if the need arise:

 

See: http://reboot.pro/to...nks-on-windows/

Please review my comment on that thread, a Junction is NOT a Symbolic Link and a Symbolic Link is NOT a Junction.

They are similar but they are not the same thing.

 

:duff:

Wonko




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users