Hey there, sorry didn't get back to you as planned, I am about to recreate the steps now, will let you know if I was successful in recreating the issue that you have.
Seems you did not read the post from the thread composer clearly or in its entirety, or you glazed over it too fast? The author explained that there were registry entries that were missing. The zip file he had up was removed. The cab files for altering NVI settings work together with the rest of the ADC provisioning files. The cabs alter more hw level settings while the provisioning xml files can build out the registry settings and other aspects of the OS as needed. It is likely there was a goal in mind that took too much time, because all the settings files (NV, xml, prov cabs, modem cabs, everything...) need to all be in tune the same way based on the hardware capabilities. It is tedious to go through all the files and know them line by line just takes time unless one were to build a program to analyze it all easily . I wish I could have spent many more days or hours on this as it was a real learning experience, but it was too time consuming....Hey, you mentioned an attached zip file in the first post, but there's no zip attached? Is there another place I can grab it?
Hmm, it was very late at night when I stumbled across this post. I will admit I just read the entire first post and then skimmed all the replies afterwards.Seems you did not read the post from the thread composer clearly or in its entirety, or you glazed over it too fast? The author explained that there were registry entries that were missing. The zip file he had up was removed. The cab files for altering NVI settings work together with the rest of the ADC provisioning files. The cabs alter more hw level settings while the provisioning xml files can build out the registry settings and other aspects of the OS as needed. It is likely there was a goal in mind that took too much time, because all the settings files (NV, xml, prov cabs, modem cabs, everything...) need to all be in tune the same way based on the hardware capabilities. It is tedious to go through all the files and know them line by line just takes time unless one were to build a program to analyze it all easily . I wish I could have spent many more days or hours on this as it was a real learning experience, but it was too time consuming....
It's OK. A file and method still exist if you're interested just follow up and read...Hmm, it was very late at night when I stumbled across this post. I will admit I just read the entire first post and then skimmed all the replies afterwards.
Hmm, it was very late at night when I stumbled across this post. I will admit I just read the entire first post and then skimmed all the replies afterwards.Seems you did not read the post from the thread composer clearly or in its entirety, or you glazed over it too fast? The author explained that there were registry entries that were missing. The zip file he had up was removed. The cab files for altering NVI settings work together with the rest of the ADC provisioning files. The cabs alter more hw level settings while the provisioning xml files can build out the registry settings and other aspects of the OS as needed. It is likely there was a goal in mind that took too much time, because all the settings files (NV, xml, prov cabs, modem cabs, everything...) need to all be in tune the same way based on the hardware capabilities. It is tedious to go through all the files and know them line by line just takes time unless one were to build a program to analyze it all easily . I wish I could have spent many more days or hours on this as it was a real learning experience, but it was too time consuming....