Home >> Support Board

Support Board

Date/Time: Tue, 26 Nov 2024 17:36:20 +0000

How to Post a Message for Support

SC on windows ARM/VM on apple max studio

View Count: 948

[2023-06-16 12:59:29] #1 [Go To First Post]
User525733 - Posts: 126
Hi, the issue below is stopping me from using SC: I am moving to a new compute environment : windows ARM on VM running on apple Mac studio. when i moved my custom ACSIL studies that were compiled on a win64 machine ( retiring soon) to the new environment (windows on VM/Apple)...i got the errors below: (relevant sections of the log) Found DLL: User-contributedStudies_64.dll 12023-06-15 UserContributedStudies_64.dII loading error. Windows error code 193: %I is not a valid Win32 application. \| 2023 06 15 and Triggering next historical data download in queue. 2023 06-15 WI 5: 13533 No download requests in the queue to start downloads for. \| 2023 06 15 Socket (3) Socket gracefully closed by remote side. \| 2023 06 15 W 15:13.678 Socket Closed. 06 15 Found DLL: 2023 06 15 WI 5:31.726 Found DLL: UserContributedStudies_64.dII 2023 06 15 WI 5:31.726 loading error. Windows error code 193: %I is not a valid Win32 application. 12023 06-15 WI 5:31753 InternalVersionNumberToFiIeNameMap is empty for 2023 06-15 WI 5:31753 Closest match search for: returned empty result. 2023 06-15 WI 5:31753 UserContributedStudies_64.dII loading error. Windows error code 193: %I is not a valid Win32 application. 2023 06-15 WI 5:31779 InternalVersionNumberToFiIeNameMap is empty for UserContributedStudies 2023 06 15 WI 5:31.77g Closest match search for: returned empty result. 2023 06-15 5:31779 Found DLL: 2023 06 15 Found DLL: UserContributedStudies_64.dII 2023-06 15 nogi_custom_studies.dll loading error. Windows error code 193: %I is InternalVersionNumberToFiIeNameMap IS empty for 2023 06 15 Closest match search for: returned empty result. 2023 06-15 WI 7:08.996 UserContributedStudies_64.dII loading error. Windows error code 193: %I is not a valid Win32 application. 2023 06-15 InternalVersionNumberToFiIeNameMap is empty for UserContributedStudies 2023 06 15 WI 7:08.998 Closest match search for: returned empty result. 2023 06-15 seems there is an issue with the SC dll that loads custom dlls. please advise thx

[2023-06-20 13:28:01] #2 [Go To First Post]
Sierra_Chart Engineering - Posts: 17182
Custom studies that you want to use with the ARM64 version of Sierra Chart have to be built for ARM 64. This would require using Visual C++ to build them. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2023-06-20 13:28:06

[2023-08-29 20:53:48] #3 [Go To First Post]
fabse - Posts: 10
I built my custom strategy for arm64 see this post please Sierra Chart Executables for ARM 64 Processor but I get an error when the strategy is loaded. See the link.

[2023-08-29 21:22:59] #4 [Go To First Post]
John - SC Support - Posts: 36300
The particular error you are getting states that it is not a Win 32 application. Is the VM you are running a 32 bit VM? Sierra Chart is only built for 64 bit architectures. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing

[2023-08-29 22:26:28] #5 [Go To First Post]
fabse - Posts: 10
The problem I was referring to in the other thread is the following: I have build my own custom studies with arm64 by changing the VisualCCompile.bat script and run it on my own like this inside a win ARM VM on parallels on a mac. So it is all ARM arch: call "C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvarsall.bat" arm64 cl /JMC /MP /analyze- /Zc:wchar_t /Z7 /Od /GS /W3 /RTC1 /Zc:inline /D "_WINDOWS" /D "_USRDLL" /D "_WINDLL" /Gd /Gy /GR- /GF /fp:precise /MTd /std:c++17 /LD /EHa /WX- /diagnostics:classic /nologo "C:\SierraChartARM\ACS_Source\FabsesStudies.cpp" /link "Gdi32.lib" "User32.lib" /DLL /DYNAMICBASE /DEBUG /INCREMENTAL:NO /OPT:REF /MACHINE:ARM64 /OUT:"C:\SierraChartARM\Data\FabsesStudies_ARM64.dll" it seems to build everything correctly for arm but when I load the custom strategy arm64 dll I get this weird error: "The custom study xxxx required version 2499 or higher of sierra chart. Current version 2499." Any ideas on how to fix this?

[2023-08-30 09:38:05] #6 [Go To First Post]
Sierra_Chart Engineering - Posts: 17182
Does not make any sense to us. But make sure you are using an up-to-date SierraChart.h header file which is located in the /ACS_Source folder. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2023-10-14 20:21:14

[2023-10-14 16:17:17] #7 [Go To First Post]
fabse - Posts: 10
I found the issue. I downloaded the latest version today. If I open the 64 bit version (SierraChart_64.exe) it says, version: 2555 If I open the ARM version (SierraChart_ARM.exe) it says, version: 2543 In the sierrachart.h file this is defined: // SC_DLL_VERSION gets updated only when there have been changes to the DLL // study interface. This should be set to the Sierra Chart version number // that includes the changes made to the interface. #define SC_DLL_VERSION 2551 If I change this to: // SC_DLL_VERSION gets updated only when there have been changes to the DLL // study interface. This should be set to the Sierra Chart version number // that includes the changes made to the interface. #define SC_DLL_VERSION 2543 and compile with the bat file mentioned above I can load my custom studies in the ARM version. So I think the fix from your side might be to also release the ARM version as version 2555?

[2023-10-14 20:22:25] #8 [Go To First Post]
Sierra_Chart Engineering - Posts: 17182
We have put out a new ARM version. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing

[2023-11-19 13:59:42] #9 [Go To First Post]
autobahn - Posts: 25
Similar issue with version 2564 - but 2562 works. Is there an easy way to tell which versions have matching headers before downloading? Date Time Of Last Edit: 2023-11-19 16:46:57

[2023-11-19 20:16:41] #10 [Go To First Post]
Sierra_Chart Engineering - Posts: 17182
We will generate a new ARM version now. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing

To post a message in this thread, you need to log in with your Sierra Chart account: