Jump to content











Photo
- - - - -

Wimlib-clc

wimlib archiver compression backup deploying wimlib-imagex wimlib-imagex gui system backup

  • Please log in to reply
34 replies to this topic

#26 AnonVendetta

AnonVendetta

    Silver Member

  • Advanced user
  • 901 posts
  • Location:A new beginning.....
  • Interests:Self-development, computing
  •  
    United States

Posted 4 weeks ago

I never really considered wimlib as a backup solution, will have to give it a look. Does it restore NTFS-compressed files in their compressed state? That's big for me, i dont feel like recompressing all my volumes after a restore.

#27 alacran

alacran

    Gold Member

  • .script developer
  • 2095 posts
  •  
    Mexico

Posted 4 weeks ago

On Windows there are two different compressions:

 

Compact Mode, Levels are 4K, 8K, 16K and LZX, new from 10, but having wofadk.sys driver installed on the OS, can be used also on older OSs. All new or modified files will be uncompressed. Files are unfragmented but free space is not.

 

And the old NTFS compression available since XP and/or Win NT 3.51. All new or modified files will be compressed. Induces high file fragmentation and its compression level is lower (about 75%) than the Compact 4K (about 66%)

 

Compact Mode Compression and wimlib:

During Apply you can always select the Compact Mode you want, this applies to Compact Mode new installations or when re-deploying from your WIM image backup.

 

NTFS Compression and wimlib:

If you make a Wim image of a drive or of a folder that is NTFS compressed, its captured WIM image keeps that characteristic and when you re-apply it, it will be NT compressed.

 

NTFS Compression + Compact Mode compression + wimlib:

If you capture a NTFS compressed drive or folder and latter apply it using Compact Mode Compression any new or modified file will be NTFS Compressed, On USB devices I usually use this "double compression" on the folder. drive or VHD where I have my Portable Programs as some of them as LibreOffice make some write or create some Log files, this way they are created or modiffied at least NTFS compressed.  Of course any time we can run WOF_Compress by wimb to recompress (a single file, a folder or a drive) with Compact Mode LZX.

 

NOTE: As I have confirmed making several experiments the opposite do not work, Compact Mode compression is lost if we latter apply NTFS compression. When a Compact Mode compressed file is copied to other location it looses its compression, but you can move it to other location on same drive (then no problem when defragmenting).

 

alacran


Edited by alacran, 5 days ago.
See Post No. 33


#28 gbrao

gbrao

    Frequent Member

  • Advanced user
  • 446 posts
  •  
    India

Posted 4 weeks ago

deleted. will create a separate thread.



#29 alacran

alacran

    Gold Member

  • .script developer
  • 2095 posts
  •  
    Mexico

Posted 4 weeks ago

@ gbrao

 

Hi my friend.  I was curious and just tested your program.

 

For very basic use (Capture and Apply) your version works fine.

By the way the wimlib-imagex version is obsolete.

 

But in my opinion it lacks many other features very useful (for me at least), just to mention some:

  1. Create high compressed ESD image files (solid LZMS image files, also know as Recovery compression too), very useful for AIO (All In One) images.
  2. Wimboot Installations.
  3. Delete Indexes.
  4. Delete/replace files/folders on a WIM file.
  5. Extract files from a selected  list, etc.

NOTE: This is not a request to include those features, as Wimlib_clc already has all that.

 

But as I always say: All depens of the user needs/prefences/likes.

 

Anyway your program does fine what is mentioned in the About first window.  And it may be usefull for non advanced users. Good work my friend.

 

I suggest you to upload it to Downloads section and a new topic will be created, and we all better stop hijacking this topic that is dedicated to Wimlib Clc, as the topic title explicity says.

 

alacran



#30 alacran

alacran

    Gold Member

  • .script developer
  • 2095 posts
  •  
    Mexico

Posted 4 weeks ago

Only for users that want to use Wimlib-clc Build 210610 (or newer) as fully portable writing all the config info to the file Wimlib-clc.ini located on the root of the program folder.

 

Attached the bare minimum Wimlib-clc.ini file (ini.7z), just extract and copy it to the root of program folder before run the program for the first time, and the first time it runs it will use it automatically, then select your prefered options and on top menus open Options  >>> Save settings/configurations now, they will be saved on the \Wimlib_clc\Wimlib-clc.ini file from now on, as it was used since the first run.

 

In case the user has same issue mentioned by gbrao on post No. 20

 

 

 

One suggestion : please mention how exactly to make it portable (settings saved in same directory as the exe).n I first ran it settings were stored in the reg. I selected 'save settings to config file'. The ini file was automatically created in AppData\Roaming. Shouldn't it be saved in the same directory as the exe ?

Also the reg entries were still present so the program kept on using those.

 

Easy solution:

  1. Close the program.
  2. Attached the bare minimum Wimlib-clc.ini file (ini.7z), just extract and copy it to the root of program folder.
  3. Extract and run attached *.reg file to delete the entries created in the Registry by Wimlib-clc Build 210610
  4. Also optionally go to AppData\Roaming\ folder and delete wimlib_clc folder, you can omit this.
  5. Run again the program and now all setting should be saved on Wimlib-clc.ini file.

 

alacran

Attached Files


  • Tokener likes this

#31 Tokener

Tokener

    Frequent Member

  • Developer
  • 333 posts

Posted 4 weeks ago

@alacran

thank you for clarifying subject "compression" in post #27.

 

@gbrao

thanks for providing your GUI.

 

 

I found wimlib GUIs a bit too complicated so I actually created one for my personal use.

 

Indeed, the interface should simplify the user's work as much as possible and recognize his intentions.

Therefore Wimlib-clc has some automations (option: suggestions) which should take over this.
The command line function (Send to) recognizes whether a directory / drive is to be captured

or an image file is to be processed.
If the source is determined (Capture), after successful selection of the target file, already image name / description is set. What more can you wish?
Therefore, for me the integration into the context menu of the explorer is the easiest method to have certain functions available.
Have you already tried this?

I would like to convince you of the simplicity of use. (I'm shure you noticed. :whistling: )
 

Best regards   T.

 
 

 

 


  • doberman likes this

#32 alacran

alacran

    Gold Member

  • .script developer
  • 2095 posts
  •  
    Mexico

Posted 5 days ago

@ Tokener

 

Hi my friend, I have just noticed on Download page for this program, there is no link to this SUPPORT TOPIC (as it is usually on all Download Pages).

I think in order to have all the info easily available for all members and readers, it could be good to add links there to this page and also to your recent topic: Adding WIMBoot capability to a previously captured Volume-image.

 

alacran


  • Tokener likes this

#33 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 5 days ago

Only for the record, NT compression is actually NTFS compression it dates back to NT 3.51 (and wasn't of course available on the 9x/Me as they had not any official NTFS support).

 

:duff:

Wonko



#34 alacran

alacran

    Gold Member

  • .script developer
  • 2095 posts
  •  
    Mexico

Posted 5 days ago

@ Wonko

 

Thanks for your comment, I already fixed post No. 27.

 

alacran



#35 vigipirate

vigipirate

    Member

  • Members
  • 94 posts
  •  
    France

Posted 5 hours ago

hello thank you for finishing the translation again errors in the not totally French tab attached the file

 

https://bayfiles.com...b-clc_fr-FR_ini







Also tagged with one or more of these keywords: wimlib, archiver, compression, backup, deploying, wimlib-imagex, wimlib-imagex gui, system backup

3 user(s) are reading this topic

0 members, 3 guests, 0 anonymous users