Yahoo Groups archive

Datacolor User to User Support Group.

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

Message

Re: Are Datacolor Spyders any good?

2010-09-08 by jjmalcolm2004

Had to look up what a "shill" was. What an interesting concept. A 'plant" to encourage a gullible crowd to buy a product - often employed by con-men, according to Wikipaedia. I am sure that's  not what was meant since others were suggesting that I was undertaking a naive attack. 

However, I WAS merely an ordinary customer reporting my experiences based on actual events which can be supported by an email audit trail and receipts. Hardly naive and hardly an attack - unless of course my comments were a bit close to a raw nerve then any suggestion of criticism would of course be a vicious and painful attack.

I am delighted to hear that the return rates for the Spyder 3 has improved. Having suffered with the previous two models I was not prepared to risk another. I am sure it is a fine product and an improvement.

Yes, Epson printers are a pain. I run 5 of them at different sizes and models. But when they go wrong it is pretty obvious. When calibration goes wrong, it isn't.

Meantime the PrintFix Pro solution continues to do stirling service.

All the best,

--- In datacolor_group@yahoogroups.com, Cdtobie <CDTobie@...> wrote:
>
> >>Graceful reply to what seemed an, at best, naive attack.
> 
> Thank you. I would like to think it was that. There has been a groundswell of what I will politely call "intentional mudslinging" on a wide range of forums of late... Which I always find quite disappointing. I enjoy a spirited discussion, but not with a shill. 
> 
> C. D. Tobie
> Global Product Technology Mngr.
> Digital Imaging & Home Theater
> Datacolor.com
> CDTobie@...
> 
> On Sep 3, 2010, at 8:34 PM, Sat Tara Khalsa <sattara@...> wrote:
> 
> > Graceful reply to what seemed an, at best, naive attack.
>

Attachments

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.