Datacolor User to User Support Group.

> >
>> Are you running the latest (2.0) version of PrintFIX PRO?
>>
>> If not: download the PFP 2.0 installer from the ColorVision web
>site.
>> Uninstall the previous (1.x) version, with the spectro unplugged;
>install
>> the 2.0 version; try again; see if that clears it up.
>>
>> If not (PFP 2.0 is installed, and you're still having this problem):
>> email me off-list at davem@..., and I'll direct you to a
>> debug version that we can use to pin this down exactly.
>>
>> Best regards,
>>
>>
>>
>> --
>> David Miller
>> Senior Software Developer, Digital Color Solutions
>> ColorVision
>
>David this is fast, very fast. Are you also working on saturday's or
>is this your normal weekend early morning shift?

Weekend? What is that word, "weekend"? :-)

Answering questions, 365 days a year (whatever time it happens to be) is normal
for me. I'm not going to work on actual -code- all of those days, however.

(I feel much better for having said that, otherwise, I'd be working too hard).

>Greatings from
>Holland where it is 9:30 PM.

Here in New York, it's mid-afternoon...:-)

>This is why I bought Colorvision
>Printfix pro. I was reading this forum befor and also have
>experiences with eye 1 for my monitor. Although faster than yours,
>service is lousy and no documentation!!

We like the kind of support we're able to provide; we think it adds a great
deal of value to the total package.

>Extra info
>Reading through the other error messages in this group I reinstalled
>the software, after dowloding from the Colorvision site and the
>problem was gone. Could make the profile from the previous read
>target. Thanks the data folder was not touched by the uninstall of
>the app.

(Correct, the Uninstall only deletes things that it installed, so the data
files you created should always stay in place, since they're not part of
the original installation)

>Still are curious what might happened with PrintFix pro 2.o version
>1.65

Not sure; I haven't heard of anyone else having that problem. From the
error code you gave, it would have been failing in the main part of the
application, when it was doing basic initialization and starting up. Another
thing I could have suggested would have been to delete preferences, in
case something had gotten corrupted somehow. (PFP doesn't use the abominable
Windows registry for storing preference values, they get stored, nice and safe,
in our own prefs file so that they have no potential to interfere with the
rest of your system). For future reference: you can clear out prefs, and
start over fresh, by holding down the Shift key as soon as you see the splash
screen. Keep holding it until the splash screen disappears.

>Some question I have after making some profiles:
>1-	Why not printing the comments on the target sheet as well?

Good question; that's on the list of possible things to add in a future
update.

>2-	Why not include the DPI of the printed target. Instead off
>the message " 150 Patch target" I can see that without reading it.

PFP itself doesn't have any access to the various driver settings and controls
that you use to setup the target print. The reason we have you type some
basic information into that early UI screen is so that we can nicely format
and print it below the target, but there's no easy way to pull that information
out of the low level driver itself.

We would have to ask you for the DPI you were printing at; you would have
to type it in; then we could print it below the target; but you could just
as easily include this information in one of the other text strings that
you type, and it will be printed for you. I'd suggest just including the
DPI in one of the text fields that you enter information into. (There's
nothing special about these fields in that early PFP UI screen; we don't
do anything with the text that you type, other than print it beneath the
target squares, so no matter what you type, it's not going to cause problems
with the profiling process, and every profile you build from a measurement
set will be the same, whether you type anything into those fields, or not).

You can also write anything you like on the targets, by hand, as you print
them...:-) (Just don't write on the color patches!)


>3-	Why can't you copy and past in the " save template box? Would
>be very convenient!

That was added towards the end of PFP 2.0 development, when time was starting
to run short. (We wanted to release without further delay). We will probably
do some additional work on that as time goes on.

>4-	Same for Save Measurements to box. And infect for every box
>used.

(adding this to the list of minor things-to-do, next version)...:-)

>5-	When profiled, the profile goes into the Color directory off
>the system. For dummies this is excellent. But for people who invest
>in Profiling equipment perhaps not. Why not having a directory , to
>set up in the preferences, where the profiles are stored? This is
>much more convenient when you profile for others and for yourself.

Most/all people will want the just-built profile to go into the proper
color directory, so it's immediately available to color-management aware
applications on their system, so that's the "right" place to build the
profiles into.

In PFP 2.0, we added a set of commands to the File menu to make it easier
to get to some of those special folders. Use the "Open Profiles" command
to have PFP immediately dig it's way into the buried Windows etc etc etc
spool folder and you'll see all of your profiles immediately. You can do
this, and then just copy to an additional location, if you need to.

Best regards,

-- 
David Miller
Senior Software Developer, Digital Color Solutions
ColorVision