ColorPro Technical Support

IV. Tips and tricks

IV.1 Adding new modules directly in the modules directory
v2.x and 3.x
This means you added modules that didn't came with the default installation. The first step is to trash them from the Modules directory and from the \WINDOWS\BINUP??? Directory (binupref in System's Preferences, on Mac). ColorPro can manage 9 extra modules in colors: custom1.bfc custom2.bfc ... custom9.bfc and 9 extra modules in B&W: custom1.bfn ... custom9.bfn (Mac users, use Custom1, Custom2, Custom3·). To add a new module coming from someone else, you need first to rename it into custom.... For example, rename own#mod.bfc into custom1.bfc, then copy it into the Modules directory. Then, you delete colorpro.log and the complete binupref directory located in the WINDOWS directory and launch ColorPro to re-personalize (enter passwords again). Now you select this custom1.bfc module in the options window; at the top of the list of modules you only have to select the Rename option and type own#mod.bfc. Your new module is now visible in ColorPro with the appropriate name.

IV.2 Adding new modules directly in the modules directory
v4.x and 5.x
After copying the new modules in the MODULES directory of the IPM, you need to launch ipm.exe (binuscan IPM, in the IPM folder) first.

IV.3 Can not open binuscan CMYK EPS V3.x with Photoshop 4.0 (white image)
All versions
PhotoShop 4.0 includes a new plug-in called EPS Parser. To enable PhotoShop 4.0 to read any EPS files, you simply need to remove this EPS Parser from the Parser directory. This PhotoShop bug has been fixed in version 4.01 of PhotoShop. Here is a workaround if you want to keep the EPS parser: - Select Open from the File Menu - Check the "Select all files" box in the File Open dialogue box - Select an EPS file - In the Format pop-up menu, select "PhotoShop EPS" instead of "Generic EPS" - The file opens normally To display an accurate preview, you still have to proceed the same way as before but selecting "EPS TIFF preview" in the Format pop-up menu.

IV.4 Can not open binuscan DCS CMYK V4.x with Photoshop 5.0
All versions prior to 5.0
This PhotoShop bug has been fixed in version 5.02 of PhotoShop and also in version 5.0 of ColorPro. Otherwise, the only workaround is to use a version 4.x of PhotoShop, or to work in two steps: if the image is opened and saved in PhotoShop before binuscan's separation, then the DCS can be opened by PhotoShop (because PhotoShop reads only its Image Resource Block to open DCS files, i.e. bug...).

IV.5 Impossible to process Kodak Photo CD images
v.2.2
The modfam.txt file delivered with this version includes an unexpected character that prevent any attempt to process a Photo CD image. This has been fixed with an extra floppy disk which contains the new modfam.txt to replace.

