so, shall I run it all back again and give u the lists, or nothing has changed in the technicality of the software?
#151
Posted 23 July 2020 - 10:06 AM
#152
Posted 23 July 2020 - 10:38 AM
so, shall I run it all back again and give u the lists, or nothing has changed in the technicality of the software?
No need to run again. All given info by you is sufficient and OK
Technically only h_path.cmd has been added that can be used in cmd window with any path as parameter.
But at the moment I think best and easiest is to use Hard_Link_List_x64.exe
that you can run just by double-click and select any path to get the desired File List and info on Hard Links.
#153
Posted 23 July 2020 - 10:53 AM
to me, running it on volume I:\ is fine, so u have everything already and I can keep the older version, if nothing substantial has been added to the functionality and efficiency of the software.
btw, the used space sizes I gave u yesterday for the combo vhd's refer to their never being booted yet (fresh from the wimboot applying); whe u run them, used space doubles up, so multiply by 2, if u need operating figures. Needless to say, if they had been run in ram for the first time, they woulda started from the original afterbaking sizes.
oh, before I forget, together with the cleaning software I mentioned in earlier posts, particular importance must be given to device remover, which I used to get rid of services I saw I did not use. not only does device remover remove the services in themselves (which might as well be obtained by sc delete --- from the command promt), but it also removes all the files and folders connected to them. of course, it is better to save a copy of the vhd beforehand, as what is removed by device remover is lost forever. another piece of software which has been vital to me is tweaking.com's windows repair (I already mentioned it) as it performs an overall checkup of the vhd and readjusts the permissions that might have been spoiled as a result of all the junctioning. it is better to run it in safe mode. at the end of the process, regbackup can be moved someplace else for space retrieval on the vhd. do u want a list of my services to analyze the lists any better?
#154
Posted 23 July 2020 - 01:06 PM
@antonino61
Thanks for the extra info.
A list of your services is certainly interesting for building a comparable installation.
The issue in h_path.cmd is solved, so everything in Dir_List is now working OK.
Download: Dir_List.zip contains program Hard_Link_List_x64.exe
More Info: http://reboot.pro/to...f-out/?p=215442
#155
Posted 23 July 2020 - 01:24 PM
so, do u want new dirlists from me or are those u already have ok? as for services, do u want a snapshot of the window or will u give me a command prompt instruction to obtain a text file?
#156
Posted 23 July 2020 - 01:52 PM
No need to make new Dir_Lists, they are OK for me.
In my System_Info program there is a button Drivers+Services that will launch ServiWin
Use ServiWin in your running minimal Win10x64 OS.
In ServiWin you can select with Icon to have list of Drivers Or Services.
For Drivers and for Services use Viiew > HTML Report All Items
Put the result e.g. in folder Drivers_Services and zip the folder and post it like mine given here ...
Drivers_Services.zip 57.06KB 2 downloads
#157
Posted 23 July 2020 - 02:21 PM
so easy, I had serviwin already, so, here are the lists:
Attached Files
#158
Posted 23 July 2020 - 02:48 PM
Thanks a lot for your reports on drivers and services.
It will certainly be helpful in achieving a minimal Win10x64 Installation
#159
Posted 23 July 2020 - 03:54 PM
waiting for your learned opinions.
#160
Posted 23 July 2020 - 11:52 PM
Dear wimb, just a little due self-correction, the amount of used space in the combo vhd does not depend on the status (filedisk or ramdisk) of the full vhd u have booted off, but on whether u have run it as filedisk or not. so, wrong assumption on my part in another post.
#161
Posted 24 July 2020 - 08:52 AM
On my way to Mini Win10x64 in 25 GB VHD using WinNTSetup and and VHD_WIMBOOT (V_W) .....
Here are the first steps taken - Disconnect Internet and After WinNTSetup Disable Windows Update for 35 days
#162
Posted 24 July 2020 - 11:03 AM
#163
Posted 24 July 2020 - 12:07 PM
Good for the time being. It would be a good idea to try shrinking the full vhdi any further with lzx.bat offline.
OK, where do I find lzx.bat ? Can it reduce the Used Size for booting as FILEDISK ?
Will continue tomorrow morning.
#164
Posted 24 July 2020 - 12:09 PM
#165
Posted 24 July 2020 - 09:41 PM
ok, I eventually came home. the command prompt string I was referring to is the folllowing:
compact /c /s /a /i /exe:lzx "i:\*"
if u have gotten hold of a better one, pls let me know.
#166
Posted 25 July 2020 - 06:04 AM
ok, I eventually came home. the command prompt string I was referring to is the folllowing:
compact /c /s /a /i /exe:lzx "i:\*"
OK, I have done that. For Full Win10x64 in VHD the Used Size is now 3.9 GB
compact.exe /c /s /a /i /exe:lzx "P:\*"
#167
Posted 25 July 2020 - 09:03 AM
If you want a Compact mode LZX, doing your final VHD and latter apply Compact LZX to it is foolish, if you can install it directly as Compact mode LZX, using wimlib, you can optionally use base_winsxs.cmd from cdob, but don't forget to fully defragment it with Defraggler to consolidate free space.
Next is a summary of my procedure:
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.
Use WinNTSetup and this WIM file to create first VHD standard mode, NO Pagefile, NO AV, optionally NO additional drivers (to increase portability), install required programs (if portables better), and SVBus driver (required for RAMboot only), here you can optionally use base_winsxs.cmd from cdob, and recapture it (with VHD_WIMBOOT or directly with wimlib) as Wimboot WIM file LZX compression, new Wimboot WIM can be used for fileboot (installed with or without using Compact mode), or RAMboot, after testing Rambooting your Wimboot VHD, optionally you can compress it as gzip using 7-zip but it is a very slow process, better use LZ4 Compressor. grub4dos 0.46a can use both compressions.
You can use VHD_WIMBOOT and UEFI_MULTI on some of previous steps, but if you want to directly install the VHD on Compact mode LZX better do it with wimlib directly, don't use WinNTSetup, wimlib does this more efficiently. If you prefer a GUI for wimlib use wimlib-clc, and remember there is a new version (1.13.2) of wimlib here.
alacran
- wimb likes this
#168
Posted 25 July 2020 - 09:42 AM
If you want a Compact mode LZX, doing your final VHD and latter apply Compact LZX to it is foolish, if you can install it directly as Compact mode LZX, using wimlib, you can optionally use base_winsxs.cmd from cdob, but don't forget to fully defragment it with Defraggler to consolidate free space.
Next is a summary of my procedure:
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.
Use WinNTSetup and this WIM file to create first VHD standard mode, NO Pagefile, NO AV, optionally NO additional drivers (to increase portability), install required programs (if portables better), and SVBus driver (required for RAMboot only), here you can optionally use base_winsxs.cmd from cdob, and recapture it (with VHD_WIMBOOT or directly with wimlib) as Wimboot WIM file LZX compression, new Wimboot WIM can be used for fileboot (installed with or without using Compact mode), or RAMboot, after testing Rambooting your Wimboot VHD, optionally you can compress it using gzip using 7-zip but it is a very slow process, better use LZ4 Compressor. grub4dos 0.46a can use both compressions.
You can use VHD_WIMBOOT and UEFI_MULTI on some of previous steps, but if you want to directly install the VHD on Compact mode LZX better do it with wimlib directly, don't use WinNTSetup, wimlib does this more efficiently. If you prefer a GUI for wimlib use wimlib-clc, and remember there is a new version (1.13.2) of wimlib here.
Thanks a lot for giving detailed description of your appoach to get Mini Win10x64.
Good idea to use first MSMG Toolkit and to use wimlib for the second Install in Compact mode LZX instead of WinNTSetup.
#169
Posted 25 July 2020 - 09:58 AM
Thanks a lot for giving detailed description of your appoach to get Mini Win10x64.
Good idea to use first MSMG Toolkit and to use wimlib for the second Install in Compact mode LZX instead of WinNTSetup.
You are Wellcome, my friend, we all are here to share and learn new ideas.
WinNTSetup first installs all, and latter Compacts it (standard Dism procedure), the advantage of using wimlib for Compact mode installs is it first compacts the files on RAM and then write them to the VHD, this lets you use an smaller size for the target VHD, that WinNTSetup can't use, I have had this trouble with WinNTSetup during my tests.
alacran
- wimb likes this
#170
Posted 25 July 2020 - 10:02 AM
my aim is not portability or usb install. My aim is to have the smallest possible on disk, whether in ram or as filedisk. lzx is to be used regularly on filedisk full vhds, as any file that the system hits will lose its "compactness". of course, if u use your vhds as ramdisks, the problem is no more. but we are still on a previous stage, so full vhd as filedisk. mstoolkit is a powerful program, but it can do very little when u have already stripped everything u could, so u will hit a stage where what u want out is hardcoded and u won't be able to delete it without hopelessly rupturing the wim for install. we still believe, and there is reason to believe so, that, at the end of the day, when all is said and done, there is still system software that the system will not need in normal routine use. I have found so many directories in program files, program files (x86) and programdata that could easlly deleted or junctioned out to ram without any hindrance to normal routine operation. and that was the stage we were at. the point now is which subfolders in the windows dir can be deleted or junctioned out to ram with no hindrance to normal routine operation.
lz4 is good. but .gz word size 8 option completes faster and smaller and works better here.
#171
Posted 25 July 2020 - 10:15 AM
WinNTSetup first installs all, and latter Compacts it (standard Dism procedure), the advantage of using wimlib for Compact mode installs is it first compacts the files on RAM and then write them to the VHD, this lets you use an smaller size for the target VHD, that WinNTSetup can't use, I have had this trouble with WinNTSetup during my tests.
Interesting these didifferences for WinNTSetup as compared to wimlib for case of Compact mode Install.
@antonino
For me it is a learning stage in general on how to reduce the Used Size of Windows 10x64.
It is to early to draw conclusions, I just try all kind of procedures and can experience how it all works and what remains of value to me.
#172
Posted 25 July 2020 - 10:20 AM
A comment about Win10 Compact mode installs, if using Compact 4K (Win10 native mode), all new files added to the drive after the install, will be 4K compacted automatically by the OS.
EDIT: Only valid for files under OS Directory, when running Compact /compactos:always, directly on the running OS.
But if using Compact 8K, 16K or LZX all new files added to the drive after the install, will be written at is full size, without any compression (user added files, temp files. etc), then in this case it is good to use CCleaner to reduce garbich, and WOF_Compress from wimb on user documents and user installed programs folders periodically.
alacran
Edited by alacran, 18 August 2020 - 07:43 AM.
- antonino61 likes this
#173
Posted 25 July 2020 - 10:29 AM
lzx with the command prompt string I gave above compacts better and smaller offline than wof-compress, which is better than lzx online but compresses less. in terms of used space size.
#174
Posted 25 July 2020 - 10:30 AM
anyway, here is what performance test yielded on all my vhd booting modes concerning the install wimb and I have been testing on.
Attached Files
#175
Posted 25 July 2020 - 10:34 AM
lzx with the command prompt string I gave above compacts better and smaller offline than wof-compress, which is better than lzx online but compresses less. in terms of used space size.
If you use wimlib during Compact LZX install, you get an even better compression.
alacran
4 user(s) are reading this topic
0 members, 4 guests, 0 anonymous users