WinNTSetup v5.4.1

[dimo70]

Most of errors in ENGLISH version fixed - soon we will make final stable version.

 

[Antonino]

wow, this must be brilliant!!!

[dimo70]

One more update - fixed some errors and added new functionality

 

[dimo70]

Here there is video help working with the NTHelper

 

[Antonino]

how do we get nthelper?

 

[dimo70]

2 hours ago, Antonino said:

how do we get nthelper?

 

Here, but not final version at this time.

[Antonino]

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

[Antonino]

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.

Edited August 5, 2023 by Antonino

[Antonino]

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.

Edited August 5, 2023 by Antonino

[dimo70]

Hi, if you have problems, or any suggestions please write exactly what is your problem.

[Antonino]

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?

 

[dimo70]

I never use VHD. VHD compressed to wim in а minute. Use WinPE Xemom1 and no worry.

[Antonino]

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

[Antonino]

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

 

[click-click]

I just did a test using Wimlib and Wimgapi to apply an image and was surprised that Wimlib took 5 minutes longer to finish than Wimgapi. I thought Wimlib was the better choice. Any idea why it's slower?

 

Edited August 15, 2023 by click-click