There are many big tech companies, which are definitively the enemy of the people, that are hell-bent, on literally killing and controlling people and Microsoft is one of them through their founder Bill Gates. We really want to get to a point where we can tell Microsoft to go to hell.
The removal of MFC will be finished before June 2021 and then we can begin to adapt Sierra Chart directly to Linux or perhaps we may just utilize WINE and get involved in working out the bugs that exist by fixing that code. Removal of MFC simplifies the interface Sierra Chart has to the operating system which means there are less functions used so there is less potential for problem.
#Xquartz and wine compile for windows on mac code
Actually we probably should just go ahead and get that done now.Īnd then there is some exotic COM functions related to creating desktop shortcuts to Sierra Chart.Īnd we are moving in a direction of removing Microsoft code from the program most predominantly MFC and making sure all of the code does not contain anything Microsoft compiler specific. The only thing exotic relates to some code with the connection to CTS which we want to remove. There is a firm rule that we do not use anything other than the standard and most basic operating system functions. Or possibly using a particular operating system function that we have not used before but that is not something which would be common and actually the trend is using less operating system functions. We think the problems that have occurred in the past, would be related to us using a new version of Visual C++ that causes some unexpected issue that where the cause is unknown to us. There would never be anything deliberately from Sierra Chart to cause a problem with using Sierra Chart with operating systems other than Windows. We want you to enable Message Log logging in Sierra Chart:Īnd then run Sierra Chart again and then provide us the log file at the time you run into the problem.Īpple, Crossover, or SC upgrades anything that breaks the setup
Unhandled exception: page fault on read access to 0x00000020 in 64-bit code (0x0000000140f4a0e2).
0 kommentar(er)
