11-26-2019, 06:38 PM
That's to be expected, though it is a bit inconsistent. The manifest info (and the user input it generated) is stored as the driver configuration. It doesn't get reset just because you install a newer version. But the CML has to be seen since it's replaced what was there before. So it sees the code but not the manifest (if you pause/resume or restart both of which cause the driver to load the code again.) It's only when you do a reconfigure that the new manifest and old stored away info are merged and you are allowed to provide info for any new prompts and such (and possibly new fixed prompts behind the scenes.)
During upgrade that same process is done, since it kind of has to be, but any new prompts are just defaulted until such time as you reconfigure since that's the only way to enter that info.
So it's a bit messy, but that's the way it currently works. Normally, the only time drivers get upgraded is during a system upgrade. Any time I give someone a driver pack I tell them to install and reconfigure, which gets everything caught up. Most of the time the driver is running and would have to be reconfigured also just to see the new CML. But if you restart the driver or system, without a reconfig then the CML is seen but not the new manifest info.
During upgrade that same process is done, since it kind of has to be, but any new prompts are just defaulted until such time as you reconfigure since that's the only way to enter that info.
So it's a bit messy, but that's the way it currently works. Normally, the only time drivers get upgraded is during a system upgrade. Any time I give someone a driver pack I tell them to install and reconfigure, which gets everything caught up. Most of the time the driver is running and would have to be reconfigured also just to see the new CML. But if you restart the driver or system, without a reconfig then the CML is seen but not the new manifest info.
Dean Roddey
Explorans limites defectum
Explorans limites defectum