ColorPro Technical Support
III. Error messages
|
III.1 "you don't have the right to use this module"
|
 |
 |
v2.x and 3.x |
You need to delete colorpro.log and the complete binupref
directory located in the WINDOWS directory (PC) or the System's Preferences
folder (Mac) and launch ColorPro to repersonalize (enter passwords again).
|
III.2 "The modules folder is empty"
|
|
|
All versions |
There is a possible mismatch of versions between modules
located in the MODULES directory and the one located in BINUPREF.
This happens mostly after a re-installation.
In order to start from a clean installation, you need to delete all binuscan
related directories in C:\WINDOWS\BINU*.*, then delete the installation
directory and launch a new installation again.
Macintosh users, delete all the binuscan folder and the binupref folder
in the System's Preferences folder, then perform a fresh installation.
|
III.3 "Protection initialization error", or "Dongle not plugged"
|
|
|
All versions |
The dongle (hardware protection key) has to be plugged
into the parallel port (PC), ADB or USB ports (Mac).
On Mac the dongle drivers are installed automatically.
- Windows 3.1x users don't need to install drivers for the dongle.
- Windows 95 & 98 users: in the .\RAINBOW\WIN_95 directory you'll
find a sentw95.exe application. You launch it and go into the "Functions"
pop-up menu to select the "install sentinel driver" item.
At this point a path pointing to the WIN_95 directory is proposed
(E:\RAINBOW\WIN_95 for example).
Now, you click OK and it says: "Driver installed! Restart your system".
- Windows NT: in the .\RAINBOW\WIN_NT directory you need to launch
the setupx86.exe application.
You go into the "Functions" pop-up menu to select the "install sentinel
driver" item.
At this point a path pointing to the I386 directory is proposed (E:\RAINBOW\WIN_NT\I386
for example).
Now, you click OK and it says: "Driver installed! Restart your system".
If you use a 16 bits applicationsuch as, for instance, JobManager
for Quark XPress 3.3x, you'll have to intall the RAINPORT (miniport)
drivers too.
For this, you go into the .\RAINPORT directory and launch setupx86.exe;
you then specify the path (manually) of the driver source files pointing
to the I386 directory (E:\RAINPORT\I386 for example).
You click OK and it says: "Rainport driver files copied successfully".
You click OK again and it finally says: "Driver installed! Restart
your system".
This works (RAINPORT only) if you have at least Service Pack 2 of
NT (because miniport management is bugged in Service Pack 1).
WARNING: on NT, you need to have Administrator rights to install the
RAINBOW and RAINPORT services.
|
III.4 "Can't copy Rainbow\win_*... to c:\windows\system..."
|
|
|
All versions |
Before installing the dongle drivers, the installer gives
a message box that specify to type the appropriate complete path pointing
to your CD drive (include the letter of your logical CD drive).
If the RAINBOW or RAINPORT installer is not able to copy several files
(and you specified the correct path), this means that an incomplete installation
was already on the disk drive.
The problem is that those files are installed with the read only attribute,
and then the new installation of the drivers is not able to apply the
replacement.
To avoid this, you'll have to find all rain*.* AND rani*.* occurences
on your system drive and delete them.
Now, you can safely launch again the installer from the RAINBOW or RAINPORT
directory.
|
III.5 "Cannot find c:\pagefile.sys" with NT Server"
|
| |
|
V. 2.x |
Decreasing (a lot!) the size of this NT swap file can be
a solution - Another solution is to delete this file, but it's not possible
directly from NT.
In that case you need a dual boot (for example Windows 95 and Windows
NT), or to boot from a DOS floppy disk (NT partition must be FAT of course).
This file will be recreated next time without problem anymore.
- Create another partition in which you tell NT to place this swap file
(or make a SUBST command of the two logical drives).
|
III.6 "Impossible to load pcdlib32.dll"
|
| |
|
V. 2.x |
This can occur until version 2.1.
Depending on the system languaged used in Windows 3.1x, the Win32S delivered
on the CD didn't work properly due to some Microsoft bugs.
The workaround is to uninstall Win32S, located in C:\WINDOWS\SYSTEM\WIN32S,
and then get a more recent of Win32S that fixes this problem (version
of Win32S needs to be 1.3 minimum).
|
III.7 "Message file initialization failed","message file is damaged
or corrupted", "Message not found", "Message non trouve", or if messages
seem cryptic"
|
|
|
All versions |
You'll have to find on your drive(s) all the files named
binuscan.mes and replace all these occurences with the biggest one in
size.
Another thing, depending on the version of ColorPro is to copy binuscan.mes
in C:\WINDOWS\BINUPREF or the binupref folder in the System's Preferences
folder.
|
III.8 "The orders will not be processed because ColorPro is not in
extension mode" with JobManager"
|
|
|
V2.x and 3.x |
It may be a synchronization problem.
ColorPro has to be launched first in Xtension mode, then Quark Xpress.
When in Xtension mode, ColorPro creates a temporary file (0 bytes) named
binuexit.
If it is not created, check that the writing of this small file is not
cached.
Another thing is that you can even force the sending of the orders in
clicking "No" when the dialog box asks "do you want to stop?".
|
III.9 "Unable to communicate with the Twain source"
|
| |
|
V3.x |
In version v3.x, the scanning interface (ScanImage) is
a 16 bits application.
You're then autorized to use only 16 bits drivers from ScanImage (or scan
with a 32 bits driver from PhotoShop).
The version of your twain.dll (located in C:\WINDOWS) must be at least
v1.6.
|
III.10 "Can't find defopt.clp"
|
|
|
V3.03 |
This occurs only with version 3.03 of ColorPro.
A simple workaround is to copy the defopt.clp file from the BINUPREF directory
to the BINUPERF directory (both located in C:\WINDOWS or in the System's
Preferences folder)
|
III.11 "Trace.clp file is getting too large, do you want to overwrite
it?"
|
|
|
V2.x and 3.x |
After processing a lot of images ColorPro's trace.clp file
grows.
Then when you restart ColorPro this message occurs.
If you press "Yes", it happens sometimes that this file is not really
deleted...
You then have no other solution than manually deleting the trace.clp and
restart ColorPro.
Don't forget to remove the already processed images from the TODO directory
before restarting ColorPro (otherwise they'll processed again).
|
III.12 "Compression not supported" in BinuCD
|
|
|
All versions |
This happens mostly when changing preferences in the session
or between images to export.
You need to quit and launch again if you change the preferences.
|
III.13 "Not enough space on disk X:\ free XXMb"
|
| |
|
V4.2 |
Due to Windows NT Service Pack 1 compatibility, it is not
possible in this version to process images on a partition greater than
2Gb.
The solution is to make several 2Gb partitions on a high capacity disk
drive.
This size test has been fixed in version 4.2A + 4.21.
|
III.14 "Can not load implib.dll" in MagicScan 4.1 or 4.01"
|
| |
|
V.4.x and 5.x |
When using ColorPro v4.x or 5.x with MagicScan, the IPM
mode of the driver is automatically selected.
UMAX needs IPMLIB.DLL in the WINDOWS directory to perform several operations.
This DLL (provided by binuscan for UMAX) is supposed to be installed by
the installer of MagicScan.
|
III.15 "Full list"
|
| |
|
V4.x and 5.0 |
This means you're using a UMAX scanner with MagicScan 4.x
(IPM mode).
UMAX use a DLL provided by binuscan and which has a limitation in the
quantity of modules to manage.
This works without any problem in the case of PhotoPerfect, but in ColorPro
5.0 all the modules are installed, and this message is displayed in MagicScan
(but in a binuscan window because the driver uses IPMLIB.DLL).
You simply need to go into the MODULES driectory of the \IPM\DATA directory
and delete around 20 modules corresponding to scanners you don't use,
but don't delete the Default, Reco and Generic modules.
|
III.16 "Demo is over"
|
|
|
V2.x minimum |
This means that you have no more credit inside your dongle
to process more images.
The reason could be that you have a limited version, or an NFR version
(Not For Resale), or you didn't send us your old dongle to receive new
passwords for an upgrade version.
If ColorPro or the IPM are able to process images excepted when you use
JobManager then: we delivered by mistake some 2.1 versions in which the
credit of JobManager was limited.
In that case, a floppy is available to fix this problem: an installer
and a password is then given to you to transform your JobManager in a
full version.
For this you need to contact us and give your serial number.
|
III.17 "The size of the elements is too small"
|
|
|
All versions |
This can happen when doing a Standard Calibration.
The reason is that the image file delivered on the floppy for your Professional
version of ColorPro is too small.
You can slightly interpolate in PhotoShop and save it again (on your hard
drive).
Now, you're able to perform a new calibration if you specify this interpolated
image file.
|
III.18 "Smoothing error in channel #..."
|
|
|
All versions |
Many cases can cause that error when doing a Full Calibration.
The best thing is to scan the calibration target (calibrator) at 200 dpi
in order to have an image file of 1Mb.
The scan has to be "raw" (histogram centered with an appropriate gamma
value, no color correction, no sharpen, etc...).
Make sure also that you crop the target correctly (no black borders).
|
III.19 "Error while reading/writing..."
|
|
|
All versions |
This can be a free disk space problem or a disk allocation
problem while reading/writing temporary files.
You should delete ColorPro and binu*.* directories, then run scandisk
before installing the software again.
Mac users, delete all binuscan files, use an Utility program to verify
and defragment your hard disk.
Rebuild the desktop file and perform a fresh installation.
|
III.20 "No scanner found on SCSI bus"
|
|
|
All versions |
This message may be displayed simply because your scanner
is not turned on, or because it is plugged to the USB or FireWire ports.
If you're using a SCSI scanner on PC : this problem occurs on some Ultra-wide
Adaptec SCSI.
It does not affect the operation of the software.
To solve it: - Install the last version for the AHA2940U as well as the
ASPI32 driver from http://www.adaptec.com - In the SCSI BIOS (at boot
up sequence), configure as follow: a) Ultra SCSI -> disabled b) Initiate
sync negotiation -> no c) Enable sync disconnection -> no d) Maximum
transfer rate -> 5Mb
|
III.21 "Invalid password"
|
|
|
V2.x minimum |
binuscan is a dongle-protected software package that requires
two 11-character passwords during the installation (version 2.x) or upgrading
process (versions 3.x, 4.x and 5.x) - these passwords are extended alphanumeric
(ie case sensitive, & including special characters).
The single most common support query on binuscan relates to mistyping
these passwords: normally o O 0 or l I 1 are misread.
The passwords are printed on a label on the outside of the software package
which also shows a sample character set with which you can compare the
characters.
With version 3.xx, passwords are no longer required during the installation
(excepted for upgrades).
Also, check that the serial number of the dongle corresponds to the label
on the packaging - run the program "counterCP" " (or in some versions
" compteurCP " or "serial number") to check the dongle and status (or
in the "About" section of the IPM 5.x).
Distributors can verify users passwords if provided with their serial
number, however this can take up to 24 hours.
|
III.22 "Demo is over"
|
|
|
All versions |
Demonstration/Evaluation copies of ColorPro are fully-functional
and documented as a normal version - however, the total number of images
that can be processed is limited to typically 50 or 100 (and more for
NFR versions).
The image count is stored in the hardware protection dongle along with
the Serial Number.
Evaluation versions are normally not sold to end-users.
Upgrade versions are limited (30 or 50 images) until the old dongle (from
the upgraded version) is returned to the reseller, or to BINUSCAN ; new
passwords are then faxed for unlimited use.
To check the status of your copy, run the "Serial Number" (or in some
versions "CounterCP", "compteurCP", or go in the "About" section of the
IPM 5.x) application which is in the same folder as the ColorPro application
- this will show the dongle serial number, the image counter or details
of the options that are installed (in some versions, Job Manager and B&W
were chargeable options).
If you have purchased a full edition of ColorPro and the dongle is image
count limited (or Demo is over), contact Technical Support immediately
(proof of purchase may be required).
Demo versions can be upgraded to full versions by reinitializing with
a new set of passwords that can normally be provided within 24 hours.
|
III.23 "Incorrect file type"
|
|
|
All versions |
- Input
binuscan can process (8 bit) grayscale and RGB 24-bit to 48-bit (color)
files in the following formats:
- TIFF (Tagged Interchange File Format)
- TIFF LZW (some earlier versions do not support LZW)
- TIFF Kodak* (with add-on Library, excepted for DCS 315)
- TGA (Targa) JPEG EPS (Encapsulated PostScript)
- EPS JPEG (aka binary JPEG)
- DCS (Desktop Color Separation)
- DCS JPEG DCS2 DCS2 JPEG YCC (Kodak Photo CD)
binuscan IPM does not process 2-bit (lineart) images.
If an image in the TO DO folder is not processed, check that the image
has not already been processed, check the file type and try re-saving
the file using a current version of Adobe Photoshop.
Be careful not to try to process images in the Photoshop file format.
- Output
binuscan ColorPro 5.02 supports the following file formats (8-bit
grayscale, 24-bit RGB and 32-bit CMYK):
TIFF TGA JPEG EPS EPS JPEG DCS DCS JPEG DCS2 DCS2 JPEG
|
III.24 "Out of memory/Not enough memory" in V5.x"
|
| |
|
V5.x |
This happens on PC with a very large amount of memory,
and the IPM won't launch.
This problem can be solved by editing preffile.txt in .\IPM\Data and reducing
the percentage of allocated memory (suggested settings: 50% for 256Mb,
40% for 384Mb, 30% for 512Mb, etc...).
|
III.25 "Unsupported scanner"
|
|
|
All versions |
This error occurs if the dongle cannot be detected by the
IPM or if the wrong dongle is plugged for the current software.
Otherwise, this simply means (in PhotoPerfect) the input image comes from
a scanner not supported in this version of the software.
Last updated April 28, 2000 |