IV.6 Running several copies of ColorPro on the same machine
v2.x and 3.x
To run two copies of ColorPro you copy the ColorPro application in another directory with defopt.clp + binuscan.mes + colorpro.pco. The last file should be found in C:\WINDOWS\BINUPREF (binupref folder In the System's Preferences folder). The first time the copy is launched, it has the same options than the original application. You then change the options you want and they will be updated looking first if defopt.clp and colorpro.pco are to be found at the same level than ColorPro.

IV.7 Opening and displaying images with ColorCorrect
V5.x
ColorCorrect can handle only binuscan's CMYK EPS and grey files as follows: - CMYK EPS 1 file - CMYK DCS 5 files - GREY TIFF - GREY JPEG

IV.8 Using Kodak Photo CD Access 2.05
v.2.2
You need to launch PCDVIEW.EXE (Kodak Photo CD Access) in order to work with Kodak Photo CD. Then you load the contact sheet to edit one image for example. Now, you go in the "Transforms" menu and select the "binulut" item. Finally you select a cropping area in your image and export it in TIFF format into the TODO directory of ColorPro (don't forget to specify a name and a resolution).

IV.9 How to get the serial number of the dongle (protection Key)
All versions
The dongle needs to be plugged in the parallel port of the PC, ADB or USB ports of the Mac. If you have version 2.x or 3.x you'll have to find inside your installation directory (mostly inside COLORPRO or DATA) for files named "compt*.exe" or "count*.exe". (counterPC or compteurCP on Mac). If you have version 4.x or 5.x you'll find "serial number.exe" (Serial Number on Mac), localized to your language, installed in a IPM\DATA or REGISTRATION directory.

IV.10 Installing or Upgrading a new version
All versions
You simply need to delete the complete installation directory. Keep a copy of the modules and 3D tables you have modified and/or created before this. Now you delete the BINU*.* directories in the WINDOWS directory (binupref folder in System's Preferences folder), and proceed with the new installation.

IV.11 Possible Xtensions conflicting with JobManager
All versions
Azalea Prepress Extension 1.5.5

IV.12 Mac partition is mounting instead of PC partition
v5.x
This may happen if you use a special utility like "Mac Opener" from Dataviz which seems to mount the Mac partition if it is the first session on the CD. You need to disable the utility before placing the binuscan CD in the drive.

IV.13 Creating a module for an unsupported scanner
All versions
binuscan's engineers continually produce and revise correction profiles (called "modules") for scanner models from most manufacturers, releasing them between major software versions. If your scanner or digital camera is not listed, it is still normally possible to achieve excellent results by creating a new Module. ColorPro Modules rely on processing a RAW scan - that is a scan that had NOT been processed by any driver that performs autobalance, autorange or sharpen adjustments. The scanner or camera software driver must be able to produce wholly consistent scans without altering the raw CCD data. All binuscan Modules include advices on the specific scanner software settings to use to achieve this. Users of binuscan ColorPro Professional ToolKit can create more accurate Modules for new scanners by using the included color targets to produce RGB calibration curves or 3D Tables. These curves, applied to correct for color casts before the correction process, are also applied by many of the default ColorPro Modules. However, they can only be viewed or edited with binuscan ColorPro Professional. NB: Some Correction Modules are specific to scanner's current firmware and software versions, which can have significant affects on the properties of "raw" scans.

IV.14 Trace files
All versions
ColorPro maintains a history of recent filenames processed from the input folders (.\PM\Data\Trace.dat). This prevents files from being reprocessed accidentally (for example after restarting). If you use the same file name twice in the current or consecutive sessions ColorPro will not recognise it and will remain in "Waiting" mode (same name and same date+time). To delete the history, simply trash the trace.dat files between sessions.

IV.15 Upgrading existing copies of ColorPro
All versions
Upgrading, reinstalling or reinitialising ColorPro may overwrite any custom settings within the correction modules, tables and preferences. We recommend the following procedure when upgrading or reinstalling ColorPro: Indentify any new or modified modules within the Modules folder (this is usually at this location: .\IPM\Data\Modules (don't forget the associated 3D Tables in .\Modules\Cor_data). Keep a copy.
  1. Identify any new or modified Table, Screen, etc... Keep a copy.
  2. From the WINDOWS folder, delete the BINU*.* folders (binu* folders in the System's Preferences folder).
Installing a new copy:

Install a new copy of ColorPro from the CD-ROM.
  1. Copy back your Modules, Tables, Screens to the appropriate locations.
  2. Now, run the IPM first.
Reinitialising:
  1. Delete the BINU*.* folders from the WINDOWS folder.
  2. Delete all the *.txt files in .\IPM\Data.
  3. Now, run the IPM first (it recreates the TXT files).

IV.16 Adobe InDesign 1.5 and binuscan DCS files
All versions

Problem description:

InDesign does not print binuscan DCS and DCS2 files on proofers and digital printers, but it will print the images if you open and resave them in Adobe Photoshop.
Note: Printing separations (on an imagesetter or platesetter) works perfectly. Only composite prints are a problem.

Solution:

  1. Launch binuscan ColorPro and select the "Action menu/Preferences/Output File Options..."
  2. In the CMYK tab, if DCS or DCS2 is selected, click on the "Edit" button.
  3. The Output File Options window is displayed with 5 tabs: Preview, Jpeg, Screens, Printer and Level.
  4. To print a composite version of your images on a grayscale printer:
    Click on the "Printer" tab and select "BW Composite". You can then adjust the resolution of this composite segment.
  5. To print a composite version on a color printer or proofer:
    Click on the "Printer" tab and select "Color Composite". You can then adjust the resolution of this composite file.
  6. You can also choose a printer profile.
    Default means that binuscan will create a composite with the same separation table as for the high-res CMYK plates.
  7. Click on the "Level" tab to specify your printer's RIP PostScript level.
    - Level 1 will add a composite file in the Master file (preview file) without compression.
    - Level 2 will compress this file JPEG (no visible loss and smaller file but only compatible with true Level 2 or 3 RIPs).

Explanation:

    Like QuarkXPress, InDesign will try to find a composite in the DCS master file when printing in composite mode (to a color printer or proofer). But unlike QuarkXPress, it will not print the preview file if no composite is available.
    Photoshop includes a composite in DCS files by default. However, if none is included, images will not print in composite mode either.
    binuscan has been allowing you to change the resolution and color matching table of this composite file for years. binuscan DCS default output file format does not include a composite since it takes more time to write the CMYK file and not everybody requires it.

Products > ColorPro > Support > Tips n' Tricks