Either I found a bug in NTLite v. 1.8.0.7261 or I don't understand what importing a HW list is supposed to do. Here's what happened:
I was using NTLite to do some removals on one Win8.1 machine. I had exported a Preset and a HW list from that machine that I wanted to use on another Win8.1 machine.
I had purposely created a Preset where no drivers had been removed. (Only removals of other items.) When I ran NTLite on the second Win8.1 machine, I imported the previous HW list from the first machine, and enabled it in the Compatibility List. To my surprise, when I inspected the resulting autosaved Preset that resulted, it now had about 15 drivers added into it! (I found this via WinMerge. The only two things that changed in the Preset where the addition drivers and an extra line in Compatibility showing the new imported HW list.
I was under the impression that the purpose of the HW list was to prevent removals of drivers. Not to remove them.
I was using NTLite to do some removals on one Win8.1 machine. I had exported a Preset and a HW list from that machine that I wanted to use on another Win8.1 machine.
I had purposely created a Preset where no drivers had been removed. (Only removals of other items.) When I ran NTLite on the second Win8.1 machine, I imported the previous HW list from the first machine, and enabled it in the Compatibility List. To my surprise, when I inspected the resulting autosaved Preset that resulted, it now had about 15 drivers added into it! (I found this via WinMerge. The only two things that changed in the Preset where the addition drivers and an extra line in Compatibility showing the new imported HW list.
I was under the impression that the purpose of the HW list was to prevent removals of drivers. Not to remove them.