Rebuilt laptop rejects an argument in our read-only FR10 connection check before it contacts anything. Same script runs on the old laptop. Several SDK folders, no imported-copy record. What should I compare before I start changing a working call to suit the wrong environment?
Inspect the running interpreter, imported module path and method signature on both machines, using the ordinary launch route. I have raised this on another rebuild: a terminal check can differ from the shortcut the workshop actually uses. Preserve the old installation while you compare.
Normal-launch inspection shows different imported paths and signatures. The unchanged argument fits the old loaded interface, not the rebuilt one. I have saved the error and both environments' details; no controller settings changed.
Have the environment owner select a documented supported setup, then test local signature compatibility and the documented read-only response separately. Removing the argument error does not yet establish that the replacement screen interprets the reply correctly.
Put the selected launch details and test result in the rebuild handover once agreed. Otherwise the immediate repair can leave the next person with the same collection of folders and no reason to prefer one.