The directories with downloaded files are no longer a manageable collection because of the increase in size of hard drives. By now it is not clear what all those zips and exe's are doing and for what purpose they are downloaded.

Solution
Create a small text file that contains whatever the zip or exe contains or what the program does with how it should be installed. It can be handy to include the site from which you downloaded the file so you can examine whether there are any updates. Such text files are often found with the extension ".DIZ".

Working-out
You can start with F4 an editor in FC/2 by default. This editor will have the same position/dimensions as FC/2, ie the information about files and directories disappear from sight. And it is this information which is important because you have to copy parts of the content in order to obtain sufficient information to create that text file. The goal is to create a text file with the same name as the file with the extension ".DIZ". FC/2 allows to call an external program and can pass parameters to that program. Because this is not a one time operation it best to make the following macro; 
E: Create info about the tagged file
EDIT !x.DIZ
The translation from this short macro is as follows;
  • EDIT is the called text editor program.
  • The command "!x" translates into the name of the current file without its extension.
  • The new added extension.

Now I can open the menu with F2 in FC/2 and with the character "E" I can start this macro. If the "cursor" from FC/2 is on the file "idontknow.zip", then the macro will start with the file "idontknow.diz".

There is yet an other problem...
The program "AE.EXE" is installed in the \OS2 directory and the \ECS\BIN directory by default. Both programs are identical. Both programs use the same "AE.INI" that is created in the \OS2 directory. This file contains all settings of the programs including the window size and position. By calling one of the two programs there is a chance that the information in the FC/2 is hidden. If "AE.EXE" or "E.EXE" is launched in full screen, then it will start next time again in full screen. And this is not desirable. I want "AE.EXE" or "E.EXE" in a small window so there is plenty of room for the FC/2 screen. And switching every time makes you stark staring mad.

As a solution I have copied E.EXE to EDIT.EXE (with FC/2). That program does not exist in the OS2 directory, so it does not bite. With KON115 I opened EDIT.EXE (it MUST be done with a hex editor!) and searched for "AE.INI". Then I replaced it with "ED.INI". You have to do this twice (2x). After changing save the file.

Next time when I open the menu with F2 and call the command "E", EDIT is started and EDIT creates the file "ED.INI" with my desired settings. I can start "AE.EXE" or "E.EXE", no matter if it is in full screen or windowed mode, EDIT always starts in a window with my given measurements.

As proof a copy from FC/2 (adapted); 
ed.ini
EDIT.BAK
EDIT.EXE

398
362403
362403

28-07-05
13-06-04
28-07-05

13:02
0:58
12:58
The file EDIT.BAK is created with KON as a backup. Here an example with EDIT and the file "PENOS2.DIZ", while in the background FC/2 has the file "PENOS2.ZIP open and README.1st is viewed with the built-in editor. The first two sentences from the file "README.1st" are copied and pasted into the file "PENOS2.DIZ". Then the file data from FC/2 are copied and pasted. This action can not be performed with only FC/2.