Yahoo Groups archive

Datacolor User to User Support Group.

Index last updated: 2026-04-28 23:18 UTC

Thread

PFP 1.1.1 won't read - problem solved

PFP 1.1.1 won't read - problem solved

2006-07-05 by bill_hansen20012001

Thanks David - see, I knew it would be something dead-simple! The USB 
socket for my Spectro was not wroking (LED was off) so I unplugged the 
Spectro, plugged it in again, and everything worked perfectly. What a 
relief!

The second profile (Epson Premium Luster with GLOP - the first one was 
EPL without GLOP) looks like it will dry down to an 
essentially "perfect" profile - or at most it may need another +1 of 
Brightness. 

Bill Hansen

Re: [colorvision_group] PFP 1.1.1 won't read - problem solved

2006-07-05 by David Miller

>Thanks David - see, I knew it would be something dead-simple! The USB
>socket for my Spectro was not wroking (LED was off) so I unplugged the
>Spectro, plugged it in again, and everything worked perfectly. What a
>relief!

(Same here; that will save some time in trying to figure this one out
further!)

I'm curious, though; is that USB port dead? (Nothing works on it?) Or
was it simply a matter of unplugging and replugging into the same port?

And related: when you ran the 1.1.1 installer, did you unplug the spectro
while the installation was taking place? (The installer instructs you to
do this, but it's also easy sometimes to skip over the instructions and
forget; I've done that before myself).

>The second profile (Epson Premium Luster with GLOP - the first one was
>EPL without GLOP) looks like it will dry down to an
>essentially "perfect" profile - or at most it may need another +1 of
>Brightness.

Glad to hear it!

I think what we'll consider doing in the next release is adding some
text to the UI that specifically states that those controls are disabled
because no spectro is attached. This question has come up before several
times; disabling controls in the UI is appropriate for this, but in those
cases, it appears to be just a little bit too subtle...:-)

Best regards,

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

Re: [colorvision_group] PFP 1.1.1 won't read - problem solved

2006-07-05 by david doughman

Glad to hear you're up and running again

Dave

--- bill_hansen20012001 <b2hansen@...> wrote:
Show quoted textHide quoted text
> Thanks David - see, I knew it would be something
> dead-simple! The USB 
> socket for my Spectro was not wroking (LED was off)
> so I unplugged the 
> Spectro, plugged it in again, and everything worked
> perfectly. What a 
> relief!
> 
> The second profile (Epson Premium Luster with GLOP -
> the first one was 
> EPL without GLOP) looks like it will dry down to an 
> essentially "perfect" profile - or at most it may
> need another +1 of 
> Brightness. 
> 
> Bill Hansen
> 
> 
> 
>

Re: PFP 1.1.1 won't read - problem solved

2006-07-06 by Bill Hansen

David Miller wrote:
���������� is that USB port dead? ....Or was it simply a matter of unplugging and replugging into the same port?

No, the port wasn't actually dead. I have three powered USB hubs, and on two of the three, a socket will occasionally stop working temporarily. Unplugging and replugging has always solved the problem. I should have thought to look at the USB hub, and I didn't.
________________________________________________________________________________________ did you unplug the spectro while the installation was taking place? Yes I did. That's one thing I did correctly.
_________________________________________________________________________________________ I think what we'll consider doing in the next release is adding some text to the UI that specifically states that those controls are disabled because no spectro is attached.

That would have helped me in this case. But really, I should have thought to look at that hub.


Thanks for your help. The sort of feedback one gets from these SIG groups is probably the best thing about the internet.

Bill Hansen

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.