Mounting WIM hides other installs and cannot select options until restart

ybfjax

New Member
1.8.0.7182 x64
win8.1x64 bit, 12gb ram, sata3 SSD, intel i5-3230M

edit: no antivirus running in background

I am trying to edit a win 10 LTSC install disk with integrated updates to August, 2019. I mounted the .iso and then copied the complete .iso files to a separate local folder (on ssd drive) so they could be edited with NTLite. But i notice some weird activity happening.

1) I would mount a particular OS from an esd (which would convert into .wim)

a) other OSs on the same esd would then become hidden.
b) the selected OS still did not mount correctly. I thought something was wrong (because online videos etc show numerous editing options on left-hand panel after mounting).
c) I would close and restart the program and then it would show the mounted image with options to edit. But the other OSs from the same esd/wim are still hidden.

In this screenshot, you can see the mounted image and the Image History are the same ISO structure, but you can see that the mounted image has the other OSs hidden.

ntlite mounting image bug.png

2) is there a manual "refresh" button that, if the program cannot refresh the mounting status, the user could click and refresh the program status? Closing and restarting is acceptable, but not ideal.

3) the mounting process uses a lot of cpu (seemingly 75-100% of available processes). Is there a way to limit the maximum processors NTLite uses?

4) Is there a video tutorial or user manual that shows the typical workflow and some use-cases? This is my first time using this program and it can seem a bit overwhelming to make sure I am using all of the features properly.
 
Last edited:
1) If you want to convert the ESD to WIM and keep all editions, select install.esd (not a single edition) and use Convert - WIM.
Then after it's converted, load an edition you want.
I should add a popup asking/warning a user about converting selected edition or all. Noted.
Not sure what you meant by not mounted correctly.

2) There is Refresh Lists above. You probably meant how to unselect an image. Use Source - Image - New Session

3) WIM mounting specifically uses a single core, it's a Windows API and no control over it.
While ESD conversion is using a number of cores (not threads/hyperv) for the number of processing threads.
Currently the setting is not exposed, no one requested it so far.
If your CPU doesn't have hyper-threading, it will take a lot. I'll reduce the thread count by one if that is the case.

4) Check the ntlite.com/support, also go through the Documentation there.

Thanks for the feedback.
 
1) If you want to convert the ESD to WIM and keep all editions, select install.esd (not a single edition) and use Convert - WIM.
Then after it's converted, load an edition you want.
I should add a popup asking/warning a user about converting selected edition or all. Noted.
Not sure what you meant by not mounted correctly.
After conversion is complete, the image (wim) is not mounted. is this a separate transaction? I thought that it should auto-mount once the conversion is complete. (I chose "mount" when clicking on the OS)
2) There is Refresh Lists above. You probably meant how to unselect an image. Use Source - Image - New Session

No I meant to refresh the sources or lists after a mounting or conversion operation is complete. But also a button that manualy refresh the gui screen based on current status.

I do not see a "refresh lists". Can you provide a screenshot please?

3) WIM mounting specifically uses a single core, it's a Windows API and no control over it.
While ESD conversion is using a number of cores (not threads/hyperv) for the number of processing threads.
Currently the setting is not exposed, no one requested it so far.
If your CPU doesn't have hyper-threading, it will take a lot. I'll reduce the thread count by one if that is the case.

It is the ESD conversion i think. But you should expose the core/thread maximum. You can suggest a default, but the user should be able to override this. Any software that will take up >= 33.3% of the processor power should give users the ability to cap CPU usage somehow. Because you cannot assume that you can just use up what's available. What if the user wants to do other things during the conversion?

4) Check the ntlite.com/support, also go through the Documentation there.

Thanks for the feedback.

The docs seem incomplete without use cases. You have any videos of 1 or more use-cases?
 
Back
Top