During the past few days I've gotten some new (to me) error message using NTLite. (1.8.0.7070.) I'm not very good at keeping my Journal while I 'Lite. So I doubt that I can recount all the steps that caused these messages. Mostly the point of this post is to query whether differently worded messages would tell the user more.
So, for example, while doing something with Win8.1, I got this message about "handles."
Is a "handle" a "name," like in CB-Radio slang?
Then I got this message.
I don't understand what an "offline servicing failure" is. Is there such a thing as an "online servicng failure"?
Then when I started to work on a Win7 image, I got this message:
When I saw the word "store," I immediately thought of the Store in Win8.1. But since this was Win7, I knew the message couldn't be referring to the Windows' Store.
I am guessing that it has something to do with the Components in my Win7 iso.
Last, I got another message after this about "handles" again.
I don't have a clue what this is telling me.
BTW, these last two error messages threw Windows and NTLite into a deep hole. I had to jump through a lot of hoops to get NTLite working again. And, IIRC, I saw NTLite do an automatic cleanup of some directories.
So kudos to nuhi for making NTLite more robust. I remember that it was a year or two ago that we were gettting into some strange states with NTFS links, where it was nearly impossible to delete the Mount Directory.
So, for example, while doing something with Win8.1, I got this message about "handles."
Is a "handle" a "name," like in CB-Radio slang?
Then I got this message.
I don't understand what an "offline servicing failure" is. Is there such a thing as an "online servicng failure"?
Then when I started to work on a Win7 image, I got this message:
When I saw the word "store," I immediately thought of the Store in Win8.1. But since this was Win7, I knew the message couldn't be referring to the Windows' Store.
I am guessing that it has something to do with the Components in my Win7 iso.
Last, I got another message after this about "handles" again.
I don't have a clue what this is telling me.
BTW, these last two error messages threw Windows and NTLite into a deep hole. I had to jump through a lot of hoops to get NTLite working again. And, IIRC, I saw NTLite do an automatic cleanup of some directories.
So kudos to nuhi for making NTLite more robust. I remember that it was a year or two ago that we were gettting into some strange states with NTFS links, where it was nearly impossible to delete the Mount Directory.