You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you run a program that's compiled with clib2, the program file remains locked and you can't rename or delete the program. The same program compiled with newlib does not keep the program file locked. If a program is running from WBStartup, you can't replace it with a newer version and reboot; you have to remove the program from WBStartup, reboot, replace the program with the new version, add it back to to WBStartup and then reboot. I don't see any reason to keep the program file locked once the program is started.
The text was updated successfully, but these errors were encountered:
When you run a program that's compiled with clib2, the program file remains locked and you can't rename or delete the program. The same program compiled with newlib does not keep the program file locked. If a program is running from WBStartup, you can't replace it with a newer version and reboot; you have to remove the program from WBStartup, reboot, replace the program with the new version, add it back to to WBStartup and then reboot. I don't see any reason to keep the program file locked once the program is started.
The text was updated successfully, but these errors were encountered: