Is there a WB command at all that can...

[TCD]

I think you mean '.key name' then use '<name>' to access it. 'name' is obviously just a placeholder Use the comma to have more than one param.
Oh and place that in the first line of your script.

[MethodGit]

Actually, if it helps explain things easier, I want the "list" command to be able to create a script that goes something like this:

WWARP T:Temp.wwp C Import="(game name).ipf" Force
WWARP T:Temp.wwp G * "(game name).adf"
delete T:Temp.wwp

This exact series of commands, added as per every IPF found in the current folder. I think it has a problem with the * in the second line though as it doesn't show up in the finished script.


EDIT: Eh? What you referring to exactly, CD?

[TCD]

Your question about the equivalent of the %1 parameter in AmigaOS

[MethodGit]

Ah okay. You might have to give me an example of how it works since Google is still being crap with coming up with good answers.

[TCD]

.key Name

echo <Name>

So, enough spoonfeeding now

[MethodGit]

Thanks. But looking at it I still don't see how this will solve my situation. I take it the Execute command won't recognise anything entered after the name of the script? Or can anything referenced in .key be carried over to as many recursive scripts as possible?

[TCD]

Originally Posted by MethodGit

But looking at it I still don't see how this will solve my situation. I take it the Execute command won't recognise anything entered after the name of the script?

Er... of course it will recognise the parameter. Otherwise it would be pretty pointless. Looking at the thread, I think that thomas gave you pretty much what you need here (you'll have to adapt it of course).
Btw : Not sure if AmigaOS supports recursive scripts.

[MethodGit]

Actually, Google finally helped me with something!

Turns out to make List/LFormat output a script with more than one command you need to use "*n" to refer to a line feed.

But alas, I am still stuck because it is unable to understand the * in the second WWarp command, and that symbol is required by the program. So it looks as if I may have to implement the long-winded two-script way after all. Unless of course there is a way around the * confusion?

Still, I'd like to know how exactly the ".key" can be called at a command prompt in the same manner as a %1 if I'm to make references inside the script.

[TCD]

Meh.

Make a script with contents of my example 5 posts above. Name it 'test'. Call it with 'execute test MethodGit'. See what it does.

[cosmicfrog]

time to get a book on amiga dos hehehehehhe

[rare_j]

Try amigados for beginners on aminet (adosbegin.lha) it explains everything you ask and more very well.

[MethodGit]

Originally Posted by TheCyberDruid

Meh.

Make a script with contents of my example 5 posts above. Name it 'test'. Call it with 'execute test MethodGit'. See what it does.

Impressive.

[MethodGit]

Originally Posted by TheCyberDruid

Btw : Not sure if AmigaOS supports recursive scripts.

Gash....... think you may be right on that one.

Here's my current script:

list >tempscript files p=#?.ipf lformat="execute IPF2ADF *"%n*""

This creates a tempscript in the same directory, and that tempscript will read something like this:

execute IPF2ADF "Secret of Monkey Island, The (Europe) (v1.2) (Disk 1).ipf"
execute IPF2ADF "Pushover (Europe) (En,Fr,De,Es) (Disk 2).ipf"
execute IPF2ADF "Pushover (Europe) (En,Fr,De,Es) (Disk 1).ipf"
execute IPF2ADF "Pushover (Europe) (En,Fr,De,Es ) (Alt) (Disk 2).ipf"
execute IPF2ADF "Pushover (Europe) (En,Fr,De,Es ) (Alt) (Disk 1).ipf"

(For some reason "list" doesn't output the names in alphabetical order but oh well)

That IPF2ADF script in turn executes this:

.key <name>

WWarp T:Temp.wwp C Import="<name>" Force
WWarp T:Temp.wwp G * "<name>.adf"
Delete T:Temp.wwp

However, what I'm getting in return is this:

creating new wwarp file "T:Temp.wwp" from file "" using trackwarp.library
cannot open file: object is not of required type
T:Temp.wwp: object not found (dos.library/open file to read)
disk image '.adf' has been written, size=0
No file to delete

AmigaDOS, why hast thou forsaken me?!

[TCD]

Fingers crossed you got the idea now
Edit : Not '.key <name>', just '.key name'...

[prowler]

Originally Posted by MethodGit

(For some reason "list" doesn't output the names in alphabetical order but oh well)

AmigaDOS, why hast thou forsaken me?!

FYI, List outputs the names in the order in which the file header/user directory blocks appear on the disk.

[MethodGit]

Originally Posted by prowler

FYI, List outputs the names in the order in which the file header/user directory blocks appear on the disk.

Even though I'm using a PC directory here? How weird.

I'm starting to worry that this .key thingy will only acknowledge output referred to in the initial execute command, and not any inside scripts. Amirite? >.<

[TCD]

Originally Posted by TheCyberDruid

Edit : Not '.key <name>', just '.key name'...

Clear enough now?

creating new wwarp file "T:Temp.wwp" from file "" using trackwarp.library

You see the "" in the message? That means it has no file to create 'Temp.wwp' from. That's why the second wwarp command in that script fails.

[cosmicfrog]

thats why there is a sort cmd, guess wot it sorts a txt file

http://www.bombjack.org/commodore/amiga-books.htm

Compute's AmigaDOS Reference Guide 4th Edition

had this for years

[prowler]

Originally Posted by MethodGit

Even though I'm using a PC directory here? How weird.

If you're using a PC directory, then the names are (I would guess) listed in the order in which they appear in the PC directory TOC.

[MethodGit]

Originally Posted by TheCyberDruid

Clear enough now?

I saw it the first time!

You see the "" in the message? That means it has no file to create 'Temp.wwp' from. That's why the second wwarp command in that script fails.

No shit! I know it can't seem to find the file, which was what led me to ponder whether .key expects me to reference it in my initial execute command. Which would defeat the whole purpose of doing a multi-convert batch file.