Quote:
Originally Posted by Photon
Skimmed, sorry if I misread sth. But filenames with spaces always require "", regardless of prepending Execute or not, and this is not a bug or sth unusual. If it shows the s attribute when you type List, the script should start just by typing its name. You can verify this by putting an echo "Running" as first line. If that shows and then it stops the error is thrown by some line in the script.
If the s attribute isn't showing, this could be from FAT formatted file system or sth?
|
The problem is that Execute command (as invoked indirectly by cli or WB) doesn't work with quotes - but works when invoked directly.
The following demonstrates this :
Code:
4.Ram Disk:> echo "echo toto" >"script with spaces"
4.Ram Disk:> protect "script with spaces" +s
4.Ram Disk:> execute "script with spaces"
toto
4.Ram Disk:> "script with spaces"
EXECUTE: Can't open script with spaces
object not found
4.Ram Disk:>
And same bad result when double-clicking the pseudo-icon from WB.