First, make sure you have the right version of the program and the right program. A serial number and activation code for Anzio Lite 15 will not work with Anzio Lite 16. Likewise a serial number and activation code for Anzio Lite will not work with AnzioWin.
Several items can cause this behavior. If Anzio should try to connect, then flash off, or you get a "runtime" error, or you get passed the login, but Anzio disappears, there are several possibilities:
The problem is not usually AnzioWin in this case. The problem is the handling of backslashes by the shell you are running under for your operating system. Since backslashes have special meaning in most all shell strings, they have to be either escaped or handled special on input and output. Try something like the following (this may vary depending on your shell and scripting environment):
/usr/bin/printf "\034%s\035" "dir/s c: "
read -r file
printf "%s\n" "$file"
file="${file//\\/\\\\}"
/usr/bin/printf "%s\n" "$file"
User macros are created and edited using AnzioWin. While Anzio Lite does not support remapping itself, if these are simple macros (with no non-Anzio Lite commands), Anzio Lite can use macros set up by AnzioWin. So you would need at least one copy of AnzioWin to do the macros and then distribute the modified key file containing the macros to the Anzio Lite users.
The common problem here is that the currently loaded keys files does not match the current terminal type. Check under the "Communications" menu to see what Terminal Type you are set for. Then go to the "File" menu and do a "Read Keys" and select the corresponding keys file. Be sure to save defaults after this so that the proper keys will be loaded next time.
Another possible problem is that you need to remap a key or key sequence. This can be done with all Anzio products except Anzio Lite. Once a key is remapped, the key file can be used by Anzio Lite.
In short, YES. There are two procedures that are commonly used and I am sure others exist. With AnzioWin, commands can be issued from the host system controlling Anzio's functionality, either telling Anzio to run a PC program or have Anzio perform an internal function. The two most common procedures to follow involve ZModem or FTP. There are several helpful documents in our knowledgebase dealing with the various types of file transfers available through Anzio.
Yes it does, but there is a little more to it than that. Within SCO, the terminal type dictates if 'mscreen' will work properly. See our document on Using Anzio with 'mscreen'.
The first prompt ask for terminal type. The terminal type refers to the type of terminal the host is expecting you to be. Most UNIX hosts support vt220 and this is a good choice if you are unsure. However, certain applications may also expect you to be using a particular terminal type and will issue various escape sequences in anticipation of your session handling it correctly. If things do not look correct on the screen, or the screen does not clear as it should, it is probably the terminal type.
Ordinarily, Anzio will ask this question whenever any settings have been changed.
If you have moved, resized, zoomed, or unzoomed the Anzio window, this will also constitute a change, if View:Track Window Position is checked. You can uncheck this item (and save your settings one more time), and then moving the window will not trigger this message.
You can also change how Anzio behaves in Edit:Advanced Options:Security, under "Prompt to save parameters".
First off, see our document on Using ZModem in Anzio. This will describe some of the problems associated with ZModem file transfer.
One thing to remember with the Zmodem, protocols (including Xmodem and Ymodem) is that they are old protocols designed to work over serial connections.
