Hello, Hai;
I'm sad you did not succeed... Too bad!
Let's take some steps, now. First, would you let us know exactly what did you store in CST variable? I mean, the exact contents of the list.
Now, if you follow me, please... I know it 'sounds' silly, but if you do what I ask you to, you should have the BEEP command assigned to the leftmost softkey. I have my HP48SX in hands right now and I'd like you to do this, please:
1 - create the list
{ BEEP }
and send it to stack level 1 with [ENTER] key. Keep the upper-case letters!
2 - place the following in the command line:
'CST'
and send it to the stack (press [ENTER]). You should see:
___________________
|4: |
|3: |
|2: { BEEP }|
|1: 'CST'|
|XX XX XX XX XX XX|
3 - Now press [STO] and then press [CST].
Now you must see the small [BEEP] in the first softkey, right? Enter the following data:
440
1
When executing BEEP, the object in stack level 2 will be taken as frequency (440Hz) and the object in stack level 1 will be taken as duration (1 second). Press the softkey, now. If after all of this you still have a string "BEEP" in stack level 1, then there is something very weird going on here... I mean, there, with your HP48SX. There is no way to have such a 'BEEP' in stack level 1 because BEEP is the name of an internal command, and it can not be taken as a name, I mean, there is no way to store an object with the name BEEP. Hence, the only two ways to have BEEP in the stack are as a string or as an unquoted command, and the only way I know hwo to do this is by putting the list { BEEP } in stack level 1 and executing [LIST->]. If BEEP is assigned to a softkey with CST, it will always try to generate a sound.
Or else I need to read Bill Wickes' HP48 Insights again... Well. this is not bad at all, it's always a good reading.
Let us know what happens, Hai.
Success!
Luiz (Brazil)
Edited: 2 June 2005, 4:48 a.m.