03-25-2023 06:46 AM
I get some old seq, maybe coding with teststand 4, i try to run with teststand 2022:
1. asked me to save the old version, so newer version cannot run the old version directly ?
2. report some error as below, the dll is there, not sure why ?
Besides this, how to customize the GUI for production operator ?
Solved! Go to Solution.
03-25-2023 08:16 PM
See Migrating to the Current Version of TestStand to migrate from TestStand 4 to a later version.
See TestStand User Interface Development Best Practices to learn more about creating custom OI.
03-25-2023 10:44 PM
Sorry, my sequence file should be teststand 2014 or above, checked your link:
I am wondering, so need migrate them seperately, could not just migrate the seq file ?
03-26-2023 07:32 AM
I looked at the error information. The TestStand is throwing an error when trying to load a DLL. Most likely the DLL is compiled for 32-bit. Try to use TestStand 32-bit instead.
03-26-2023 07:36 AM
Okay, so normally the dll is compatible with different teststand version, but not for 32bit and 64bit both, right ?
Maybe that is the problem, thanks.
03-26-2023 08:05 AM - edited 03-26-2023 08:07 AM
A DLL can be compiled for 32-bit or 64-bit. An executable too. And Microsoft specifically and explicitly decided to not repeat the mistake when going from Windows 3.1 to Windows NT/95 and try to support a 16-bit to 32-bit thunking layer for user applications. They do have that internally (the SysWOW64 subsystem in which all 32-bit applications run on a 64-bit OS) but went to great lengths to make that subsystem completely inaccessible for user applications to avoid having programmers try to go around the clear cut that 32-bit software only can be executed in 32-bit applications and 64-bit only in a 64-bit application.
That 16-bit to 32-bit thunking layer back then was a total mess and absolutely unsupportable in the long run. You ended up having to write assembly code anyhow in most cases, so it was simply mostly useless.
03-26-2023 08:36 AM
Thanks for your info, Sir.