Running Anzio on a File or Terminal Server

The information provided below is confidential and is intended for
registered users only of the AnzioWin and Anzio Lite software.

The notes below are general guidelines describing Anzio Lite and AnzioWin and how these interact with their various support files. These notes are simply that, notes to help you decide how to best utilize Anzio Lite and AnzioWin in your own environment.

These notes apply to both Windows File Servers and Windows Terminal Server editions as well as Citrix and other network configured servers. Again, what we are trying to describe is how Anzio Lite and AnzioWin behave so that you can adapt them to your particular site’s needs.

Files necessary for Anzio to run

AnzioWin and Anzio Lite utilize three files when running, the default file, the key file (associated with the terminal type) and the executable. These three files are all that are needed. A fourth file may be required in a network environment, the license file.

Default files

By design, the default file name is "anziowin.def" and is located in the home c:\{anzio} directory (usually c:\”Program Files”\Anzio15\). Both AnzioWin and Anzio Lite use the same settings file when no other file is listed in the command-line or the shortcut's target.

If you wish to point to separate default files, you do so by referencing the new file name in the command-line or target-line for a shortcut, i.e.
            c:\anzio126\anzio32r.exe newdefaults.def

Key files

The key file is pointed to by the default file and should also reside in the current Anzio directory. This contains all the key maps and macros that may be referenced by the particular terminal type being emulated. This file name usually matches the terminal type name, i.e. vt220.kys,
but may be user defined.

Server Setup Recommendations

Default file access

When setting up Anzio Lite or AnzioWin to run from a server, the issue is one of whether someone can or cannot change the default files, or do you want to set up individual default files for each user.

When the Anzio program is first brought up it will look for the default file of "anziowin.def" unless one is specified on the command-line. Then that specified file will be looked for.

The first approach is to mark this file as "read-only". If the default file is marked as a read-only file, AnzioWin and Anzio Lite will pay attention to this and not allow any user to save parameters, nor will it ask when the user exits even if they have done some change.

A second, approach would be to set up a single default file for each user and then reference this by a shortcut, i.e.
            c:\anzio126\anzio32r.exe user1.def
In this manner you could set a shortcut that uses the User's login name. You could also reference a user default file by some user environment variable, such as
            c:\anzio126\anzio32r.exe %username%.def

Deployment

AnzioWin and Anzio Lite use only three files when executing, the executable, the default file and the key file referenced in the default file (see the File:Read Keys menu item), as well as an optional fourth file, the license file. You can then deploy just these 3 or 4 files, or you can reside them on a file server and set up access accordingly.

The license file is optional and may or may not be needed. See the notes below for information on this file.

Serial Number and Activation Code

AnzioWin and Anzio Lite license information is normally carried in the Windows registry entry for each Windows installation. However, in the case of a network file or terminal server, we have a mechanism for getting around having to install the license information each time.

First create a blank file in the current Anzio directory called "ser.ini" (this file can be created with Notepad). Then bring up Anzio and enter the license information again (the program will either ask you when it starts up to "Enter license code" or you can go to the Help : Enter License
Number menu item. This should write a secure version of the license information into the ser.ini file.

When a shortcut then runs the executable program from that directory, it should see the ser.ini file and not look in the Windows registry. On most Windows systems you should be able to also mark this file as "read-only" to prevent someone from overwriting or removing it.

This license file, "ser.ini" could then be deployed if you are doing a file server install script, saving you from having to enter license information on each machine individually.

Conclusion and More Information

Always check our web site and Support documentation for more information. This should help get you started with network installations. If there are any questions, please contact us at rsi@anzio.com.