UHC Tools

[npagonis73]

Originally Posted by jayminer

There is a small CLI utility within UHCTools called AskMore that maybe could be used for what you are thinking of. You would have to make some scripts that could take a string using AskMore and then search for it, and another script that would take a number using AskMore for download/extraction.

I'm not sure how well this would work but I do believe it could be done without too much hassle.

Perfect. I will try AskMore and experiment.

Thank you all guys for the immediate help

[npagonis73]

Just to update everyone on the situation. I wrote 7-8 scripts using AskMore and also requestfile or requeststring which all work perfect. They work as buttons on docks or menu items in ToolsDaemon. The scripts are made for Aminetsearch, Aminetextract, Aminetget, Aminetrecent and unpack. I also wrote scripts to combine Aminetsearch or Aminetrecent with Aminetget or Aminetextract. So with one script you search Aminet for you file and then just fill in the number and it downloads it and extracts in in ram straight away. Very fast and very convenient.

Thanks a lot for pointing me to the right direction.

Now i will try the GUI to see what else we can do

Perfect set of tools !!! Well done

[npagonis73]

Hello again

Wrote a few scripts like the attached photo which work perfect. What would I add at the end of this script in order to loop back when reaching the end so I can download more files? I tried the LAB & SKIP commands but don't work as they do in other scripts.

Thanks in advance

[patrik]

You need to add the BACK argument to skip if you want it to search backwards for labels.

Btw, if AskMore is in your path, you do not need to supply the complete path to it for each line.

[npagonis73]

Originally Posted by patrik

You need to add the BACK argument to skip if you want it to search backwards for labels.

Btw, if AskMore is in your path, you do not need to supply the complete path to it for each line.

Would it be

"LAB LOOP" without quotes at the second line

And at the end

"SKIP LOOP BACK" ?

Wouldn't that put the script in an endless loop? It would be better with a question and Yes or No. If yes then loop, if no end cli. What would you suggest for that?

[patrik]

You could treat an empty answer as that the user wants to exit and make it skip to a label at the end in that case.

Lab loop
AskMore “number: “
If ”$ANSWER” EQ ””
    Skip end
EndIf
aminetextract $ANSWER
Skip loop BACK
Lab end

[npagonis73]

Thanks a lot Patrik. Will try that!!!

[npagonis73]

Hello there

Could you please have a look at this error on 3.1 Amiga OS? UHC tools work fine in all other OS such as 3.2.1, 3.1.4 and 3.9 but in 3.1 i get this error and none of the scripts work

[patrik]

As a general remark on this issue, UHC Tools has no compatibility issue with 3.1 which we are aware of, it was actually developed mainly under 3.1.

Which command are you executing when this happens?

Can you create files and write to them in T:? Does the following work:

echo test >T:testfile

Also, can you execute other scripts - would for example the following work:

echo version >ram:testscript
execute ram:testscript

[npagonis73]

Patrik thanks for your reply. Will test your suggestions later tonight to see if I can write anything in t:

Just for your information, i can't run any of the UHC scripts in the S folder coming with the installation. Even uchupdate doesn't work and i get the same error in all of them. I installed uhc the same way i did in all my other OS. So most probably there is something wrong with my 3.1 installation and folder t: which seems in use by something!!

Will come back to you later tonight when i try what you said

[npagonis73]

Is the file in t: command-00-t002 a file used by UHC?

[patrik]

It is temporary files created by execute. Not 100% sure when they are created, but I think it is when a script calls another script.

[patrik]

Now I know - execute creates those when scripts with arguments are used. It creates a temporary script with the argument(s) resolved/expanded and I am positive that the temporary file is what is actually executed.

Look at this example:

9.Ram Disk:> type argscript 
.KEY SOMEARG
echo "<SOMEARG>"
wait 10
echo "done!"
9.Ram Disk:> run execute argscript testing 
[CLI 1]
9.Ram Disk:> testing

9.Ram Disk:> list t: 
Directory "t:" on Söndag 06-Mar-22
Command-0-T1                     37 ----rwed Idag      00:35:26
1 file - 37 bytes - 2 blocks used
9.Ram Disk:> type t:Command-0-T1  
 
echo "testing"
wait 10
echo "done!"
9.Ram Disk:> done!

9.Ram Disk:> list t: 
Directory "t:" is empty

Also, as you can see, it removes the temporary file in T: after it is done.

[npagonis73]

Hello again Patrik

Thanks a lot for looking into it. As you can see in snoopdos log, it fails to write on this file even though it has written and read the 2 first times. That is strange!!

Any ideas on how to solve that?

[npagonis73]

Hi there again

Found the issue!!!

I replaced the very old execute command from 3.1 with execute from 3.1.4 and it all works fine now.

Patrik thanks a lot for helping me solve this issue. You pointed me to the right direction!!!

Good night

[jayminer]

It's great that you got this solved, but this sounds strange because just like Patrik said - 3.1 is what we have used for most of the development of UHCTools and definitely should work. Do you still have the old Execute command and can do a version on it using "Version FILE C:Execute.old" or where the file is right now.

Maybe your Execute command had been replaced with an even older version or something at some point?

[npagonis73]

Hello jayminer

I will try to find the version I replaced. I checked the version on the old execute before i replaced it and it was from back in 1991 (don't remember the version number). Do you want me to send it to you?

[npagonis73]

Originally Posted by jayminer

Maybe your Execute command had been replaced with an even older version or something at some point?

I am sure that this is what happened.

[patrik]

The 3.1 execute is "execute 37.11 (1991-05-14)".

Is your T: non-standard in any way, or is it the normal RAM:T?

[npagonis73]

Originally Posted by patrik

The 3.1 execute is "execute 37.11 (1991-05-14)".

Is your T: non-standard in any way, or is it the normal RAM:T?

Yes that was the version of the old execute file i had.

My RAM:T folder is a standard one. It is normal 3.1 installation with Better WB, internet, whdload etc.