<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Activity for mabac</title><link href="https://forge.codesys.com/u/mabac/activity/" rel="alternate"/><id>https://forge.codesys.com/u/mabac/activity/</id><updated>2024-10-30T16:00:35.962000Z</updated><subtitle>Recent activity for mabac</subtitle><entry><title>mabac posted a comment on discussion Engineering 🇬🇧</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/3a1cc4df9d/?limit=25#e2fa" rel="alternate"/><published>2024-10-30T16:00:35.962000Z</published><updated>2024-10-30T16:00:35.962000Z</updated><author><name>mabac</name><uri>https://forge.codesys.com/u/mabac/profile/</uri></author><id>https://forge.codesys.com/forge/talk/Engineering/thread/3a1cc4df9d/?limit=25#e2fa</id><summary type="html">CODESYS introduced many cyber security related changes over the last few years, one of them is to restrict file access. By default, file access is restricted to the PlcLogic folder and subfolders of the CODESYS control runtime of version 3.5.19.0 and newer. For Control Win this would be the folder C:\ProgramData\CODESYS\CODESYSControlWinV3x64\xxxxxxxx\PlcLogic\ To enable access to other folders, you can configure additional paths by adding them to the file CODESYSControl.cfg. For example: [SysFile]...</summary></entry><entry><title>mabac posted a comment on discussion Runtime 🇬🇧</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/39b44d4ae1/?limit=25#3413" rel="alternate"/><published>2023-11-30T21:46:00.507000Z</published><updated>2023-11-30T21:46:00.507000Z</updated><author><name>mabac</name><uri>https://forge.codesys.com/u/mabac/profile/</uri></author><id>https://forge.codesys.com/forge/talk/Runtime/thread/39b44d4ae1/?limit=25#3413</id><summary type="html">You may just need to create a boot application: https://content.helpme-codesys.com/en/CODESYS%20Development%20System/_cds_creating_a_boot_application.html</summary></entry></feed>