Loading content, please wait ...

Zeepe 8



Free deployment



Security Manager




Contact support

MeadCo's Products

Zeepe 8.0


About MeadCo

About MeadCo

Privacy policy

Contact us

Download the Zeepe SDK

The Zeepe 8.0.3 SDK contains the redistributable Zeepe framework, the Zeepe Programmers' Guide compiled as an .exe using the Zeepe Application Packager (also included) and sources to various samples and utility code.

If you have downloaded a previous version of the SDK, please note the latest SDK will not overwrite previous versions; the latest SDK is installed in its own directory. To remove any old SDK, please use Control Panel|Add/Remove Programs.

The current version of the Zeepe framework is 8,0,3,4.

If you would like to register with us and receive notifications of updates, please complete the following form - you will receive an email upon succesful registration with details on where to obtain the SDK.

Alternatively, you may directly download Zeepe SDK 8,0,3,4


We provide a number of routes for support of the Zeepe framework and welcome feedback with your thoughts or wishes for improvement. As can be seen below, Zeepe is actively developed in response to customer requests.


We continually strive to improve Zeepe as a result of feedback from our customers:

Hotfixes (stable)

Hotfix releases are stable and preferred to the latest release version. All hot fix releases contain all prior hotfixes and are periodically re-packaged as the latest release version.

There are no hot fix versions available.

Release Versions (stable)
(15 October 2013)

Zeepe 8 is compatible with IE 9+ and is a more streamlined install. ScriptX has been removed from the main download and is now available as a separate install.

  • Aligned with ScriptX 7.3.0.
  • Issues with IE11.
(17 April 2013)

Zeepe 8 is compatible with IE 9 and IE10 and is a more streamlined install. ScriptX has been removed from the main download and is now available as a separate install.

  • Aligned with ScriptX
  • SDK Documentation app not working well with IE 10.
(30 November 2012)
  • Aligned with ScriptX
  • Resolved issues with SxS and Zeepe 7.
(24 October 2011)

Zeepe 8 is compatible with IE 9 and IE10 and is a more streamlined install. ScriptX has been removed from the main download and is now available as a separate install.

  • Zeepe 8 can side by side install with Zeepe 7.
(04 June 2009)

In addition to fixes for a number of issues, this release introduces the ability to send bytes directly to a printer allowing printing to devices such as label printers, Enterprise+ licensing, support for IE8 final and support for Windows 2000 and later only.

Zeepe 7.2.7 and later no longer support Windows 9x/NT.

ScriptX 7 is deprecated. The full power and control is now provided by the zeepe:printing element.

  • IE 8, ability to specify the font to use for page headers and footers.
  • Enterprise+ licensing providing licensing based on computer domain name. Requires Windows 2000 or later.
  • The rawPrinting object provides the ability to send bytes directly to a printer allowing printing to devices such as label printers.
  • Various fixes for compatibility with IE8 Final.
  • layered shadow and background windows not being created in the correct z-ordering in some circumstances on Vista/Windows 7.
  • On Vista/Windows 7 window.close() failed to close the window when the process was created by another zeepe application.
  • Accomodate very long default user agent string.
  • Crash when using ShowHtmlDialog() with some forms of user agent string.
  • Erroneous border when using the MaxiPT template.
  • Pages using <iframe > generate a (caught) exception which interrupts execution flow.
  • Edge case licenses unable to validate properly on Vista.
  • Print scaling could not be used with printHtml().
  • With IE 7 or later, if Page Setup is used within print preview, scripted configuration of the printer is lost.
  • Vertical rebar not sizing correctly in standards mode.
  • Margin changes from dragging in print preview are persisted in the session (but as with scripted changes, lost when the document is closed).
  • Security Manager fallback support for latest certificate.
  • On Vista refreshes IE broker policies after install.
(23 April 2007)

This release is fully compatible with Vista and IE 7.

