V (release 3) What this is is a front end for commodore's More, or possibly for some other text-file-viewer program that can be made resident. I prefer More over other text viewing programs like MuchMore because it is small and quick and has every feature I really need. V's original purpose was to make More create its own window when run from the CLI, instead of using the CLI's window. Its more useful purpose nowadays is to avoid loading More or a similar program from disk when used from Workbench. This newest version also allows you to specify what window More will show the text in. To use V you should make More resident, with (naturally) the Resident command. If V cannot find More on the resident list, it will attempt to load C:More, and failing that, SYS:Utilities/More. V then opens a window, and runs More as part of its own process like the CLI would, passing to it the args given to V, translating any Workbench argument into command line form. The reason it runs More as a CLI process is that More's E command, which sends the file to the editor specified in the environment variable called EDITOR, is deactivated when More is a Workbench process. Thus if your Workbench icon specifies C:V as its default tool, or if you click on the V icon and shift-double-click the text file's icon, it will show the file with More (or some other program that you have named "More" on the resident list so that V can find it) without loading More from disk. It only has to load V, and V is only 1280 bytes long since I translated it into assembly. What I do personally is put copies of V in all sorts of places that various text icons expect to find viewers, such as SYS:Utilities/More, :C/Less, C:MuchMore, etc ... all just copies of V. Note that V itself can also be made resident, so that AmigaShell does not need to load either V or More from disk. You need not be using AmigaShell for V to work, though; its ability to use the resident copy of More is self-contained. V can also accept input from a pipe. There is one small bug in More. When you start it up with no argument, it asks you to enter a filename. After you do this and it shows the beginning of the file, it makes the E command available, but it doesn't work if you try it. If you press E it executes a command consisting of several sequential copies of the contents of ENV:EDITOR. V puts a message in the window under these conditions reminding you not to use the E command. V runs More as a CLI process even when V is a Workbench process, because More does not make the E command available when running under Workbench. Since More is being run from a CLI as far as it can tell, it will use a window provided for it instead of opening its own. You can tell V what window to open for More in ENV:MOREWINDOW. If none is specified, the default is "CON:0/0/640/200/More". You can tell it to use a larger window with, for instance, commands like setenv morewindow CON:0/0/640/256/More or echo > env:morewindow CON:0/0/640/400/More or if you have ConMan installed, you can take advantage of ConMan's special features, such as the ability to open a window on the topmost screen instead of the workbench screen (with "CON:S*/0/0/640/200/More" for instance -- note that if you put quotes around the con: specification in a setenv command, you have to use S**/ to mean S*/, otherwise the * is lost), or to open a window to fit whatever the size of the screen is ("CON:////More") or open a borderless window with no size gadget, so that you can read 80 columns of text ("CON:0/0/640/200/More/NS"). I used to use such a window myself, but now I have set my Workbench screen to be 664 pixels wide (and 220 tall), and 80 columns of text fit into a normal resizable window of that width. The window I now use is "CON:S*//1//215/ More ", which with ConMan creates a window on the frontmost screen as wide as will fit. I prefer to use More because of its simplicity and quickness, rather than fancier (larger, slower) programs like MuchMore. V is by Paul Kienitz and is in the public domain.