Tested many different things yesterday, including the new -compressratio options and -minalign. -nbhashbits was tested with Windows 7 ISOs (less time-consuming), all other options were tested with the 19041.208 MVS ISOs. If you want to see the results, check the spoiler below. --- Spoiler: results Spoiler: system Code: Intel(R) Core(TM) i7-3632QM 8,0 GB DDR3 Samsung SSD 850 EVO 250GB Spoiler: files Code: f88082500b0bd7da628da447ca9b099a55cfe490 *de_windows_10_consumer_editions_version_2004_x64_dvd_7efdffc7.iso cd025a75fa9b7661fd0935de7c086c322f7527ea *en_windows_10_consumer_editions_version_2004_x64_dvd_8d28c5d7.iso 4e0450ac73ab6f9f755eb422990cd9c7a1f3509c *en_windows_7_enterprise_with_sp1_x86_dvd_u_677710.iso 65fce0f445d9bf7e78e43f17e441e08c63722657 *en_windows_7_ultimate_with_sp1_x86_dvd_u_677460.iso --- Spoiler: patch1.cmd Code: @echo off set "start=%time:~0,8%" smv.exe BuildPatch "patch_%*.svf" "en_windows_7_ultimate_with_sp1_x86_dvd_u_677460.iso" "en_windows_7_enterprise_with_sp1_x86_dvd_u_677710.iso" %* set "end=%time:~0,8%" echo Started at %start% and finished at %end%. Spoiler: -nbhashbits Code: Only the options completet faster than the reference are listed. Stopped at -nbhashbits 40, because there are no differences between -nbhashbits 31-40. patch1.cmd (reference, no parameters) ===================================== Time: 00:01:12 Hash: 64cd88968c12219ce5b9905f16c831639928c020 patch1.cmd -nbhashbits 20 ========================= Time: 00:01:12 Hash: 64cd88968c12219ce5b9905f16c831639928c020 patch1.cmd -nbhashbits 21 ========================= Time: 00:00:56 Hash: 64cd88968c12219ce5b9905f16c831639928c020 patch1.cmd -nbhashbits 22 ========================= Time: 00:00:47 Hash: 64cd88968c12219ce5b9905f16c831639928c020 patch1.cmd -nbhashbits 23 ========================= Time: 00:00:42 Hash: 64cd88968c12219ce5b9905f16c831639928c020 patch1.cmd -nbhashbits 24 ========================= Time: 00:00:42 Hash: 64cd88968c12219ce5b9905f16c831639928c020 patch1.cmd -nbhashbits 25 ========================= Time: 00:00:42 Hash: 64cd88968c12219ce5b9905f16c831639928c020 patch1.cmd -nbhashbits 26 ========================= Time: 00:00:42 Hash: 64cd88968c12219ce5b9905f16c831639928c020 patch1.cmd -nbhashbits 27 ========================= Time: 00:01:02 Hash: 64cd88968c12219ce5b9905f16c831639928c020 patch1.cmd -nbhashbits 28 ========================= Time: 00:01:02 Hash: 64cd88968c12219ce5b9905f16c831639928c020 patch1.cmd -nbhashbits 29 ========================= Time: 00:00:42 Hash: 64cd88968c12219ce5b9905f16c831639928c020 patch1.cmd -nbhashbits 30 ========================= Time: 00:00:42 Hash: 64cd88968c12219ce5b9905f16c831639928c020 patch1.cmd -nbhashbits 31 ========================= Time: 00:01:02 Hash: 64cd88968c12219ce5b9905f16c831639928c020 patch1.cmd -nbhashbits 32 ========================= Time: 00:01:12 Hash: 64cd88968c12219ce5b9905f16c831639928c020 patch1.cmd -nbhashbits 33 ========================= Time: 00:01:12 Hash: 64cd88968c12219ce5b9905f16c831639928c020 patch1.cmd -nbhashbits 34 ========================= Time: 00:01:12 Hash: 64cd88968c12219ce5b9905f16c831639928c020 patch1.cmd -nbhashbits 35 ========================= Time: 00:01:12 Hash: 64cd88968c12219ce5b9905f16c831639928c020 patch1.cmd -nbhashbits 36 ========================= Time: 00:01:12 Hash: 64cd88968c12219ce5b9905f16c831639928c020 patch1.cmd -nbhashbits 37 ========================= Time: 00:01:12 Hash: 64cd88968c12219ce5b9905f16c831639928c020 patch1.cmd -nbhashbits 38 ========================= Time: 00:01:12 Hash: 64cd88968c12219ce5b9905f16c831639928c020 patch1.cmd -nbhashbits 39 ========================= Time: 00:01:12 Hash: 64cd88968c12219ce5b9905f16c831639928c020 patch1.cmd -nbhashbits 40 ========================= Time: 00:01:12 Hash: 64cd88968c12219ce5b9905f16c831639928c020 Spoiler: patch2.cmd Code: @echo off set "start=%time:~0,8%" smv.exe BuildPatch "patch_%*.svf" "en_windows_10_consumer_editions_version_2004_x64_dvd_8d28c5d7.iso" "de_windows_10_consumer_editions_version_2004_x64_dvd_7efdffc7.iso" -nbhashbits 30 %* set "end=%time:~0,8%" echo Started at %start% and finished at %end%. Spoiler: -compressratio Code: Only the fastest option of a compress-engine is listed here. patch2.cmd (reference, -nbhashbits 30) ====================================== Time: 00:04:47 Size: 636 MB (666.937.108 Bytes) patch2.cmd -compressratio 9 =========================== Time: 00:04:47 Size: 636 MB (666.937.108 Bytes) patch2.cmd -compressratio 49 ============================ Time: 00:11:45 Size: 528 MB (554.553.788 Bytes) patch2.cmd -compressratio 59 ============================ Time: 00:11:47 Size: 528 MB (554.578.064 Bytes) patch2.cmd -compressratio 119 ============================= Time: 00:04:49 Size: 639 MB (670.201.260 Bytes) patch2.cmd -compressratio 192 ============================= Time: 00:09:11 Size: 490 MB (514.551.184 Bytes) patch2.cmd -compressratio 259 ============================= Time: 00:09:22 Size: 627 MB (657.638.904 Bytes) patch2.cmd -compressratio 332 ============================= Time: 00:04:36 Size: 650 MB (681.733.196 Bytes) patch2.cmd -compressratio 362 ============================= Time: 00:04:36 Size: 650 MB (681.733.196 Bytes) patch2.cmd -compressratio 392 ============================= Time: 00:04:36 Size: 650 MB (681.733.196 Bytes) patch2.cmd -compressratio 492 ============================= Time: 00:04:36 Size: 650 MB (681.733.196 Bytes) Spoiler: patch3.cmd Code: @echo off set "start=%time:~0,8%" smv.exe BuildPatch "patch_%*.svf" "en_windows_10_consumer_editions_version_2004_x64_dvd_8d28c5d7.iso" "de_windows_10_consumer_editions_version_2004_x64_dvd_7efdffc7.iso" -compressratio 192 -nbhashbits 30 %* set "end=%time:~0,8%" echo Started at %start% and finished at %end%. Spoiler: -blocksize Code: This option is useless for MVS ISOs / ISOs in general. patch3.cmd (reference, -compressratio 192 -nbhashbits 30) ========================================================= Time: 00:09:11 Size: 490 MB (514.551.184 Bytes) patch3.cmd -blocksize 8 ======================= Time: 00:09:43 Size: 491 MB (514.977.200 Bytes) patch3.cmd -blocksize 16 ======================== Time: 00:09:48 Size: 491 MB (514.977.200 Bytes) patch3.cmd -blocksize 32 ======================== Time: 00:09:53 Size: 491 MB (514.977.200 Bytes) patch3.cmd -blocksize 64 ======================== Time: 00:09:11 Size: 490 MB (514.551.184 Bytes) patch3.cmd -blocksize 128 ========================= Time: 00:08:49 Size: 490 MB (514.822.960 Bytes) patch3.cmd -blocksize 256 ========================= Time: 00:09:53 Size: 491 MB (515.272.156 Bytes) patch3.cmd -blocksize 512 ========================= Time: 00:11:14 Size: 492 MB (516.717.608 Bytes) patch3.cmd -blocksize 1024 ========================== Time: 00:14:32 Size: 495 MB (519.779.540 Bytes) patch3.cmd -blocksize 2048 ========================== Time: 00:22:37 Size: 502 MB (526.914.112 Bytes) patch3.cmd -blocksize 4096 ========================== Time: 00:39:15 Size: 516 MB (541.132.104 Bytes) patch3.cmd -blocksize 8192 ========================== Time: 00:39:09 Size: 516 MB (541.132.104 Bytes) Spoiler: -minalign Code: This option is useless for MVS ISOs / ISOs in general. patch3.cmd (reference, -compressratio 192 -nbhashbits 30) ========================================================= Time: 00:09:11 Size: 490 MB (514.551.184 Bytes) patch3.cmd -minalign 1 ====================== Time: 00:09:11 Size: 490 MB (514.551.184 Bytes) patch3.cmd -minalign 2 ====================== Time: 00:38:53 Size: 2,46 GB (2.646.351.320 Bytes) --- Spoiler: extract.cmd Code: @echo off set "start=%time:~0,8%" smv.exe x "patch_.svf" -br . %* set "end=%time:~0,8%" echo Started at %start% and finished at %end%. Spoiler: -bymerging Code: -inplace (-inplacenochecksum) not tested, because it changes the source file. extract.cmd (reference, no parameters) ====================================== Time: 00:00:11 extract.cmd -extractbystep ========================== Time: 00:00:11 extract.cmd -bymerging ====================== Time: 00:00:10 --- I'll suggest everyone to use these parameters: Code: Patching ======== Storage-saving but time-consuming: -compressratio 192 -nbhashbits 23/24/25/26/30 (preferred) Time-saving but storage-consuming: -conpressratio 332/362/392/492 -nbhashbits 23/24/25/26/30 Extracting ========== No real difference: -extractbystep, -bymerging -blocksize and -minalign might help patching virtual machine drives, not tested.
ask the author of zstd 1.4.5 (zstd 1.4.5 isn't software of G Vollant) smv only use zstd decompress compress (like zlib, and all other compression ) smv has his own intern file handling (VF system) wich handle files > 4GB if we start to discuss other software, this Thread run's out of topic
I downloaded smartversion 3.80 from their own website and i installed it but after installation it says the version is 3.75 on Help-About section am i missing something ?
It is not your fault, but the fault of the developer! file version is 3.80. About-window and test-period-window at program-start shows version 3.75!
I post my questions here as the first page of this thread "[DISCUSSION] Windows 10 1903/9 'FINAL' Build 18362/3.xxx (PC) [19H1/2 Release]" mentions the name "Smartversion". For the record, I did use the "Search" function of this website to look for where I can post my questions; however there is no post with the thread "Smartversion". My questions about Smartversion are: 1. For the version used on Windows OS, what registry entries are made when I install Smartversion? 2. For the version used on Linux, what additional software need to be installed? What entries are made to the operating system? Note to moderator: Please move this post of mine to the appropriate category.
1. SmartVersion stores the settings of the program in the registry. It also stores the information how to open .svf files. But that is only if you install it, you can use the command-line utility without installing SmartVersion, which doesn't store any configuration / other information. 2. I don't use Linux (except WSL), but I think it also stores the program settings in a configuration file. But as in Windows, that is only if you install it. And here's the thread for SmartVersion: https://forums.mydigitallife.net/threads/smartversion-tools-scripts.79415/
@luzea said that the command-line version of Smartversion does not require installation on Windows OS. See post #272 of this thread. However I was unable to find the command-line version for Windows OS on its official website. Am I missing something here?
Is that a joke for Bastille Day? It is so laughable. Did you know that the krack or registration details are all over the internet? Browse the Russian-language forums and you will see that the registration details for Smartversion are there for all the world to see. Do not confuse "registry entries" with "registration information/details". Read my post again. In my original post, I also asked what registry entries are made to the Linux version of Smartversion.
I was asking about what registry entries are made to Windows OS. I downloaded version 3.70 from Softpedia and ran the executable. Smartversion messed with my OS. Do not confuse registry entries with registration details. The latter are needed to register the software which, in this case, is Smartversion. I was not asking for registration details. As I have just replied to @Enthousiast, the registration details are all over Russian-language software forums.
Where? You wrote: "However I was unable to find the command-line version for Windows OS on its official website."