Fiery Production Solutions
EFI MicroPress 8.3
Frequently Asked Questions
How many engines does MicroPress support?
- The number of engines supported depends on the MicroPress® model. Color connectivity requires more resources than black and white. For a supported options matrix, please see the MicroPress Datasheet.
Is a Fiery controller the same as a PrintLink?
- No, a PrintLink is a controller that allows MicroPress to connect to the engine. The PrintLink could be a Fiery® controller or a specialized piece of hardware. Once a Fiery controller is dedicated to be a PrintLink, it no longer functions as a separate and independent controller.
Does MicroPress require a Fiery controller to act as the PrintLink for each print engine?
- This situation depends on the connectivity kit. For those print engines that use Fiery technology as a controller, MicroPress requires a Fiery controller to act as the PrintLink. To be sure, check your connectivity kit and the MicroPress supported printers list for guidance.
Can I print files directly to the printers, bypassing MicroPress, and use the full Fiery controller on the printer?
- No, this is not a supported configuration. The PrintLink must have a direct connection to the MicroPress workflow. This means that the PrintLink/Fiery controller is on a private network behind the MicroPress workflow, and cannot be accessed by general network users. If you choose to bypass MicroPress and directly connect to the Fiery controller, it may impact the printers’ performance.
What is included in the connectivity kit?
- The connectivity kit content might be different for each print engine. For most kits, you will get a license for a single connection on the supported engine, a set-up guide, Ethernet cable and, in some cases, a PrintLink. Please see your OEM pricelist for details.
Why does MicroPress need two network interface cards?
- MicroPress is designed to connect to the print devices on an isolated network. This requires you to install multiple network cards on the MicroPress server. One card is used for the LAN and the other for the print devices. You may need a third network card if you have both black-and-white and color printers connected to the MicroPress workflow. To ensure MicroPress operates print devices as intended, you cannot run other traffic on the same network as the print device.
Can I order a CD/DVD of MicroPress 8.3?
- Yes. You can order MicroPress DVDs through your dealer.
Is MicroPress available for all countries?
- The software for MicroPress Solo, Plus and Max is available in French, German, Spanish and Dutch.
Does MicroPress support Windows 7?
- As of the MP 184.108.40.206 release (Nov ’09), we officially support MicroPress Print Drivers (PPD) for client systems running the Windows 7 operating system. Support for Windows 7 on MicroPress Servers is currently available with MicroPress 8.3 in the Solo, Plus and Max configurations. EFI included a copy of a Windows 7 OS license if you purchased MicroPress v8.2 after April 2011. Tech Support can provide detailed instructions on how to upgrade your system to Windows 7 and then restore MicroPress. If you bought MicroPRess v8.2 before April 2011, you may not have received a Windows 7 OS license and will need to purchase the Windows7/MicroPress recovery DVD kit from Tech Support.
When will 8.3 be available for download from EFI Technical Support for existing 8.X customers?
- MicroPress software is not available by download. You can get the latest software on DVD from your dealer.
Is the MicroPress 8.3 upgrade available for existing MP7.XX customers?
- No, there is no upgrade available for MicroPress 7.X.
Can I upgrade from MicroPress Solo to MicroPress Plus?
- Yes. If you have the Solo version, you can upgrade to MicroPress Plus. This upgrade includes a license enabler. Customers can only order one upgrade per server, and the upgrade requires a Dell 960 server.
Do I need a new keycode for MicroPress 8.3?
- No, you do not need a new keycode if you already are on any MicroPress 8.0 version. However, if you received MicroPress 8.3 when you bought a new connectivity kit, you will need a new keycode for the connectivity kit.
Where can I find documentation on MicroPress?
- MicroPress documentation is installed on the server in the following location: C:\Micropress\Documentation\PDF
Is spot color management offered in MicroPress 8.3?
- Yes it is. We support CMYK substitution using Fiery) Spot-On™.
What native file formats are compatible with the MicroPress workflow?
- MicroPress supports .ps, .tiff, .pdf, .xps, jpeg, .gif.
Can MicroPress handle PCL files?
- Yes, your MicroPress uses a tool called TruePCL to handle PCL data. This is standard on MicroPress Max and Max Enterprise and can be purchased as an option on Solo and Plus.
Can I access jobs remotely from MicroPress?
- Yes, you can access and edit jobs remotely using Remote TrueEdit. Available on MicroPress Plus or higher, it has the same system requirements as the MicroPress Solo/Plus.
Do I need a training guide or manual to use or program MicroScript?
- MicroScript uses an intuitive interface that allows you to easily create scripts using a drag-and-drop method. So you really don’t need a manual to get started. However, a manual is available and installed on the MicroPress server as C:\MicroPress\Documentation\PDF\MicroScriptUserGuide.pdf.
With the MicroScript, can you type in your code instead of using the GUI?
- Yes, you can create and edit scripts in the “Code View” using Visual Basic and API commands or in the “Design View” by adding blocks to handle the job attributes and layout. You can easily switch between views within MicroScript.
Can I increase functionality by moving jobs from one engine type to another in PrintStation Manager?
- All jobs in the PrintStation Manager are in “raster format” for the type of color or black and white PrintStation(s) managed by the Virtual Engine. Because of this set up, you can only manage printers with the same connectivity type with a Virtual Engine during workflow configuration. PrintStation Manager can map job attributes such as, duplex, staple, punch and others when moving files between Virtual Engines, which manage similar PrintStation types that can print the same raster image.