Check to tun post new galil driver install

## autosave check

locate autosave files in `c:\instrumemt\var\autosave\GALIL*` with the `settings` keyword in them from a date prior to the upgrade, then pass name to `asverify` command for each galil controller e.g.
```
C:\Instrument\Apps\EPICS>asverify C:\Instrument\Var\autosave\GALIL_02\GALIL_02_settings.sav_260731-182226
```
This will show PVs that differ in value before and after upgrade. All you should see is:
* ` HOMEVAL_SP ` no longer exists, but it should say its saved value was 0
* `_EDEL_SP` will have a different value, it is not autosave in the new driver but there is logic to pass its previous value to the new PV `_ENC_TOLERANCE_SP`
* If it says live values of `USWITCH_CMD` is 0 but saved value is 1 that is fine, we want 0 for this
* If `ONDELAY_SP` has chanegd from 0.000000 to 0.001000 fine as well
* if may talk about `FTRANSFORM`, `RTRANSFORM` changing from scalar/array – these are for MTRxx09 and above so can be ignored

Start by locating pre-upgrade files matching C:\Instrument\Var\autosave\GALIL* with the settings keyword, then run asverify for each Galil controller as shown. Compare the output against the listed expected differences and ignore the explicitly permitted changes. Done means no other unexpected PV value differences remain.

Written by the indexing model from the issue text.