Antonino

i have not yet figured out what it is for but it does open ok

this one does open ok

i did extract it ok it is the exe that does not execute

it does not execute here because I have my temp in z:(ramdisk) can u adjust nthelper to my situation or shall I move my temp dir anyplace else?

probably a stupid question, but I wll ask it anyway: can an already minwinned vhd be minwinned again and reboot ok?

i can confirm jfx is correct!!! so we'll have to take good care to have the box unchecked beforehand if we want no indexing, btw, I have a feeling that only my old captured wims work properly; I have never succeeded to make a dvd out of what I have just recaptured. I do not know what the resason might be; it never was so with any previous version. there must be something wrong with my capturing (and recapturing, for that matter). whoops, sorry - I tried once again and ... no issue this time. so I guess it all depended on my postmodified vhds

thanks a lot., this is what I need too, so how do I get it now that it is no longer automatic? can we re-automate it or automate it in any other way?

btw, I have just found out that the indexing box is ticked, unlike somebody said in earlier posts, if I understood correctly

thank u ever so much jfx. Everything works here, but I am not so significant a tester, as I have always run ur winntsetup from powerrunx64.exe. so no issues so far. the only think that did not work at the outset was wimmization with winlib, which I righted immediately by switching to w**api or something like that (the alternative provided, I mean).

I personally back up mine on a regular basis, the only difference being, mine are not so huge. they tend to be about 2gigs.

that is that is exactly what I meant at the outset - is there any point in differencing at all? talking of less than 2gigs?

Is it really worth the trouble?

formatting with nthelper like greased lightning!!!! excellent!!! then what? winntsetup?

I can get the wim ok, out of any vhd, thru winntsetup

for the time being, I am testing its diagnostics, which seems accurate - right clicking on the drive and getting the data concerning it in a command box. the problem to which I alluded was not due to any fault whatsoever of nthelper.exe, but to the reduction (miniwinning) of any vhd which does not take into account the dlls that any executable requires in order to run properly. what one normally does in such cases is get the specific executable running on an unminiwinned vhd and run process explorer to check which dlls it needs in order to run properly and get a txt listing all of them. then each string on the list (c:\windows\syswow64\blablabla.dll in the case of nthelper.exe) will be turned into something like copy c:\windows\syswow64\blablabla.dll d:\nthelperdlls and so on till the end of the list, which will be saved as *cmd or *.bat Once the dlls have been gathered, one runs the miniwinned vhd and copies all dlls in nthelperdlls to syswow64 and ur software that did not work before will work ok now. now do u want a specific problem that I might have at the moment which nthelper could contribute to solving? well, of all the vhds I have only one runs ok as ramdisk, and I do not know why this one does and the other ones do not. they crash with BSOD and the error signaled does not enable me to tell what has gone wrong. as filedisks all of them vhds run ok. as ramdisks, all of them load into ram, but only one of them completes the booting process to the desktop interface. any idea why?

well now it does run on any vhd, even miniwinned, it was some syswow64 dll or other. in a bit for the findings. i do not know how to connect it with winntsetup though, but I will tell u what it does in and of itself that can be useful, at least from my point of view.

pls bear with me, I had to exit a miniwinned vhd because it would not run there and enter an unminiwinned vhd, where it of course does run, now I want to check with process explorer for the dlls it need to run on any miniwinned vhd, and then I will tell u what I have found.

thank u ever so much! I would like to try and contribute with my feedback, however meager it may be.

how do we get nthelper?

wow, this must be brilliant!!!

yes, pls, do repair that asap

thanks jfx, I already knew the junction trick and I extensively use it. I was wondering if the above folders could be made special folders as anywhere-locatable as, say, documents, pictures, sendto, startmenu, so as to move them wherever one pleased. between u and me and anyone concerned, it would be wonderful to treat any folder like that if the stuff in it is not involved in the booting to the extent that the system demands that it be in c:\ . don't forget that my participation in the reduction of windows by wimboot and winntsetup started from my provocative assumption whereby windows is whatever must reside on c:\ in order for the os to boot and reach the interface + whatever else, which should preferably reside anywhere other than c:\ ; the more portables we have instead of installable software, the neater and simpler the system. my vhd's are the same over months or years, they dont get clogged with installed stuff - whatever was once the prerogative of the mac and linux is now possible with windows as well thanks to a few of u. that is why i insist that miniwin is not a curiosity, but some more efficient form of os to be seriously taken into consideration even if ur hardware can fit more stuff for an os - that saved space could be used for more substantial stuff than a bloated os.

interesting point, jfx, may I take it as a hint? well I will try to explain to u what I would like to do. I would like to tell winntsetup to write C:\Windows\Microsoft.NET to d:\Microsoft.NET, c:\windows\assembly to d:\assembly, c:\windows\system32\driverstore to d:\driverstore. can it be done? if yes, how to?

Well, not much of a difference then; how many do u have to bake per day?

.@dimo70 The Great Bulgarian I hope ur findings are correct, 20x is like greased lightning! What I initially meant eas that minwin contains txt files that will be processed by the tool if they are meaningful (containing paths to existent files and/or folders), no matter what their files are called (even pamelo.txt is pricessed). In the dism hatch, instead, whatever u specify is processed, so whether it is pamelo, or sample or mangiacaprini, if it is there and u specify it, it will be processed. So, minwin both and Dism either or