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
kOS doesn't let you change the bootfilename to a path or even the string for a path it only seems to accept the string of a file name and will only run the file if it is found on the root volume of the core.
If a file is not in the root directory i couldn't find a way to set the bootfilename to that location and have the targeted file run
File called "my_example1.ks" found at path: "1:/other_boot_files/my_example1.ks"
SET CORE:BOOTFILENAME TO PATH("1:/other_boot_files/my_example.ks"). //will crash
SET CORE:BOOTFILENAME TO "1:/other_boot_files/my_example.ks". //will not run my_example.ks when rebooted
But if the file is found at 1:/ then you can set BOOTFILENAME to that file so long as you only use the name of the file
File called "my_example2.ks" found at path: "1:/my_example2.ks"
SET CORE:BOOTFILENAME TO "1:/my_example2.ks".//will not run my_example2 when rebooted
SET CORE:BOOTFILENAME TO "my_example2.ks".//will run my_example2 when reboot
This seems at odds with the rest of the way we are suppose to handle files now. if it needs to be kept that way for backwards compatibility then it would be nice to have another version of bootfilename that could be set to paths or strings that describe paths
The text was updated successfully, but these errors were encountered:
kOS doesn't let you change the bootfilename to a path or even the string for a path it only seems to accept the string of a file name and will only run the file if it is found on the root volume of the core.
If a file is not in the root directory i couldn't find a way to set the bootfilename to that location and have the targeted file run
File called "my_example1.ks" found at path: "1:/other_boot_files/my_example1.ks"
But if the file is found at 1:/ then you can set BOOTFILENAME to that file so long as you only use the name of the file
File called "my_example2.ks" found at path: "1:/my_example2.ks"
This seems at odds with the rest of the way we are suppose to handle files now. if it needs to be kept that way for backwards compatibility then it would be nice to have another version of bootfilename that could be set to paths or strings that describe paths
The text was updated successfully, but these errors were encountered: