Mickatroid wrote: ↑Tue Mar 14, 2023 5:54 pm
Could be the space, <execute> is just grabbing the bit before the space. Quotes around the whole script file name might have fixed it too.
In case you refer to my startup-sequence.
The new name for the WB1.3 s-s is conceptually required.
My WB1.3 is on the first partition that also has the highest boot priority. As such, it will always execute the file „startup-sequence“ from the WB1.3-partition in S:
Now, if you then want to execute the s-s you need for actual WB1.3, you already have one file named Startup-sequence. Hence you need a new one.