Environment variables in command line on CDTV?

earok · 26 January 2024, 09:47

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.

alexh · 26 January 2024, 12:58

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

Don_Adan · 26 January 2024, 13:05

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.

Amigajay · 26 January 2024, 13:25

Can’t you use a direct line like?

sys:$mygame
$mygame

earok · 26 January 2024, 14:25

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

Thomas Richter · 28 January 2024, 05:55

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.

26 January 2024, 09:47	#1
earok Registered User Join Date: Dec 2013 Location: Auckland Posts: 3,542	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.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
FSUAE - Launch CDTV Rom from the command line?	zardoz	support.FS-UAE	1	22 March 2020 11:46
environment variables for kickstart 1.3	jotd	support.Other	2	13 January 2018 10:40
is there new command line ?	turrican3	support.WinUAE	1	15 April 2007 12:21
command line?	Drake1009	support.WinUAE	7	14 August 2004 17:17
Command Line.	ruttolibero	support.WinUAE	1	25 July 2003 15:05

26 January 2024, 12:58	#2
alexh Thalion Webshrine Join Date: Jan 2004 Location: Oxford Posts: 14,354	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

26 January 2024, 13:05	#3
Don_Adan Registered User Join Date: Jan 2008 Location: Warsaw/Poland Age: 55 Posts: 1,975	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.

26 January 2024, 13:25	#4
Amigajay Registered User Join Date: Jan 2010 Location: > Posts: 2,889	Can’t you use a direct line like? sys:$mygame $mygame

26 January 2024, 14:25	#5
earok Registered User Join Date: Dec 2013 Location: Auckland Posts: 3,542	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

28 January 2024, 05:55	#6
Thomas Richter Registered User Join Date: Jan 2019 Location: Germany Posts: 3,231	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.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)