Antonino

looking forward to the fix, and Merry Xmas to all. I regret reboot.pro is down so I extend my wishes to all of u who are here and belong there too.

sorry about posting something a little off topic, but I am dying for an answer to the following: given the mac's ability to run windows for an os as well as the native mac, can one have rambooting, wimbooting, and what more and what not that we have normally done on the pc for years (ie, g4d menu, svbus loading, windows on vhd) from a mac machine?

well, I have just tried it and, ... what can I say, after some due personal adjustment, it works. the free-space gain is about a few hundred megs. I could not take full advantage of the shrinking, owing to my system's apparent need for systemapps, which forced me to place a ! in front of the string concerned. this may be due to the fact that it is a windows11, so I do not know if what I am saying applies to most other ppl's systems. those who know better, pls say anymore.

Attaboy!!! higher aims ahead!!! btw, have you modified any text files in the remove folder of this new edition? where do we get it from anyway? I do not see any link

so outside virtual or p2v scenarios, is one better off using ordinary vhd or is wimboot:wimcopy vhd any way faster?

1+ question for jfx, or anyone else, for that matter, to answer: what is the advantage of having the wimfile inside the vhd if one applies the wimboot:wimcopy way relative to plain wimboot mode (with wimfile outside, elsewhere)?

nossa! assim vc me mata! just kidding, huh

thank you ever so much for ur detailed reply, jfx. so, if i have understood correctly, winntsetup is already prepared to accept instructions from a file called MySoftware.txt if it finds it in the \Tools\MinWin\Default\Remove folder, right?

so will those files be removed from across the whole volume, regardless of where they are found? my second question was related to a group of system32 and syswow64 root files that I have to keep in order to let my favorite software still work after the miniwin deletions. so I was thinking of as many instances of !\windows\system32\filename.dll and !\windows\syswow64\filename.dll as my files to keep to be appended to system32-dll.txt and syswow.dll respectively. but just in case I place these strings elsewhere, in some other scripts, will they be effective, viz, will the files be kept where they are even if the instructions are not in the proper textfile? do u mean environment variables make the operation handier and more viable?

excuse me, I would like to know how to signal my intention to get rid of a certain filetype wherever it is found on the os disk/vhd, of course by a script string of this kind: \*.kyk\* or \*.scr\* are they correct? oh before I forget, is there any such thing as custom_command.txt, like in win_reduce_trusted, where one can place any string he/she sees fit? if there isn't one, can I append strings to any list I find, or do I have to use a specific script for them to be effective? tx in advance.