A number of other problems have been resolved - the SDK documentation has the details.

  • The Microsoft <HTA:Application /> element from Microsoft HTML Application files (.hta) is supported. The element is supported to provide simple compatibility with HTA files; a file can simply be renamed and run. With just the addition of a suitable license, an HTA application can be run directly from a web site.
  • New window style attributes have been added; border, borderStyle, innerBorder, sysmenu, scroll, scrollflat, selection and windowstate.
  • Within the Zeepe host, when a <zeepe:window/> element is present and Zeepe Application permission, both window.showModalDialog() and window.showModelessDialog() are implemented by Zeepe to provide dialogs without security adornments such as url bars and status bars. For modal dialogs, there is no difference between zpmObject.ShowHTMLDialog() and window.showModalDialog().
  • Combined security mode (_hostFlags attribute value 64) of the Zeepe:browser element has been improved to include the outer host license is automatically inherited if the content displayed is covered by the license (e.g. same domain).
  • As for the Zeepe host window, the zeepe: namespace is declared to the Zeepe:browser element so that license, window and printing elements can be used without requiring a namespace implementation declaration (as is required in IE).
  • When running with the IE 7 components installed, Zeepe printing defaults to using a print template with the same features as the IE 7 template - in particular enhanced print preview and automatic scale to fit printing.
  • An IE 7 style template can be specified when IE 5.5 or later components are installed.
  • A frame can be previewed - does not require MaxiPT.
  • SetPreviewZoom() added to provide control over the zoom factor used on print preview.
  • SetPrintScale() added to provide control over the scaling used when printing - IE 7 style template only.
  • Windows Vista 'Per-user' installs
(02 June 2006)

This release fixes a number of problems that have arisen with the 7.2.4 release and adds a new event - the SDK documentation has the details.

This release is required in order to resolve problems with accepting new licenses.

(21 April 2006)

This release is compatible with Microsoft Windows Update KB912812. When this update is installed, previous releases of the Zeepe framework will not be able to use the zeepe:browser element. This release is also compatible with Internet Explorer 7 Beta and Vista CTP February 2006.

A number of other problems have been resolved - the SDK documentation has the details.

  • Enhanced print templates as to be available with Internet Explorer 7 are available in this release - but for all Internet Explorer versions since, and including, 5.5.
  • Preview of frames (in previous versions this required MaxiPT).
  • Due to changes in Vista, the MeadCo Setup control is now deprecated. An Internet Component Download .cab is provided for installation of the framework but the recommended installation is through download and run of the Windows Installer file (zeepe.msi) or similar installer developed with the merge modules.
(25 November 2005)

A number of problems have been resolved - the SDK documentation has the details.

  • A number of new convenience properties and methods have been added for simpler scripting of the host frame window.
  • New properties unsecuredDataTransfer and unsecuredClipboard provide enhanced access to dag'n'drop and clipboard data - these properties require a license.
  • A number of new features have been added to improve consistency of behaviour across OS versions along with additional control. The SDK documentation has the details.
(24 June 2005)

Zeepe 7.2.2 brings first class HTML Widgets to the Windows platform; with Zeepe 7.2.2 great looking cool apps and widgets are possible.

Widgets can be delivered over the Internet, no need for users to download and install each one.

(06 June 2005)
  • A number of new events have been added to the Zeepe window controller - these events provide information on system changes such as the display (size, colour depth and theme), power management and system shutdown.
  • Quit() support added to <zeepe:browser /> element and fires the onbeforeunload event. If the current document requests an option to stop the quit through a onbeforeunload handler and the user does cancel then an error is thrown - this should be caught and the browser not closed.
  • The new attribute application on the <ICON> element of a <WINDOW> style definition specifies, when its value is "true", that the icon should be used for all subsequent Zeepe host windows created in the application. (Default value is false).
  • The framework defines the pluggable protocol runzeepe: to enable launching of Zeepe applications from within either the Internet Explorer or Firefox browsers. Alternative protocols may now be defined.
  • The printerControl property of the zeepe print object returns an object providing extensive information about, and control of, a printer.
  • The SDK contains an extended application stub (zapfstubex.exe) for the packaging of applications that may be used in place of the simple stub - with the extended stub it itself provides the custom host windows rather than the standard installation (zeepe711.exe) and therefore download windows, error boxes etc, grouped taskbar tabs etc all use the icon and description from the application. The extended stub may also be used by OEM installers to provide complete branding - in such cases they should implement their own pluggable protocol as described above.
  • If the registry key HKEY_LOCAL_MACHINE/Software/MeadCo/Zeepe/MiniDump is a DWORD with a non-zero value then a crash mini-dump is created in the event of a crash in the Zeepe host application. Please return the mini-dump to MeadCo to help us determine the cause of the crash.
  • The window.external.TraceDebug(string) method will output the given string to the Win32 API OutputDebugString(). Such output can be collected by applications such as DebugView.
