Digital BW, The Print

For: (very bad mood) Bob Frost:

> I agree that ImagePrint 5.6 is easy to install. My problem is that it 
> simply
> doesn't work properly after it is installed! ....
> But after two days of trying to get it to print a B&W grayscale image, 
> I
> have one print that is a complete reversal - i.e. a negative

That sounds like a mismatch between the inkset type and profile type.


>  - and I've had
> to reboot the computer more times than I used to with Win 3.1 in 
> several
> years. With Win XP Pro I had almost forgotten what rebooting was - 
> until I
> ran this program. It is mindboggling that they haven't yet got round
> (version 5.6!!) to combining the different bits that are installed 
> into one
> program that works. Why should I have to run a separate program 
> IpInstall to
> install a printer, IpManage to change this, and SpoolFace to try and 
> get rid
> of the files that it won't print.

Can't help you with that. All I can say is that it's very simple to 
switch between the the installation modules (IP Install and IP Manage) 
and between the two operational modules (ImagePrint and SpoolFace).


> Despite reading the full manual, your
> instructions, and some other instructions, and trying installing the 
> printer
> to a specific port, or piggy-backing it off the existing Epson driver, 
> it
> still doesn't work. It usually says it can't get the machine 
> identification.

It sounds like you're doing something systematically wrong in 
installing the program. The best guide to this is the QuickStart 
manual, which I presume that you've read although you don't mention it. 
It has step-by-step instructions that are fool-proof unless you try to 
use a different printer name rather than just selecting from the menu. 
If you are following the QuickStart instruction you shouldn't have to 
worry about specific printer ports or piggy-backing off the Epson 
driver. You might do a search on the IP Yahoo Group 
(http://groups.yahoo.com/group/ImagePrint/messages/) where I remember 
someone having a similar problem -- and it turned out he was doing 
something very wrong and not following the installation instructions.

--Mitch/Paris