Persistence (or a template) for Compatibility Setting on Live Runs?

[pmikep]

I think I've asked for this feature before. If not, asking again.

I find myself using NTLite Live all the time on my Win10 box.

Every time I start it, the Compatibility settings seem to default to a default. (I think.) And I keep forgetting to change it, since it's kind of "out of sight, out of mind." (Like, I had to check VBox a few times.)

Is there a way that NTLite could have persistence across Live runs for Compatibility? Perhaps either Compatibility templates or placeholders that are tied to OS and NIC, for example? That is, so that I don't have to change Compatibility every time I run live on my Win10 box.

I could, as a work around, make a Template Preset that has the Compatibility settings that I want and always start a new Preset using the template. But then I would forget to save the new Preset with SaveAs. So if NTLite offered a template, perhaps it could be ReadOnly to force me to save a Preset built on it using SaveAs.

 

[Kasual]

You can add (edit) to settings.xml the component's name to keep, example:

    <LockComponents>
        <c>azuread</c>
        <c>driver_bthpan.inf</c>
        <c>font_msgothic</c>
        <c>hwsupport_printer</c>
        <c>hwsupport_scanner</c>
        <c>searchshell</c>
        <c>shellhwdetection</c>
        <c>wpdbusenum</c>
    </LockComponents>

This will work every time you start NTLite.

 

[pmikep]

Cool. That's for locking components. I wonder if I can copy the
<CompoentFeatures> to settings.xml to lock them in? (I'll try it.)

 

[pmikep]

I tried it. It doesn't work.

But perhaps nuhi can make the settings.xml so it does work with this trick? (It's not intuitive. But is better than nothing.)