FileViewer.com

Hi, is there a way to save a certain window layout (hex, ebcdic etc..), so that at after closing V, the next open of a file would display in the same way?

update: I found a manual (i'm investigating V 1.3 for my compagnie, and it downloaded without a manual), and found out that certain start options (commandline options), can do what I want. I will have to open files (wich ar in EBCDIC format) with the options vertical hex, (flat)text mode and ebcdic mode. Only the ebcdic mode doesn't seem to function. I use the "/B " commandline option, but it will always open in ASCII mode.
So I start with "X:\V\v.exe /b /vh /r /flat /text. But the /b seems useless. Am I overlooking something?

regards

I use the "/B " commandline option, but it will always open in ASCII mode.
i'm investigating V 1.3 for my compagnie, and it downloaded without a manual

Are you sure you are using Version 1.3? 1.3 is over 15 years old and the problem you describe is probably an old bug.

I would download the latest version (V14) from the web site and try again. The /B option should work.

Okee, thanks for your answer. I downloaded and installed the 64bits version SR1.
It still isn't able to start in EBCDIC mode. What we are doing is that we need to keep more then 100.000 files "alive", at the moment we will get rid of our mainframe. The data is frozen, we only use it as a static info. The data has a variable contents, so simply transfering the EBCDIC data to a ASCII platform is not an option because there are packed information fields in the data, but not at a fixed position.
So.. I try the V fileviewer and it looks oke, it does what I should expect and what I want. Because we don't want our end-users, who will be using the product, to have to change too many configuration options, I start V with the following options: v.exe /b /vh /r /flat /text. Perhaps there is an inconsistancy?

One other thing that I am curious of is : is it possible to edit the EBCDIC-ASCII table so that "unprintables" wil not display as a small square, but as a dot, or better as a space. I figured out that changing the table is indeed an option, but I have to edit every entry that is possible "unprintable". But it would be easier if there was a "generic" substitution of an unprintable character. And last but not least (up till now): if I have such a possibility or if I eventually change every character in the table, can I then save that table?? so that I don't have to do the action every time again.

sorry for so much text!

It looks like a technical problem..... I have here at the companie Windows7 server 64 bits. Some options like /r work fine, others like /B and lately I tried the /LINE: option to specify a certain wrap length, theij don't work as a command line option. Is this perhaps a shortcoming because I have an unregistred version?

regards

I start V with the following options: v.exe /b /vh /r /flat /text.

You should not use /flat as this option basically ignores all end of line characters. And you should not use /r as this option is not valid when specifying a file name on the command line.

If you have an EBCDIC file that will not view correctly with "V /b /vh /text" please send it to v at fileviewer.com

is it possible to edit the EBCDIC-ASCII table so that "unprintables" wil not display as a small square

The character printed depends on the display font. You can use the EBCDIC section of Preferences to change the mapping of the unprintable EBCDIC characters to a space (instead of an unprintable ASCII character). However, this is only possible with the registered version of the program.

I figured out that changing the table is indeed an option, but I have to edit every entry that is possible "unprintable".

Yes, but you only have to do it once. Once you change the mapping it will be used for viewing all subsequent EBCDIC files.

lately I tried the /LINE: option to specify a certain wrap length

I assume you mean /LEN: as there is no /LINE option.

All options work in the unregistered version. If you find something is not working, please tell me the exact command line that you are using.

I have sent a seperate mail with the examples

best regards