(06 February 2005)
  • The menu object, the <menu> element within a zeepe:menubar element has gained new methods InsertItem() and RemoveAll().
  • The <menuitem> element has a new attribute default.
  • The zeepe:notifyicon element provides complete coverage of the functionality available from the Win32 API Shell_NotifyIcon() allowing creation of an icon in the taskbar status area with tooltip, balloon tooltips, context menus, updatable icon etc etc.
  • The singleInstance attribute of the UI definition for a window style specifies that only a single instance of the application owning the window should be allowed. If another instance of the Zeepe application is started, the previous instance is bought to the front.
  • Zeepe now provides its own compressed file format and access protocol (mc-zapf:) to replace the use of MS HTML Help format files (Zeepe publications, .zpx).
  • The command line used to start the Zeepe host is available as the commandLine property of the customBrowser object.
  • The snaptoedge attribute of the UI definition for a window style specifies that the window should snap to the desktop/monitor edge when the window moves to within the specified distance from an edge.
(07 June 2004)
  • When running under Windows XP SP2 full security as for Internet Explorer is enabled, e.g. Local Machine Lockdown. These features are disabled in the presence of a suitable license conferring Zeepe Application permission. Note that since Zeepe Application permission is provided by default for content opened from the local hard disk (i.e. double click a zpa file) then Local Machine Lockdown does not apply - however it does apply to content loaded from the local disk and displayed in a zeepe:browser element.
  • When running under Windows XP SP2 pop-window control is entirely in the hands of the author - implement a handler for the NewWindow3 event in order to disallow pop-ups (by default they will be allowed).
  • Navigations within Zeepe do not update browser history. Due to problems within the IE components supplied with Windows Server 2003, this feature will cause Zeepe to crash. When running on Windows Server 2003 set HKEY_LOCAL_MACHINE\Software\MeadCo\Zeepe\History (DWORD) value to non zero.
  • An additional value has been added to the _hostFlags attribute for the zeepe:browser element to provide control of Pop-up blocking behaviour.
  • The SDK includes the re-distributable components and Wix based scripts for creation of a Windows Installer script (msi). The scripts provide for generating the required registry entries for 'branding' by OEMS or within an organisation of Zeepe and displayed dialogs.
(12 March 2004)
  • Sends a user agent string including "Zeepe 7.1" - this is embedded within the usual IE user-agent string. This can be used by server side code to customise output. Note: the zeepe:browser web browser control to continues to send the standard IE user agent string.
  • Calls to window.close() by documents displayed within the Zeepe Frame Window closes the window without the IE query (i.e. acts as HTA).
  • A number of features have been added to the Zeepe Window controller - the SDK has details
  • Multiple menubars could not be displayed within a single window. Within Zeepe 7.1 multiple menubars can be declared (for example within zeepe:rebar elements) but only a single menubar can be active at any time. The <zeepe:menubar> element has a new property active, which defaults to true. Declare as false for all menubars other than the first to be displayed and flip the property value as approriate to deactivate/activate menubars.
  • The LoadMenu() method will now replace a menu. To declare a complete menu, a top level element must be declared in the passed XML.
  • The Zeepe Window Controller method ShowHTMLDialog() now supports cascading dialogs. The dialog shown by ShowHTMLDialog() does not support the use of the Zeepe User Interface elements or the Zeepe Window Controller but does support the method ShowHTMLDialog() on the DHTML window.external object.
  • A method MessageBox() is provided on the DHTML window.external object, this method provides extended alert style dialogs.
  • MaxiPT is a set of custom print templates that provide advanced control of the printing process including the ability to preview individual frames and provide page headers/footers that include HTML. To declare MaxiPT on a document within Zeepe, use <zeepe:maxipt id="maxipt" />.