WOF_Compress

if anybody told me how to create a new topic, I would do it right away.

well, I disabled both wifi and bluetooth from the network window, then I also detached all usb devices and rebooted --> wimboot took only 2 secs less than in the previous tests with all of it on and connected!

if anybody told me how to create a new topic, I would do it right away.

Select appropriate part of this forum e.g. Groups > Windows 10

Use Upper Right Button - Start New Topic - Give Topic Title .....

new topic started. now how do I move all our posts concerning that topic from here to there?

new topic started. now how do I move all our posts concerning that topic from here to there?

give me the post number(s) here and i can give it a try.

62-77

Can you Implement LZMS?

WOF_Compress Version 3.4 is on line - Download encrypted with password = bootwimb

- Added RunAs Trusted Installer

- Improved Display of Used Size of Drive Before and After Compression / UnCompression

==

 

Good, It will make a better job now, I will test it and let you know my comments.

alacran

just downloaded it. shall I change any wimbootcompress.ini, or any other *.ini (for that matter) here too?

It is working very fine.

On compressing photo on first line WimBootReCompress.ini was selected but on second line the internal WimBootCompress.ini located into the VHD took precedence.

Attached comparative photo of final used sizes, at left is the old W10x64_MX_1.vhd and at right is the new W10x64_MX_2.vhd

As you can see W10x64_MX_1.vhd iis a few smaller, since it was reapplied with VHD_WIMBOOT-30 by means of wimlib, wich allways gives a few better compression than MS Dism and the W10x64_MX_2.vhd was just compressed in situ.

Comments:

On W10x64_MX_2.vhd only 2 files were fragmented but the free space was highly fragmented as usuall when compressing in situ.

W10x64_MX_1.vhd was almost perfectly defragmented as it was when captured, only BCDs were fragmented wich is understandable since they were modiffied by VHD_WIMBOOT-30 after applying it.

alacran

it works as before, whether I run it as ti or not. so, I repeat, with lzx.bat I get more free space.

@ wimb

Forgot to comment this:

On WimBootCompress.ini very last version this two lines were added, as on the version on VHD_WIMBOOT-30, but they do not exist on WimBootReCompress.ini, not a big deal, I added them on my copy but I suggest you to update the download.

\Windows\System32\pwdrvio.sys
\Windows\System32\pwdspio.sys

A little history about this two lines for future readers:

The mentioned files are created by PartitionWizard (even my portable version does it) and are loaded during boot (I don't know for what reazon), but if they are pointers you can't boot a Wimboot VHD, then in the case of compact installs I assume it is better to have them uncompressed, just in case. They are 18.7 KB and 12.2 KB respectively, and in case this files do not exist, there is no problem.

About this:

 

On compressing photo on first line WimBootReCompress.ini was selected but on second line the internal WimBootCompress.ini located into the VHD took precedence.

As my  actual WimBootReCompress.ini and the WimBootCompress.ini into the OS been compressed are just the same then I didn't notice any difference.

I assume this behaviour is in your code.  But I would like to know what is the logic you used on this part, as I don't know the logic you used I'm thinking in potential problems, but better will wait for more info before commenting or suggestig anything, please have in mind this is with the best intention of being helpful.

Remember the modded WimBootCompress.ini we both have been updating and testing during some tiime works fine from 7 to 10. As long as versions before 8.1 Update 1 have wofadk.sys.

alacran

I use partition wizard too. the former file is present here but diskspace used is 0, which I think means that it is a pointer. the latter file is not present here, in any form. the system is running wonderfully.

Remember I have made many test not only on Win10 as you, and I'm always thinking to make things clear and easy to follow for other people, and at the sane time trying to prevent any real and potential cause of issues on practically any PC and programs, and your way of doing things only apply to your machine and your favorite programs.

My test have being Rambooting  7, 8.0, 8.1 U1 and 10 Wimbooting VHDs and filebooting Compact installs, unfortunately I don't remember what version I was running when this happened on first or secont time.

it never happened to me before until one day when testing the ffirst install VHD I decided to test the links to my portables one by one openig each program, at that moment the 2 files were created (I lknew this latter), and latter on final VHD when rambooting and just after loading the VHD to RAM when the system started to boot I got the message; The system can't open the file pwdrvio.sys maybe it is corrupt or something with same meaning,

Then I deleted the pointer, and copied the file to same path on the VHD, on next boot same message but this time for the file pwdspio.sys, after doing same fix as in the other case, no more troubles. Also tested just removing both files and it also worked fine,

Then if the files do not exists or if they are full size (not a pointer), I don't have this problem.

My first solution was try to keep sure to delete both files before final captue, untill I forgot to delete the files on a new build, and had same problem again.

So I am totaly sure what caused the problem and the alternatives to fix it, and the easier and foolproof solution is just incude the 2 lines in the [PrepopulateList] and if they exist they will be copied full size, if they don't exist then they will not be copied and no problem.

Now I am thinking that same issue can happend on Compact installs or after compressing the drive as you want to take it, and if both files exist and are so small it is better to prevent a potential problem.

alacran

ok, u r all right. the thing is that if I have a situation here, I do not think this situation only applies here; it might apply everywhere, since it applies here, which is possible, albeit not so probable. in this specific case, my partition wizard is portable, for a change. I guess everybody here is trying to help, in anyway we can. me, I wish I knew a lot more about info-tech than I do, so I put my enthusiasm and goodwill to contribute to the growth and development of desktop pc usage for everydoby's sake, and my own as well.

@ wimb

 

A little history about this two lines for future readers:

 

The mentioned files are created by PartitionWizard (even my portable version does it) and are loaded during boot (I don't know for what reazon), but if they are pointers you can't boot a Wimboot VHD, then in the case of compact installs I assume it is better to have them uncompressed, just in case. They are 18.7 KB and 12.2 KB respectively, and in case this files do not exist, there is no problem.

 

alacran

And

it never happened to me before until one day when testing the ffirst install VHD I decided to test the links to my portables one by one openig each program, at that moment the 2 files were created (I lknew this latter), and latter on final VHD when rambooting and just after loading the VHD to RAM when the system started to boot I got the message; The system can't open the file pwdrvio.sys maybe it is corrupt or something with same meaning,

 

alacran

Are you reading or drinking?, you can't do both.

alacran

no no, I am not drinking, I am reading, sorrry I did not see it. it must be old age. I still do not think it depends on the compression of the file, but I might be wrong. If it depended on compression I would have the same problem, don't u think?

Your logic is almost impeccable Mr. Spock.

But there is also a variable you haven't take into consideration my friend, the program.

About the program:

-The original program is not portabe. This is a fact. EDIT: Wrong, free version is now portable.

-Maybe the guy that made your portable did a better job moddifying it to make it portable,

-The version of the original program used to make your portable, it is possible your version do not require to load those damn files during boot.

-It is a fact yours and mine act in different way, mine create problems if it is a pointer when rambooting.

-One of us is a damn liar.     Don't take this seriously. Just joking.

Anyway I mounted my 10x64  Compact-LZX & reduced VHD to make some pictures, Please make exactly same pictures and attach them to your next post.

alacran

Just went to the program page and there is v12, now free  & Porteble, I remember I downloaded an installed the v11 or maybe v10, but it was not portable AFA I can remember.

I'm going to test this version 12 and see if it likes me.

Also will check if the problem was solved and let you know.

alacran

version 11 is portable and version 12 as well.

On compressing photo on first line WimBootReCompress.ini was selected but on second line the internal WimBootCompress.ini located into the VHD took precedence.

 

That lines with Custom exclusion list and system exclusion list in your photo are generated by WofCompress.exe Tool of JFX.

When you select Checkbox Use Wof Compress Tool  then the only thing my program does is to launch the Tool of JFX.

In the command line the Custom exclusion list is given as parameter. It might even be that both exclusion lists are used by JFX.

The [PrepopulateList] Section where you asked to add entries for the Partition Wizard is not used by the Tool.

The [CompressionExclusionList] Section is used by the Tools for Compression.

[PrepopulateList] Section is used in Apply of WIM file and determines what files will be applied as real file instead of as WOF pointer.

[CompressionExclusionList] Section determines what files will be excluded from Compression.

When the Checkbox is not selected then my program code is used.

Run RunAsTI64.exe first and then launch WOF_Compress_x64.exe from Command Window is needed to be Trusted Installer in this case.

I hope things are more clear now.

==

@ wimb

Ok, let's see if this summary is correct. as I think:

There are 2 programss embeded on your WOF_Compress, depending of check box selected one of them will be used:

Use file list for drive (the version you and erwan.l developed): It uses (by default) Compress_FileList.txt for the list of files that will be compressed and Compress_Exclude_Files.ini wich the listed files will not be compressed because in many cases files they are allready compressed and if trying to compress it will be a waste of time and/or some files are there for safety pouposes an avoid compressa vital files that needs to be uncompressed allways.

Use WofCompress Tool: When selecting this option, this uses (by default) WimBootReCompress.ini, and it will be added as  a parameter to your command that will launch WofCompress.exe of JFX latter. Then once you select Compress or Decompress Button the program will launch the command line program WofCompress.exe of JFX.

But if your program detects the Windos Directory is contained iin the path of your selection to commpress, your program automatically launch coded instruction to  RunAsTI64, before sending your command to run WofCompress.exe of JFX.

I have a Question here about Compress_Exclude.ini, is it used in some part of the default process or it will be used (and then replacing WimBootReCompress.ini), only if manually selected on the Exclusion File selector?  

I assume it will be used (and then replacing WimBootReCompress.ini), only if manually selected on the Exclusion File selector but want to confirm with you.

So far I think this is the internal procedure as I understand it.

I haven't seen before WofCompress.exe of JFX calling WimBootCompress.ini, but since you allready told me that is not in your code and it is done by WofCompress.exe it is almost sure I just never pair attention before to the first lines and concentrated my attention in the info given about processed, compressed, excluded (etc) files.

Then the questions here are:

 WofCompress.exe uses both WimBootReCompress.ini or any custum file selected on your program and added as a parameter in your command line to lauch WofCompress.exe as a fist filter and then (if exists) the WimBootCompress.ini contained into Window\System32 of the system under compression as a second filter?

Or it simple ignores WimBootReCompress.ini and uses the WimBootCompress.ini contained into Window\System32 of the system under compression?

Is WimBootReCompress.ini only a fall back option?

I allready know you don't know the code used into WofCompress.exe but IMHO it is important to know the logics used here.

I know Dism (& wimlib) only uses [ExclusionList] during Capture ignoring all under this section and don't coppying the content  under that section to the WIM,

And during Apply [PrepopulateList] is used to copy to the target drive all content on it as real size files not pointers or not compressed in both cases Wimboot or Compact mode install, and do not copy anything under [ExclusionList] even if it exist.

In acordance with the info you meentioned here:

 

The [PrepopulateList] Section where you asked to add entries for the Partition Wizard is not used by the Tool.

The [CompressionExclusionList] Section is used by the Tools for Compression.

[PrepopulateList] Section is used in Apply of WIM file and determines what files will be applied as real file instead of as WOF pointer.

[CompressionExclusionList] Section determines what files will be excluded from Compression.

The [PrepopulateList] Section where you asked to add entries for the Partition Wizard is not used by the Tool.

The [CompressionExclusionList] Section is used by the Tools for Compression.

If WofCompress.exe allows to make a compression having only WimBootReCompress.ini

Then this means if WimBootReCompress.ini can be used alone all those files not in its [ExclusionList] will be compressed, this can cause a disaster and just to mention some critical files that could be compressed see following list:

*winload.*
*winresume.*

wofadk.sys  >>> This the file that makes the OS capable to read pointers or compressed files and it never be a pointer or compressed.

\bootmgr
\Boot\BCD
\EFI\Microsoft\Boot\BCD

If WofCompress.exe allows to make a compression using only WimBootReCompress.ini

This is a big potential problem: Lets think a user having on his running standard install (7, 8.0 and 8.1), after running WinNTSetup for the first time wofadk.sys and its respective service to run it, are installed and running, and then that system is capable to be compressed, but as those systems lack WimBootCompress.ini, then WimBootReCompress.ini will be the only one taking care wich files must not be compressed.

But we have two options to avoid this problem:

Verify if the system allready has and if not Copy to C:\Windows\System32\WimBootCompress.ini our modded WimBootCompress.ini (wich have proven to be reliable on this scenarios) file before start the compression, maybe after running  RunAsTI t(just in case). This is my favorite option.

Second option is copying from our modded WimBootCompress.ini, all under [PrepopulateList] section to WimBootReCompress.ini [ExclusionList] section, but as there is the option to select other Exclusion Files, this option may not be the safer.

Your friend

alacran

I did some testing and it turned out that I had some misunderstanding of how Exclusion works in case of the WofCompress Tool of JFX.

I can say now:

The [PrepopulateList] section of the Custom list makebt\WimBootReCompress.ini 

and the system list \Windows\System32\WimBootCompress.ini are both used as Exclusion List by JFX Wof Compress Tool.

However things are more complicated. For Exclusion you must take into account the hardlinks 

Exclusion of WOF Compression of drivers requires also to Exclude the Driverstore since the files refer by hardlink to the same data on disk

Thus it is needed to use in this case

\Windows\System32\drivers\*.sys
\Windows\System32\DriverStore\*

The WofCompress Tool of JFX works already as Trusted Installer and my program does not auto launch RunAsTI64.exe

WofCompress Tool of JFX requires to specify a Path and in this case  it is not possible to Compress / UnCompress a single file or to process a FileList.

Then my program code:

The WOF_Compress_x64.exe program has code to process a Path Or a single File Or a FileList and is in this respect more versatile.

In case of a selected File or FileList there is no Exclusion, it is just the List that is processed in this case.

In case of a selected Path then the [CompressionExclusionList] section of makebt\Compress_Exclude.ini file is default used, but it is possible to select other Exclusion file.

For a single selected file then the WOF Compression Status is given with the WOF = 0  or WOF = 1 Flag (handy to determine what has occurred)