blog Discussion
williamfrench
blog
(Discussion)
Forum for blog comments
Last updated: 2022-01-25
Home
williamfrench
wiki
(WikiPage)
This is the personal project of williamfrench. This project is created automatically during user registration as an easy place to store personal data that doesn't need its own project such as cloned repositories.
Last updated: 2022-01-25
wiki Discussion
williamfrench
wiki
(Discussion)
Forum for wiki comments
Last updated: 2022-01-25
(no subject)
williamfrench
wiki
(Thread)
Last updated: 2022-01-25
Home
goghie
wiki
(WikiPage)
This is the personal project of goghie. This project is created automatically during user registration as an easy place to store personal data that doesn't need its own project such as cloned repositories.
Last updated: 2022-01-25
wiki Discussion
goghie
wiki
(Discussion)
Forum for wiki comments
Last updated: 2022-01-25
blog Discussion
goghie
blog
(Discussion)
Forum for blog comments
Last updated: 2022-01-25
(no subject)
goghie
wiki
(Thread)
Last updated: 2022-01-25
Home
draygoon
wiki
(WikiPage)
This is the personal project of draygoon. This project is created automatically during user registration as an easy place to store personal data that doesn't need its own project such as cloned repositories.
Last updated: 2022-01-26
wiki Discussion
draygoon
wiki
(Discussion)
Forum for wiki comments
Last updated: 2022-01-26
blog Discussion
draygoon
blog
(Discussion)
Forum for blog comments
Last updated: 2022-01-26
(no subject)
draygoon
wiki
(Thread)
Last updated: 2022-01-26
wiki Discussion
gurke258
wiki
(Discussion)
Forum for wiki comments
Last updated: 2022-01-26
blog Discussion
gurke258
blog
(Discussion)
Forum for blog comments
Last updated: 2022-01-26
Home
gurke258
wiki
(WikiPage)
This is the personal project of gurke258. This project is created automatically during user registration as an easy place to store personal data that doesn't need its own project such as cloned repositories.
Last updated: 2022-01-26
(no subject)
gurke258
wiki
(Thread)
Last updated: 2022-01-26
Home
edizerevren
wiki
(WikiPage)
This is the personal project of edizerevren. This project is created automatically during user registration as an easy place to store personal data that doesn't need its own project such as cloned repositories.
Last updated: 2022-01-26
wiki Discussion
edizerevren
wiki
(Discussion)
Forum for wiki comments
Last updated: 2022-01-26
blog Discussion
edizerevren
blog
(Discussion)
Forum for blog comments
Last updated: 2022-01-26
(no subject)
edizerevren
wiki
(Thread)
Last updated: 2022-01-26
wiki Discussion
tobiasduester
wiki
(Discussion)
Forum for wiki comments
Last updated: 2022-01-26
blog Discussion
tobiasduester
blog
(Discussion)
Forum for blog comments
Last updated: 2022-01-26
(no subject)
tobiasduester
wiki
(Thread)
Last updated: 2022-01-26
Home
tobiasduester
wiki
(WikiPage)
This is the personal project of tobiasduester. This project is created automatically during user registration as an easy place to store personal data that doesn't need its own project such as cloned repositories.
Last updated: 2022-01-26
Ticket #7: Potential issue with codesys using updated vcrun files from MS download
CODESYS 4 Linux
tickets
(Ticket)
I installed Codesys on wine onto a clean Debian 10 and Debian 11 environments using the manual install method on Deb 10 and Deb 11, and the install2.sh on Deb 11. In all cases I was able to launch Codesys IDE start and compile project, deploy/start runtime to both localhost or network connected device, but simply could not establish a login session from IDE to runtime to perform download, etc.. After some research on winetricks github I discovered the previous 1 or 2 winetricks releases modified SHA256 hash for some of the VCRUN files due to MS releasing updates even to old VCRUN versions. I modified the winetricks shell to force it to use VCRUN files I manually extracted from Codesys install packages, and the runtime connection problem is solved. Unfortunately I did not keep records of the install environments, logs, etc.., however I am hoping this basic information may prove useful to someone else who may experience the same problem. There may be a more graceful solution, but further troubleshooting was beyond my current capacity. I tricked winetricks by: extracted older vcrun and dotnet files from a Codesys install zip package, moved into manually created folders (matching the expectations of winetricks) in the .Cache folder of my user's wine prefix folder. (I don't think dotnet changed, but did them also to be on the safe side) Using a text editor, comment out all of the command lines downloading fresh copies of vcrun's and dotnet's from MS. 2022-01-27 01:57:41.445000 Ticket #7: Potential issue with codesys using updated vcrun files from MS download CODESYS 4 Linux codesys-4-linux tickets tickets False /tol/codesys-4-linux/tickets/7/ Ticket Potential issue with codesys using updated vcrun files from MS download False 1 2022-01-27 01:57:41.332000 7 Potential issue with codesys using updated vcrun files from MS download open I installed Codesys on wine onto a clean Debian 10 and Debian 11 environments using the manual install method on Deb 10 and Deb 11, and the install2.sh on Deb 11. In all cases I was able to launch Codesys IDE start and compile project, deploy/start runtime to both localhost or network connected device, but simply could not establish a login session from IDE to runtime to perform download, etc.. After some research on winetricks github I discovered the previous 1 or 2 winetricks releases modified SHA256 hash for some of the VCRUN files due to MS releasing updates even to old VCRUN versions. I modified the winetricks shell to force it to use VCRUN files I manually extracted from Codesys install packages, and the runtime connection problem is solved. Unfortunately I did not keep records of the install environments, logs, etc.., however I am hoping this basic information may prove useful to someone else who may experience the same problem. There may be a more graceful solution, but further troubleshooting was beyond my current capacity. I tricked winetricks by: extracted older vcrun and dotnet files from a Codesys install zip package, moved into manually created folders (matching the expectations of winetricks) in the .Cache folder of my user's wine prefix folder. (I don't think dotnet changed, but did them also to be on the safe side) Using a text editor, comment out all of the command lines downloading fresh copies of vcrun's and dotnet's from MS. False False 0 0 0 None 1.0 oims24 None
Last updated: 2022-01-27