All Frequently Asked Questions - All

Anzio Lite does not support any keyboard remapping, macros or scripting of any type. While it may respond to some functions and commands sent from the host or from another AnzioWin keymap, these are very limited and it cannot remap keys or build its own macros. To do this you would need AnzioWin.

On Windows Vista or Windows 7 systems, the AnzioWin and Anzio Lite installer may not run successfully. This can be due to certain group or user policy settings, or to a restrictive user being limited in what it can do. It may also be caused by the browser you are using and certain restrictions applied by the browser or by your site security settings for that browser. In many cases there is a work-around. If you do have problems, try the following steps: a) If you are not using Internet Explorer, close your current browser and try the download through Internet Explorer. Go to www.anzio.com and select the correct product and version. b) When asked if you want to "Save" or "Run", do a "Save" and place the file on your Desktop. c) Once the file has been downloaded, try running the file from the Desktop. If your Windows Vista has UAC, User Access Control, enabled, you should right-click with the mouse and do a "Run as Administrator". Otherwise, click and see if the install goes better from here. d) If you still have problems, log out from the user account and try the same steps as the Windows Administrator. In some cases, a restricted user download may not allow for an install to take place. Make sure you are running as Administrator. e) If you still have problems, we recommend contacting your PC or system administrator. They should be able to help you get the proper permissions to do a download and install. This should allow you to do an install on any Windows Vista machines. If you are getting errors other than security permissions, search our web documents and notes on the particular error you are getting.

When installing AnzioWin or Anzio Lite you may run into a number of different error messages, many of which seem quite cryptic. These errors usually indicate one of two things, a missing file or no permissions to load/access a necessary file.

When an installation fails, here are some quick steps to try:

1. If you are on Windows XP, 2000 or 2003, make sure your login has administrative privilege, or log in as "Administrator".
2. Often a custom or mirrored OEM version of Windows, will miss some of the key files needed for installation, if you are running an OEM version of Windows, certain errors, such as the "ikernel" error, may occur. You can usually do an Internet Explorer or Microsoft Office update, and it will fix this problem.
3. It is possible that some other setup or install left a file loaded in memory or without any user rights. Restart the machine (don't just log out and log back in) and immediately try the installer again.
4. If the setup program still fails, check out our knowledgebase article on installing and uninstalling errors with Anzio for more information and troubleshooting tips.
5. If all else fails, give us a call and we can walk you through alternate approaches to installing Anzio.

Our normal licensing for Anzio Lite and AnzioWin is a per PC license. Additionally we offer a concurrent-use license. However this requires that you have your own license management software already in place. Concurrent use license would allow you to run a specified number of Anzio Lite or AnzioWin sessions at any one time, but have the ability to install the software on an unlimited number of machines. Concurrent use licenses are 40% above the cost of a normal user license. At present we do not offer any enterprise-wide or site license options. We do offer aggressive quantity discount licenses however. If you have a specific need for more than 100 copies, give us a call for a discounted price.

SSH servers are available for most Windows and UNIX platforms from several sources, including SSH Communications Security (www.tectia.com), Red Hat (www.redhat.com), SSH.Org (www.ssh.org) and others. Please refer to these sites for the correct version to download and the instructions for its installation. As for setting AnzioWin up to use with SSH, you do so with a clean startup, or by changing the communications method under the Communicate:Setup dialog. AnzioWin 12.5 and later support login and password authentication over the SSH1, SSH2 and OpenSSH protocols. Starting with version 12.6n, we also support public key authentication with SSH2 and OpenSSH (call for information on public key setup).

There are many things that control a connection for Anzio Lite and AnzioWin. This includes network devices, the host application, the host operating system, user login scripts, Microsoft Windows settings and more.

Telnet and Secure Shell (SSH) connections are stateful connections and must be up and available whenever a character of any type is passed either direction. If not, the user's connection can be dropped and thus, depending on the settings in Anzio, the Anzio window may close. This type of failure usually indicates some network or server action timed out, or the network connection was not available.

This is different than how the FTP (file transfer) or HTTP (web browser) protocol behaves, these protocols simply try to reconnect since no login is necessary.

These type of dropped connections are most often seen when connecting over the Internet through an ISP (Internet Service Provider). They can also occur when a hub, router or network switch is not properly configured or when one of these devices is beginning to fail (generating errors). There are some options a user can do to try to get around the issues:

1. Contact your ISP and let them know you are doing telnet or secure shell connections and the connections are dropping (if you get the right tech person, he/she will know what is miss-set in your connection to them).
2. Check your devices in-house and see if one of them is getting errors in their log file. If they are unmanaged devices, switch ports and see if the problem moves.
3. Make sure the host system is not timing out. There should not be a "tmout" or "tout" inside your host script files (.profile or login scripts). Also make sure the host and PC network cards are not generating any network errors.
4. Try setting the "Stay Alive" parameter (available in version 15 or later). Check under the Communications menu and Network : Stay Alive. This option, when set greater than zero, will send a single empty packet over the network stating that Anzio is still alive and working (typically set this for 30 seconds). However, setting this option too low may only show the problem earlier and more often and not really hide it. Again this option is masking some other problem or misconfiguration, but it will help in about 80% of the cases.

Check out the following pages for more information:

• A Guide to Telnet
• Troubleshooting a Telnet Connection
• Connections Timing Out

You did not miss a release. In October 2003, Rasmussen Software released a major revision of AnzioWin and Anzio Lite. However, due to our international community of users, versions 13 and 14 were not released. Version 15 is what we started shipping after version 12.7.

See "How to get rid of a corrupt file"

AnzioWin and Anzio Lite are supported on Windows XP and later. To run on Vista or Windows 7, we require version 16.2.

Both AnzioWin and Anzio Lite are 32-bit Windows programs, but run fine on either 32-bit or 64-bit versions of the above Windows platforms.

Normally, a web object such as WēPO is installed on client PC's as needed by simply clicking on the component on the web page. However, today's security is an issue and even though the WēPO product is signed and trusted with an Authenticode signature, people still worry.

You can install the ActiveX object before hand and avoid having to set and reset Internet Explorer security. From our web site you can download either the .OCX or the .CAB file for Print Wizard OCX, also called WēPO. You can download either one, though manual installation of one is easier than the other. The .CAB will contain the Authenticode signature and the .OCX file, while the .OCX is the actual ActiveX control to install.

If you download the .CAB, you need to extract out the .OCX file from it. On Windows 2000/XP you can do this by bringing up Windows Explorer, click on the .CAB file and "explore" it. Then right click on the PWButtonXControl1.ocx file and "extract" it.

Once you have the .OCX, do a Start : Run and enter the following to install (register) it:

regsvr32 PWButtonXControl1.ocx

To uninstall (unregister) it, do

regsvr32 -u PWButtonXControl1.ocx

To do this automatically you could set up a small batch file to do the work or burn it to a CD with an autorun if needed, as the regsrv32 will act like an install and copy the .OCX from where it is to where it needs to be for Windows.

For future releases, we will be also making available a self-install copy of the program.

Yes, we have AnzioWin and Anzio Lite running on many terminal servers around the marketplace. The only catch, similar to running from a file server (see above), is manually setting up shortcuts and making sure default files are referenced and read-only as necessary. As for entering a serial number/activation code for each workstation, this may not be necessary. We do have a method of accessing a global license entry - call for more information. Note that AnzioWin and Anzio Lite are licensed on a per-workstation base, a single license for each node accessing it from a terminal server, not one license per server, but one license per workstation.

Troubleshooting modems can be quite frustrating and time consuming. A couple of simple hints when connecting through AnzioWin or Anzio Lite: a) Make sure your host modem communications software is set correctly. It should handle the modem as a standard serial device (tty) and NOT as a PPP connection. If you are wanting to connect via PPP, use Microsoft's Dial-Up Networking to connect, and then run Anzio as a telnet, rlogin, or SSH connection. Also, check to see if your host serial port is set for "baud cycling" (common default setting on UNIX), whereby the baud rate may change if any errors are encountered. b) Make sure the host modem is set for dialing in (auto-answer). By default, modems are not configured to answer, you must configure them to do so. c) Know what your modem connection rates and settings are in advance. Remember that the host modem usually connects to the host over a serial line (unless it is internal) and if the PC uses an external modem, it too connects to the PC serially. Also, know the parity and stop bits. You then also have the rate of connection between the two modems (over the phone line). d) Test the host modem connection. Try dialing in manually and make sure the modem on the host picks up. You may also want to check with the system administrator for the host and make sure the modem is working for others (and that it has been tested). e) While there are standards out there for the higher speed modems, there are still a couple of different standards for error correcting that are followed. Know what each modem is set for. Compatibility among modems can be a real problem. f) If you are running an inexpensive PC internal modem (also called a WinModem), make sure you are using the latest drivers. These modems have little hardware and are driven by Windows software. Almost every one of these modems has had a major software update for each Windows version. And remember that even Windows ME, 2000 and XP may not ship with the latest drivers.

Anzio, and telnet in general, is a connection oriented protocol, requiring the connection remain up during a session's duration. However, network devices, traffic, auto-disconnects, etc., can cause the connection to be lost. Neither Anzio nor Windows has an auto-disconnect feature, but are dependent on the network staying active.

Sometimes you can fine tune the TCP/IP parameters to not respond quite so quickly or to retry more often before determining a connection as severed.

With the latest versions of Anzio Lite and AnzioWin (version 12.5 or later), you can also set an option that will occasionally send a single keep-alive packet to the host. In most cases this will work fine in keeping a connection open, especially over the Internet. However, remember that in doing this you are actually hiding some other issue that may cause problems down the road.

This option can be set in version 12.5 by doing a hexpatch command to the default file:

<ctrl><shift>f                                                  (to get to the Function line)
HEXPATCH 18c2 05<enter>

To use this feature in version 12.6 or later, go to Communicate:Network:Stay Alive, and enter an interval in seconds.

Anzio does nothing with time-outs. In fact, we totally depend on Windows and Windows is dependent on not getting any type of disconnect from the host. Within Windows, there are a few registry entries that relate to keeping a connection alive (refer to a reference guide on Windows Registry troubleshooting for more information). These determine when Windows will check for a dropped connection (how long to "stay alive") and how long to wait before determining the connection has been dropped from the other end. However, these do not determine time-outs. Rather Windows TCP/IP simply responds to a dropped connection. The most common problem for the dropped connection has to do with other network devices. A couple of examples are a) a router that drops stale "routes" out of its table after a period of time, b) WAN connection devices that occasionally get long latencies between the PC and Host and c) other devices, such as bridges, VPNs, firewalls, etc., that drop "stale" connections when a table fills up or idle period is reached. Of course, there are other causes, such as the host shell script having a time-out included, the host telnet server having time-outs set, etc. Sometimes you can fine tune the TCP/IP parameters to not respond quite so quickly or to retry more often before determining a connection as severed. Check out the Microsoft web site for some helpful hints.

See our document on Using Anzio to Connect to Multiple Host Systems. This will describe how to set Anzio up for multiple host connections.

Version 12.5 or earlier of AnzioWin or Anzio Lite does not support these media file types. You could set up a macro in AnzioWin that would transfer the file and then launch it for Windows to handle. Starting with 12.6, the PLAYMEDIA command can play video as well as audio.

AnzioWin and Anzio Lite work well with terminal servers and in running them from file servers. However, do remember that AnzioWin and Anzio Lite licenses are on a per PC user. On a file server or terminal server this refers to the number of nodes that will have access to the server.

In order to set AnzioWin or Anzio Lite up to run from the server, install the product on the server and permit access to the users. That's it! Well almost. Two things that may be a headache:

1. Anzio looks for its default file, called AnzioWin.def, within the Anzio program's home directory. You can set every user up to use this default file by simply saving it as you'd like and then marking the file as "read-only" so not everyone can change it and affect others. OR you can set up individual anziowin.def files in user directories and when you create the shortcut, include the file name (see 3 below).
2. Anzio requires a registration/activation license code in order to run. You can purchase individual licenses for each user, one quantity license to share among each user, or you can install the license on the server (saving from having to enter it for each user). If you wish to do this last option, give us a call and we can let you know how to do set it up for a server.
3. You do need to create the shortcuts on each users desktop. With most server software, you can do this easily. If you need to give each user access to their own default file, it may take a little more work. A shortcut can point to individual default files by doing

<executable name>  <default file name>

  such as

f:\anzio126\anzio32r.exe $UserHomeDir\anziowin.def

Passthrough printing allows a host computer to send a print job through the user's terminal (emulator) and out to an attached printer. It is sometimes called "local print", "attached print" or "slave print". This means the user must be logged in to the host. The host then sends a sequence of characters that causes the telnet or terminal emulation software to redirect its output to a local printer until a similar sequence is received to turn off the passthrough printing. In our document library we have an excellent document talking about passthrough printing, how your host support should be set up and how Anzio works. See the A Guide to Passthrough Printing document for more information.

When you have a host application that does not support passthrough printing (printing that goes through the Anzio telnet session), your options are somewhat limited.

The most common approach is to set up the LPR/LPD protocol to do the remote printing. This works by acting as a back channel from the UNIX spooler to redirect the output through LPR on the host to an LPD server (daemon) on the PC. With our standalone Print Wizard product, we provide PWLPD which is a robust LPD for the PC.

The second approach is to use netcat (freeware for UNIX), netprint (our product included with Print Wizard also) or H/P JetAdmin for UNIX. H/P JetAdmin redirects to the output from the UNIX to a specific printer attached to the network with a JetDirect device. Netcat simply dumps data to port 9100 at another IP (the data can then be captured and printed). Netprint is a UNIX utility included with our Print Wizard standalone product that sends data from UNIX to the PC's printer using port 9100 and Print Wizard on the PC.

The catch: These products work fine as long as the remote user's IP address is known in advance (a static IP). However if the user is coming in over the Internet from an ISP, the dynamic IP will change each time. To solve this problem, it is easiest to have a login script that runs which modifies the LP print queue for a specific user during a specific session. It can be a pain to set up, but works smoothly once done.

Our netprint program, though, does have the ability to determine dynamically what IP you're coming in from, and route a print job to that IP address, where you can have Print Wizard running.

FTP is the "file transfer protocol" most often used over the Internet. It is even used by most browsers when doing downloads. Starting in version 12.6 of AnzioWin, we included an integrated FTP client that could auto-login to a host, transfer files and provide some user feedback. It could also be used within macros and scripts for AnzioWin.

AnzioWin version 15 introduces SFTP support, FTP over a Secure Shell connection. SFTP encrypts all its data and control sequences during a SFTP session, just as SSH would for a terminal session.

There are major differences however. FTP actually runs utilizing the Windows "wininet" routines and requires opening a separate network connection to the host requiring a separate login and password be entered again (though AnzioWin can do this in the background). This also means your firewall must allow FTP connections in and out.

SSH SFTP does not require a separate login, does not require a new network connection and does not require access through a firewall. SFTP works over a "back-channel" of SSH, running in the background of the same SSH session you are currently logged into.

More information can be found in the Anzio manual, How-To and Read-Me files, and in our support pages at our web site.

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.

Commonly what we see is that someone is running Zmodem, Xmodem, Ymodem over a network connected Anzio and expecting it to work as it would over a serial connection. In about 75% of the cases it may work great. But in the other 25% of the cases, these protocols fail and usually fail badly. There are several contributing factors to this:

• network drivers - the network speed, how network traffic gets routed and buffered internally
• the X-ON/X-OFF protocol for controlling packet loss
• issues with dropped packets and getting out of synch
• problems with numerous releases and whether the one on your system has been updated to work over a network

You can play with parameters in Anzio, namely windows and buffer sizes, and you may be able to get better functionality out of it. Check with the vendor of the operating system and ask if anyone is running these protocols over network connections. However, we recommend using FTP for network file transfers. You will find FTP about 200% faster and more reliable for moving files between systems.

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".

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 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.

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"

The "-r" is necessary on the read to not strip the backslashes and if you need to redisplay the file name with just an echo or use it within other variables, the "file=..." string will escape the backslashes for you.

There are a couple of commands that will help in situations where you continue to have problems with backslashes.

First, you can set the default directory separator character (a backslash) to be something other than the Windows default with the "dir-separator" command.

/usr/bin/printf "\034%s\035" "dir-separator | "

You will then get back a file name with that character separating the path directories, i.e. c:|myfolder|myfile.pdf.

Additionally, when a dir/s, findfirst/s, findnext/s or other directory commands fail or are completed, they return, by default, a double-backslash, i.e. \\. This too can be difficult to work with on some hosts. So we have a command to adjust this as well, the "dir-terminator" command.

/usr/bin/printf "\034%s\035" "dir-terminator DONE "

In this example, instead of a double-backslash being returned when a directory command is complete (or fails), the word DONE will be returned.

More information can be found in the AnzioWin manual and whitepapers, as well as in the readme.txt file shipped with each version of 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 host has a user limit in effect
• The host name or address is wrong
• The port you are trying to connect to at the host is incorrect
• The default file is corrupt
• You have selected the wrong terminal type for your host login or your host application
• A router with port forwarding is limited to a single user and already in use
• The login you used is limited to one connection and is already logged in

For any of these, check to make sure you have set up Anzio correctly for your host connection (correct port, correct host name or IP address, correct terminal type and correct login). If all else fails, you can try clearing out the default file for Anzio and reset the startup settings:

1) Look under the Windows Start menu and All Programs for the Anzio folder. Inside this folder you should see the item "AnzioWin (new connection)" or "Anzio Lite (new connection)". Run the appropriate menu item to start Anzio without a default file.

2) If Anzio was working but is not now, try renaming or deleting the file "anziowin.def" located in the same directory as the executable. By doing this you will have to re-enter all your initial values, but it should clear up the bad record.

3) You can also accomplish the same thing as above by starting AnzioWin or Anzio Lite from the Start:Run dialog by entering:

c:\anzio126\anzio32.exe none
        or
c:\anzio126\anzio32r.exe none

The word "none" will start Anzio without a default file. You can then save the new settings over the top of the old when you exit, thereby replacing the bad default file.

This error occurs with certain combinations of Anzio versions and old Windows versions. It can be fixed by updating to the latest AnzioWin or Anzio Lite. Also check to see that you are running all the service pack releases available for your WIndows operating system.

The communications DLL is the Windows module performing the communications between Anzio Lite and AnzioWin and the external connection. If you are connecting via a serial connection, the probable cause is that something else already has the port in use. Check for conflicts in the communications COM port and check for software loaded in the background using the same port (if it's a modem, check for fax software). If you are connecting over TCP/IP, check to make sure that you have a connection to the network first. If you are dialing in to the Internet, your ISP service (Compuserve, MSN, etc.) must already be connected and you must be logged in. If it is a direct connection, check to see that the "Control Panel:Network" properties are correct. Also, if you are using a 16-bit version of Anzio Lite or AnzioWin, there should be one and only one, Winsock.dll found (it is usually under the \windows directory). Multiple winsock.dll are as much a "no-no" as is none at all.

There is an increasing number of printers and printer drivers hitting the market for Windows. Also, there are an ever-increasing number of applications which manipulate the printer driver. While we do attempt to support all options, we have found that certain applications "mess" with the printer control record causing Anzio's setup to become corrupt. Once the default file becomes corrupt, there are two possible fixes.

First, if you have more than one printer installed under Windows, go to Printer Setup and choose a different printer, save defaults and try printing (if this is an option).  Then return to the printer with the problem, save defaults again and try printing.

Second, if the first is not an option or does not work, is to create a new defaults file. Make sure you know the default file name you are using, i.e. anziowin.def, the keys file being loaded, i.e. vt220.kys, and your communications setup options. Go to the File:Run or Start:Run dialog box and enter the executable name followed by the word NONE. This will start Anzio without a default file. Go through the setup procedure and log back in to your host. Select the printer again under Printer Setup and attempt to Print Screen. If it's ok, be sure to re-save the defaults under the correct name. If this fails, give us a call.

You can download the Print Wizard installation program from our web site, or order it on CD. Run the setup program in order to install Print Wizard on your Windows PC. It is as simple as that.

Setting up Print Wizard may involve a little more time however. You do need to know what you are going to be using Print Wizard for and how you will be printing through it. There are also numerous examples included that will help you determine what Print Wizard is capable of.

When you run the install program, you end up with a desktop icon for Print Wizard. This is the user interface and will give you the opportunity to set it up the various options available, include the services you may want to run.

Refer to the Print Wizard manual for more information on using Print Wizard and Print Wizard services.

Winsock errors normally come from some network problem that has occurred. Most often causes fit into two different categories: hardware (bad network cards, bad cabling, network down, ..) and software (firewall blocking inbound traffic, Internet security software blocking inbound traffic, personal firewall blocking port traffic, software already using a specific network port, .).

If network traffic seems normal, i.e. your web browser seems to be working, the most common problem is software related. Two major problems occur frequently, there is some security software blocking inbound and outbound network port traffic, or there is some software already using the network port Print Wizard Services, such as LPD needs.

Personal firewalls and internet security suites, such as McAfee or Symantecs, or Microsoft's own Windows firewall maybe blocking port traffic for the LPD service.

The best first test is to disable the firewall portion of your security software and see if the LPD service will run. If so, turn back on the firewall or security software and check to see if you can add the network port to an exceptions list, or add the Print Wizard program to the application exceptions list (PWLPD.EXE for Print Wizard Service or PWSERVICES.EXE for the Windows Service).

Two different methods can be used to set up the printing for a print queue, a) through a profile or b) direct through the command line option.

Through A Profile:

A Print Wizard "profile" is a textual file defining how a print job should behave and what settings to use, including the init file. When you set up a print queue, you can specify a profile name to use for a specific queue. These "profiles" are set up via the User Interface and the Tools menu for "Setup profile" and the Properties:Print Wizard tab. You can then associate a Print Wizard "profile" with your queue (see the Queue Properties).

Direct:

Through the User Interface, go to the Tools : Setup Services : Properties dialog, select your queue and go to its Properties. Under the Queue Properties and the "Action to take" tab, you can actually specify the job to run for this queue (the 'Default program or script...'). Here you can add the init file direct to the executable line for Print Wizard:

C:\printwiz3\printwiz.exe /q /minimize /vdocname=PWS /vinit=abc.init

(check the path of course....).

Those are the two ways. The objective in this version is to provide more flexibility and this does make things a little more complicated, but the general features are still the same.

From the Print Wizard user interface, under the Tools menu, you can set up faxing and the default fax method to use. Check mark the default fax method that you want as the default. You can usually determine if any fax software is loaded by looking at your Control Panel : Printers and Faxes to see if any fax drivers are available (as an example a printer driver called "fax" on Windows XP and later is usually referred to by us as "fax32", whereas one called "WinFax" or "WinFax (Photo Quality)" is usually Symantec's WinFax Pro).

Through the Print Wizard user interface you can define "print profiles". These "print profiles" decide what to do when processing a job with a profile, including the ability to email. When you define the profile, the user interface will ask you if you want to create a desktop shortcut. If you answer yes, you will end up with a desktop icon that you can drag and drop files on that will then get emailed.

If you want to manually set up a shortcut, you can do so by including the profile name on the command line, or target line, for the shortcut:

C:\Program Files\Printwiz30\printwiz.exe /profile=myemailprofile.profile

You can take this further by setting up the drag/drop profile to do one of the following:

• Always email to a specific address
• Include specific email information, such as the subject, notes line and attachments
• Always ask where to email to

You can then open up your Windows Explorer or other file applications and drag a file from there and drop it on this shortcut to email as you need.

In the case of email, all files are sent as attachments. You can also specify additional files by browsing for them when using the Email Form input screen (through both the user interface and the Print Wizard engine), or by specifying it on the command line for the Print Wizard engine:

printwiz.exe /email=abc@def.com /ac:\temp\file.doc myfiletoemail

Different behaviors may be noticed with different email options. Contact us for more information.

Yes, Print Wizard version 3.0 or later supports printing a PCL file directly. The question may be one of what level of PCL is the file in and whether your printer supports PCL. If you are printing to a non-PCL printer, and the PCL codes are for version PCL 5 or earlier, you can turn on "translatepcl" with a command-line switch (or via a "print profile") and Print Wizard will translate this to your specific printer. If you are printing to a PCL printer, and the file contains PCL 5 or earlier, you can either print this direct or with the "translatepcl" command-line switch. If you are printing a PCL 6 or later file, you need to print this to a PCL 6 or later printer driver as it will not work with a PCL 5 or earlier driver, not can Print Wizard handle the translation to a normal printer driver. This means that you cannot print PCL 6 on a non-PCL printer currently.

The Print Wizard engine allows you to convert any printable file into a PDF file by simply printing it with the appropriate switch settings:

Printwiz.exe /pdf /fFilename.pdf myfilename
Printwiz.exe /fpdf:// myfilename
Printwiz.exe /fpdf://myfilename myfilename

You can also generate PDF files through the user interface menu items.

Specific printer and printer drivers have differing unprintable areas. Along with this, there are also the issues of margins. Some of this can be controlled by PWML code in an "init" file, or by setting items in the printer driver itself. Getting overlays to fit properly can be a chore. We can help. Give us a call and we can usually come up with a solution.

Print Wizard supports several graphics file formats, including the option to print them at true size or at full page, stretching as needed. The possible formats are TIFF, JPG, GIF, WMF or BMP.

The simplest way is to lay out your print document and print to a PCL 5 or earlier printer driver. When you do this, go into the printer driver and select "Print to file". It should ask you for a file name that can then be saved off for future use.

Even if you do not have a PCL printer, you can install a PCL printer driver to generate print files from. Do an "Add printer" and select an H/P printer that supports the level of PCL you want. Then set the "Print to file" flag and use it to print through. The PCL file can then be used for subsequent printing, for overlays or for other reasons.

If you first bring up your print file with Print Wizard engine and the Preview command-line switch set (or do it through the user interface), you can then reselect the starting label.

Refer to the Print Wizard manual for more information.

PWML, Print Wizard Markup Language, can be added to the beginning of any file directly in the data stream or by specifying a PWML print "init" file. Print "init" files can be specified in a print profile file as well, or can be referenced on the command-line for the Print Wizard engine to use:

C:\Program files\Printwiz30\printwiz.exe /vinit=myinit.txt myfiletoprint

Printer errors, especially those in the 5000 range, usually indicate that we are sending data to the printer that the printer cannot understand. A good example would be sending PCL codes to a non-PCL printer or sending Okidata escape sequences to an H/P Laserjet, or sending raw data to a Windows-only-printer.

By default, the Print Wizard engine will determine if the file contains printer-specific escape sequences and then try to send the data in either spooler or raw print level. Many Windows-only printers cannot accept raw data and this will cause a printer error.

Likewise, if Print Wizard determines the file has Okidata escape sequences in the data stream, and you try to print it on an H/P Laserjet, the printer driver will generate an error.

The Print Wizard engine is designed to be fully functional through the use of print profiles and command-line switches.

• You can run Print Wizard through a shell execute or Exec command. With the "/q" command-line switch to prevent any dialogs from appearing and will return error codes to the hosting application.
• You can run Print Wizard from a file association by specifying a specific extension as being printed with Print Wizard (see the Print Wizard manual on setting it up as a File Association). Then you simply start the file through a shell execute or Exec command.
• You can include Print Wizard in a script that runs from your program, returning an error code if the print job should fail.
• You can run the Print Wizard DLL, calling the various methods exposed to allow Print Wizard to handle all your printing needs.
• You can run the Print Wizard ActiveX module from your program. WePO exposes a subset of the Print Wizard calls, allowing you to use it in your .NET or Windows application.

At present, Print Wizard does not support COM or DDE directly. We are working on this for the future. If you have any need let us know.

The Print Wizard DLL is designed to interact with the many features of Print Wizard through program calls. These program calls are made by your own Windows program or script and result in Print Wizard doing all the print work for you. Check out our documentation on Using the Print Wizard DLL.

Print Wizard Personal Edition includes the basic of the user interface, the Print Wizard engine and the Print Wizard DLL. It does not support any remote or despool Print Wizard or Windows services.

The Service Edition is designed for those PCs that will be receiving print jobs from remote locations or despooling print jobs from a specific remote or local directory. Print Wizard Service Edition supports the Despool, FTPDespool, Listen and LPD protocols.

The demo version of Print Wizard includes all capabilities. If you have been working with the demo version and are ready to order, and you're wondering which version you need, the test is simple: if you're running a service, you need Service Edition.

There are two methods available.

By default, the desktop shortcut set up to the Print Wizard installer will cause the file dropped on it to print with the default Print Wizard settings including auto-fit, auto-margins, etc.

For more advanced printing needs, you can go through the Print Wizard User Interface program (PWUI) and define a "profile". These profiles determine what to do when processing a job with a profile, including the ability to print with specific options set.When you define the profile, PWUI will ask if you want to create a desktop shortcut. If you answer yes, you will end up with a desktop icon that you can drag and drop files on.

If you want to manually set up a shortcut, you can do so by including the profile name on the command line, or target line, for the shortcut:

C:\Program Files\Printwiz30\printwiz.exe /profile=myprofile.profile

You can take this further by setting up the drag/drop profile to do one of the following:

• Always fax to a specific number
• Include specific fax information, such as the subject, notes line and attachments
• Always ask where to fax to

You can then open up your Windows Explorer or other file applications and drag a file from there and drop it on this shortcut to email as you need.

Below is some information on setting up WēPO both at the server and for the client PC. Additional information can be found in other knowledgebase articles on Print Wizard and WēPO and in the various user manuals.

At the PC

Normally, a web object such as WēPO is installed on client PC's as needed by simply clicking on the component on the web page. However, today's security is an issue and even though the WēPO product is signed, PCs may not allow it to be downloaded and installed automatically.

You can install the ActiveX object before hand and avoid having to set and reset Internet Explorer security. From our web site you can download either the .OCX or the .CAB file for Print Wizard OCX, also called WēPO. You can download either one, though manual installation of one is easier than the other. Both contain the Authenticode signature. The .OCX is the actual ActiveX control to install, whereas the .CAB file is compressed into a Windows "cabinet" file.

If you download the .CAB, you need to extract out the .OCX file from it. On Windows 2000/XP you can do this by bringing up Windows Explorer, click on the .CAB file and "explore" it. Then right click on the PWButtonXControl1.ocx file and "extract" it.

Once you have the .OCX, do a Start : Run and enter the following to install (register) it:

regsvr32 PWButtonXControl1.ocx

To uninstall (unregister) it, do

regsvr32 -u PWButtonXControl1.ocx

To do this automatically you could set up a small batch file to do the work or burn it to a CD with an autorun if needed, as the regsrv32 will act like an install and copy the .OCX from where it is to where it needs to be for Windows.

For future releases, we will be also making available a self-install copy of the program.

At the Host

In order for a client to download the WēPO ActiveX module, you still need to have it referenced somewhere from your web site. If you are running a licensed version of WēPO, you can include the license information and the download location in your web page script that calls this ActiveX. Check out our examples on our web site to get an idea of how to integrate this in at the server side.

WēPO is usually called by a specific class from a web page. By inserting the appropriate ActiveX information into the web page, you can force the WēPO component to be displayed.

<OBJECT classid="clsid:659D3554-54CD-46BC-B0F1-D88C4CCFD10C"
   codebase="http://www.mysite.com/controls/printwizocx.cab#version=2,7,0,0"
   width=263
   height=71
   align=center
   hspace=0
   vspace=0
   ID="Pwbuttonx1" VIEWASTEXT>
<param name="mainurl" value="http://www.mysite.com/reports/myreport.txt">
<param name="caption" value="Print">
</OBJECT>

Simply place this <OBJECT> tag in your html in the location you wish for the button to appear.

There are several items you need to be aware of in trying to troubleshoot WēPO.

1. For each version of WēPO, there is an unique class identifier, clsid, that is called by the web page. This object, the referenced version number and the codebase referencing a specific .CAB or .OCX file, all combine to make sure you are running the correct ActiveX component. They must match up or your ActiveX component will not be called. Everytime you receive a new version of WēPO, be sure to check our web site to make sure you are using the correct classid.

<OBJECT classid="clsid:659D3554-54CD-46BC-B0F1-D88C4CCFD10C"
   codebase="http://www.mysite.com/controls/printwizocx.cab#version=2,7,0,0"
....    

2. The web browser needs to be able to print to some printer. This is usually not an issue, but we have seen a few Windows and Internet Explorer installs come back with no default printer. Make sure you have a default printer designated at the Windows level and that Internet Explorer can see this printer under the File menu and Print...

3. The file being rerferenced by the "mainurl" parameter must be available to be fetched by the web browser. Have your web administrator check permissions if you suspect problems here.

<OBJECT classid="clsid:659D3554-54CD-46BC-B0F1-D88C4CCFD10C"
   codebase="http://www.mysite.com/controls/printwizocx.cab#version=2,7,0,0"
   ...
   ID="Pwbuttonx1" VIEWASTEXT>
<param name="mainurl" value="http://www.mysite.com/reports/myreport.txt">
<param name="caption" value="Print">
</OBJECT>

4. Lastly, any personal firewall security may cause a problem, as well as certain settings within Internet Explorer's Options. Check to be sure yopur security settings a) allow a download and install of the ActiveX, and b) they do not prevent ActiveX from running.

WēPO is an add-in, ActiveX module for web pages. These are stored within the Windows directory in different locations (depending on your release of Windows and whether the user has administrative permissions).

The first place to look is in the Internet Options (under the browser's Tools menu item or in the Control Panel). Under the Programs tab, you can click on "Manage add-ons" and from here disable it and update it.

Likewise, you can un-register the product and then update it through the web site in question. Check the WēPO documentation for more information.

Keyboard remapping is done through AnzioWin. While Anzio Lite does not support remapping itself, it can use a remapped keys file. So you would need at least one copy of AnzioWin to do the remaps and then distribute the modified key file to the Anzio Lite users.

AnzioWin key remapping is done similar to setting up macros. See our various support documents and knowledgebase articles for more information.

Print Wizard version 4 is supported on Windows XP and later, including Vista and Windows 7.

Print Wizard version 3 through 3.3 is supported on Windows XP and later. However, for Vista and Windows 7 we require you to be on the latest release of 3.3.

Print Wizard is a 32-bit program. It will run fine on either 32-bit or 64-bit versions of the above platforms.