TM> The executable extension doesn't NEED to know about
  > any %1 parameters!  It's the associated program (together
  > with 4Dos.com) that will deal with the parameters!

 But the program may be picky about the *placement* of those
 parameters.  Consider this test extension:

 set .zaq=d:\bag\xx34e.com 40 150

 The program wants commands in a certain format:

 Usage: XX34E [d:path]filename [columns] [rows] [ADn]

 So this command works:               d:\bag\xx34e.com d:\incs.zaq 40 150

 But what the ExecExt produces is:    d:\bag\xx34e.com 40 150 d:\incs.zaq

 And XX34E can't handle the switches coming first, even though
 most programs want them there.  The '%1' bits try to handle the
 positioning.  But they don't work, either.

 set .zaq=d:\bag\xx34e.com %1 40 150
        produces                        .ZAQ=d:\bag\xx34e.com  40 150

 set .zaq=d:\bag\xx34e.com %%1 40 150
        produces                        .ZAQ=d:\bag\xx34e.com %1 40 150

 The latter looks good in the environment, and using "%%0" looks
 better.  But neither actually turns out to work.  An executable
 extension works fine for programs that like their switches up
 front.  If they like them at the end, it doesn't work.

TM> Then build an alias like this: alias pret=pret.exe %{at}name[%1]
  > and an exec.extension like   : .pas=pret
  > One way or another it should be able to work ;-)

 But it doesn't:

D:\>alias qax=d:\bag\xx34e.com %{at}name[%1] 40 50 ^ set .zaq=qax

D:\>eset .zaq qax
.ZAQ=qax
qax=d:\bag\xx34e.com %{at}name[%1] 40 50

D:\>incs.zaq

        XX34E 0.2B(c)1992 Greg Vigneault
        Box 7169,Stn.A,Toronto,Canada M5W1X8

        ?Error: Filename

 All variations of %1, %%1, %0, %%0, and %name and %%name fail.
 Did you actually try any of your suggestions?

... A wise skepticism is the first attribute of of a good critic.
--- SR 2.00 #1019  -!-  Lowell