The old laptop runs our read-only FR10 check. The rebuilt one rejects an argument before connecting, using the same script. I found several SDK folders and a shortcut whose working directory nobody recorded. I'd rather identify the imported copy than reinstall everything and lose the clue.
Our rebuilt FR10 laptop loads a mystery SDK folder
Harriet_Blair · 2025年12月5日 20:14 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
5 条回复
Have the script report its interpreter path and imported module path from the normal shortcut on each laptop. Keep the exact argument error beside the failing configuration. Does the working copy have a recorded version or dependency list?
14分No dependency list. The shortcut imports a local SDK copy from the script directory. On the old laptop that local copy is a different version.
11分Ask the software maintainer to identify the intended supported version and compare the call against its documentation. Finding the different copy explains a useful difference, but it does not decide which version your handover should preserve.
17分The maintainer has the script and both imported paths. She is checking the original deployment notes before choosing the environment. The rebuilt laptop still fails; no claim that locating the folder fixed it.
6分Include the agreed launcher settings and dependency versions in the eventual rebuild instructions, then verify through that normal shortcut. The next person should not have to repeat the directory investigation.
10分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .