Frequently Asked Questions - Print Wizard

This is the overall Print Wizard family.

Print Wizard version 4 is supported on Windows XP and later, including Server 2003 through 2012, Vista, Windows 7, and Windows 8.

Print Wizard version 3 through 3.3 is supported on Windows XP and later. However, for Server 2008 through 2012, Vista, Windows 7, and Windows 8 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.

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.

WēPO is an add-in, ActiveX module for web pages. Thus it is something that is downloaded from a web site at the time of the page being displayed. Certain browsers may never allow ActiveX modules, others may not allow the download without user intervention, others may require changes in security settings and still others may download and install but not show the control on the screen until some user interaction takes place.

Add to this all the Internet Security suite software and the various anti-virus products on the market, and the display of the ActiveX may be questionable in some environments.

Likewise, Windows Security and Internet Security suites are in a constant state of flux and hence ActiveX controls, such as WēPO tend to work one day and not the next, depending on various updates and security settings. Check your products running and know when and what updates do.

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.

As mentioned above, WēPO is usually called by a specific class object from a web page. If you do not want the object button component to show, simpl make its width and height as 0 and then you can locate the class object anywhere:

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

Next you need to include your java (or other script) code to call the "click" action for the WēPO control. Something like this will work:

...
<input type=button value="my print" OnClick="javascript:buttonclick();">

<script language=javascript>
<!--
function click(){
document.Pwbuttonx1.Click();
}
//-->
</script>
<div>&nbsp;</div>
<a href="javascript:click();">Hello World - Click here!!!!</a>

</BODY>
</HTML>

WēPO is licensed on a per web server / per domain basis.

  • If you are running a single web server with multiple domains, you need separate licensing for each domain.
  • If you are running a single domain across multiple clusters of web servers, you need separate licensing for each server.

We do offer discounts for both of these situations. Give us a call for more exact pricing.

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.

"bang" commands are commands that can be included in a data stream that will change the behavior of Print Wizard in printing a portion of a file. Bang commands are discussed in detail in the Print Wizard manual.

You can split your data into multiple sections to be processed separate from other sections by including bang commands directly in the data stream. As an example, if I wanted to create a PDF of part of a file, fax another part of a file and email another part of a file, I could do this within one print job with bang commands.

!PDF /fmypdf.pdf
Line 1 of data
Line 2 of data
Line 3 of data
!fax /x5036240760
Line 1 to fax
Line 2 to fax
Line 3 to fax
!email /eabc@def.com
Line 1 to email
Line 2 to email
Line 3 to email
 

Print Wizard version 3.0 introduced the concept of Smart Print. With "smart print" turned on, virtually any print file that resides on your PC and has a related file association can be printed.

Print Wizard supports several types of files by their file extension, from text files with a .txt to graphics files with a .JPG extension. However some files only print properly through the applications that support them, such as a .DOC file. With "smart print" on, Print Wizard will try to determine, from the file extension, how best to print a file.

If "smart print" is turned off, Print Wizard itself will try to always print the file it is given.

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.

Print Wizard version 3.0 introduced a new concept of 'print profiles'. Print profiles are settings that will be applied for each subsequent print job that includes that profile as a parameter.

Print profiles include information such as the printer to use, the various printer settings, number of copies to print, whether to print it, fax it, email it, etc. These can all be set up in the user interface by settings things the way you want and then saving your current settings, or by creating a profile from default settings and saving it.

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.

Yes. All of the Print Wizard engine functionality can be run from within a script. With the "/q" command-line switch for quiet-mode, Print Wizard will display no dialogs, but will return error codes. See the Print Wizard manual for a complete list of error codes returned.

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.

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.

It is possible to script all uses of the Print Wizard engine such that the user does not know what is happening.

  • From your own application or user script, you could set up Print Wizard to run multiple times against the same file, simply by preserving the file between runs.
  • You could set a script up that runs Print Wizard once to format a file to a specific type, such as creating a PCL file, then use Print Wizard to reprint it, fax it, email it, etc.
  • From the PWLPD or PWListen program, you could run a script upon receiving the file that would manipulate the file and output it to numerous sources (set up a Custom Program for output).
  • From a Print Wizard print profile, you can define a "By Custom" profile that actually ran a script that runs the Print Wizard engine several times instead of once for the file specified.

There are lots of options here. Call if you have a specific need.

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

This is not as easy as creating a PCL file. A SPL file is created when a print job spools out what is called EMF files to the printer spooler.

First locate the spool directory, usually "\windows\system32\spool\printers". Under Windows NT, it may instead be "\winnt\system32\spool\printers" or "\winnt\SYSTEM\CurrentControlSet\Control\Print\Printers". On some versions you can configure Windows to use a different directory for all printers, or for a specific printer.

To find your PC's general spool directory:

  • Go to the Control Panel
  • Click on "Printers" or "Printers and Faxes"
  • In the File menu, click on "Server Properties"
  • Click on "Advanced"
  • Note what is in "Spool folder".

If in the steps below you fail to find a particular spool file, you may want to check the Windows Registry, under one of the following areas:

  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Printers\DefaultSpoolDirectory
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers\specific printer name\SpoolDirectory

Now capture the SPL file.

  • Open the Control Panel's "Printers" or "Printers and Faxes" applet.
  • Double-click the icon for the printer in question. Ideally, there will be no print jobs showing.
  • From the Printer menu, choose "Pause printing".
  • Print the document you want to capture, on the chosen printer, using whatever Windows software is appropriate. You should see the print job show up in the printer window on your screen.
  • Look in the spooler directory as identified previously. You should find a file with a ".SPL" extension (hopefully only one). Copy this file to some other location on your computer.
  • In the printer's window, cancel the print job.

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.

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.

Print Wizard supports several overlay files. The possible formats are a PWML file, a SPL file, an EMF file, a PCL file or a graphics file (TIFF, JPG, GIF, WMF or BMP).

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.

Overlay files either need to be in the format of a PWML file, a PCL file or a graphics file (TIFF, JPG, GIF, WMF or BMP). The problem with the graphic file formats is they may not appear clean if they were not scanned or created at the proper resolution for the printer, including the proper offsets for margins, etc. This may be a problem if you plan on moving this overlay between specific printers. A better approach is to utilize a PCL file if you can.

Another possibility is laying out the overlay with PWML (Print Wizard Markup Language). This may help you come up with a much cleaner overlay file.

If you do continue to have problems or want some help with PWML, give us a call.

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.

There are two options here.

If the print file has printer-specific escape sequences in the file, Print Wizard will pass this directly to the printer without trying to format or auto-fit any portion of the print job. So you need do nothing in this case.

If the print file contains control sequences and tag printing that Print Wizard does not see as printer-specific codes, you can still print direct to the printer by including the command-line switch to print to the spooler or to print raw:

/vlevel=spooler       or       /vlevel=raw

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.

In the terminal emulation world, such as what is supported with our Anzio products (serial, telnet or SSH), remote printing was most often done by passthrough printing, where the print job would "pass through" the terminal session to the locally attached printer. Host applications often supported this as well as the terminal client.

Other types of printing were also supported by the host application and the host itself, namely printing to a spool or queue on the host for the local printer. The UNIX could also be set to print through the LPR or LP program which could then be redirected to remote printers or remote print servers.

Print Wizard supports three types of printing that works with these approaches, Despool, LPD and Listen.

  • Listen watches for remote print jobs coming in as raw data on port 9100, similar to Hewlett-Packard's ® JetDirect protocol.
  • LPD utilizes the LPR / LPD protocol for capturing print jobs destined for a remote print server.
  • Despool, and the FTPDespool variation, watches for remote jobs posted to a specific location. While Despool watches a locally mounted directory, such as over SMB or NFS, FTPDespool can watch a remote directory over the FTP protocol.

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.

From the Print Wizard user interface, under the Tools menu, you can set up email options as well as the default email method to use. Check mark the default email method that you want as the default.

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

Localhost printing refers to printing through the PC to a local port on the PC as if this PC was a remote printer. Print Wizard supports this by setting up a loop back printer, one that prints out a network port to itself. Refer to our support document on Localhost printing to configure a local printer to do this.

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

Services are programs that "watch" for events to happen. In the case of Print Wizard, this involves watching either for a print job to show up in a specific directory (despooling), or watching for a job to arrive over a network port.

Print Wizard supports two types of services, Foreground Services (previously known as Print Wizard Services) and Windows Services.

  • Foreground Services are those that are run by a specific user, when logged in, watching for print jobs to appear. This does require the user to log in and start the Print Wizard Service. Alternately you could add the service to the Windows Startup folder and it would run in the background whenever the user logged in.
  • Windows Services for Print Wizard are run from the Windows registry whenever the machine is actually booted up (you do not need to log a user in). These services are available for all users and will receive remote print jobs even if there is no user logged in. They normally run as a "Local System" user with very little permissions.

Both services are managed through the Print Wizard user interface. Refer to the Print Wizard manual for more information.

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.

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.

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.

This is an issue that appears ONLY in Server 2003. It is an issue with Anzio Lite v. 16.2, AnzioWin v. 16.2, and Print Wizard v. 3.3. It is a problem with a security feature called DEP. The way our programs do their online registration causes a conflict with this feature in Server 2003. Here's how to solve the problem: 1) Log on with administrative privileges. 2) Go to the Control Panel, System item. 3) Click on the Advanced tab. 4) Under Performance, click Settings. 5) Click on the "Data Execution Prevention" tab. 6) Click on the "Add..." button. 7) Navigate to the program that will be doing the registration. Assuming standard installation locations: For Print Wizard: c:\program files\printwiz30\pwui.exe For Anzio Lite: c:\program files\anzio16\anzio32r.exe For AnzioWin: c:\program files\anzio16\anzio32.exe 8) Click "OK" on everything. 9) Try again to register.

Print Wizard version 4.0 includes all the necessary support for Print Wizard Personal Edition and Print Wizard Service Edition (formerly called Server Edition). When you run Print Wizard as a demo (60-day evaluation), the program assumes you are working on a Service Edition and all options are available to you.

Once you enter a license code for the Personal Edition, Print Wizard Services, Windows Services and a few more features become unavailable. You must have a Service Edition license to utilize these Services and remote retrieval of print jobs.

The basic Print Wizard Personal Edition license is set to support up to 3 output devices (printers, faxers, pdf) that it can print to at any given time. If you have additional needs, contact us for further licensing options.

The Print Wizard Service Edition license supports a specific number of output devices (printers, faxers, pdf) available to the print server, depending on the license you purchase:

  • PW SE 3 -- Support for up to 3 output devices
  • PW SE 6 -- Support for up to 6 output devices
  • PW SE 10 -- Support for up to 10 output devices
  • PW SE -- Support for an unlimited number of output devices

Both Print Wizard Personal Edition and Print Wizard Service Edition are licensed on a per machine basis - one license for each machine. Multiple licenses would be required to run on multiple PCs.