Environment variables in command line on CDTV?
I've configured a startup sequence for a CDTV/CD32 project kind of like the following:
cd $mygame $mygame ($mygame is set from a kind of launcher menu earlier on the startup sequence) On CD32, it works fine. $mygame is interpreted as the value it's set to. But on CDTV $mygame is interpreted literally. I wasn't quite sure what needs to be set up on the CDTV for environment variables to be interpreted as such in the startup sequence. |
Is the file $mygame an executable or a script?
Is it something to do with it being a script with the "s" protection bit set? AmigaOS 1.3 doesn't have the "s" protection bit. In that case : Execute $mygame Should work for both |
If I remember correctly that "cd" is WB command for kick 1.3. Then You must copy "cd" from c dir from Workbench 1.3 disk.
|
Can’t you use a direct line like?
sys:$mygame $mygame |
I just saw it reported here that variables don't work on the command line in Kickstart 1.3, I'll try a different approach.
https://eab.abime.net/showthread.php?t=90197 |
Kick 1.3 does not have environment variables at all, as there is no environment. (ENV: does not exist). However, you can pass parameters into shell scripts that are parsed by the "Execute" command, and in this way you get some flexibility.
|
All times are GMT +2. The time now is 19:55. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.