No. It doesn't work. But it will work if you use a comma instead of a colon. That is, /Font:"Arial:11" will not work but /Font:"Arial,11" will. Note that there must not be a space after the comma. ("Arial,11" will work, "Arial, 11" will not)

This syntax is incorrect. The font size needs to be specified outside of the quotes otherwise it is taken to be part of the font name. The correct syntax should be: VIEW *.txt /P /Font:"Arial",11 /LM:0.75 /Header:"%%e;%%f;Page %%p" However, this results in an error message.It seems there is a...

This problem has been fixed in 15.00.33

Thanks for sending me the files. There is a problem with how I identify UTF8 files. It will be fixed in a future update.

VIEW does not auto-detect code pages - it always use the system code page (by default). If you would like to use Windows 1252 (eg, to display line drawing characters), you will have to set it manually by left-clicking on "ANS" in the bottom right of the status bar and then selecting "Character...

VIEW will not run without a valid TC15 license. Can you run Take Command? What does the TC About box display? There should be a file called V.log in one of the following directories: C:\Users\UserName\AppData\Roaming\V or C:\Users\UserName\AppData\Local\V It will contain an error line if...

I assume you mean "view /h FILE" and "view /w FILE"? I can think of no reason why "view /h FILE" will work and "view FILE" will not work. Are you sure this is the case? Are you perhaps using "v FILE" instead of "view FILE"? This is expected. You cannot run v.exe as a standalone app. It...

The default method for cycling through files is by using Ctrl+PageDown/Ctrl+PageUp or by using the left/right arrow buttons on the toolbar.

I sent an email to the address I had on file for you. If you haven't received it, send me an email at v at fileviewer.com.

You are right - %f happens to work by good fortune and not by design. %f and %F should work as stated in the Help file. I will fix the bug in the next VIEW update. In a word, no. You should be able to implement this behavior as follows: 1. Enable View Next File in the Keyboard section...

In the Editor/CMD section of the VIEW Preferences, specify %f as the Editor Options. This should force VIEW to use the full path. Does this fix the problem?

If you can reproduce the problem, please replace your v.exe with the one below: ftp://ftp.fileviewer.com/jpsoft/v.exe After running VIEW (which should fail) send me the latest v.log

Can you still reproduce the problem as another user?

Not really, but can you please send V.log to "v at fileviewer.com"

In that case, is it possible that you had version 13 registered under a different user name?