Our FR10 identity script runs on the old laptop but rejects an argument on the rebuilt one before connecting, and I have three SDK folders with no note saying which one the working shortcut uses.
Replying to NaomiBrown0941
Start the script the usual way on each laptop and check the interpreter path and imported module location. Folder names will not settle this. Compare the callable signatures too, using the read-only script; do not start rewriting its arguments until you know which copy it imports.
11 points