PDA

View Full Version : E-5000 problems



jellyfruit
11-08-2010, 04:14 PM
We have an E-5000 running on a savin c4540. After running great for 6 months we are now getting a shadowing effect around type that is overprinting (inside) solids. Our tech says is a driver issue, so we replaced the driver and no change. Is there a way to reload or upgrade the version on our fiery to see if that helps?

Nick_V
11-08-2010, 06:15 PM
Assuming you're at version 1.01, there is nothing to upgrade to. That said, there may be patches available. Since this is a Ricoh-manufactured Fiery controller, all service (such as reinstalling the system or installing patches) requires a Ricoh Technician.

Now, in a situation like this where you're running fine for 6 months and then suddenly something is wrong, the obvious question is "what did you change?" It certainly doesn't seem like you made any changes to the Fiery system or Fiery driver. This suggests that the cause of the change is probably not Fiery-related.

A new client workflow (e.g. upgrading applications) or something on the consumables side (e.g. low toner or different paper) are always worth considering.

This isn't to say that it's impossible for this to be Fiery-related. We'll need to know more about your workflow and what changed before we can make any determinations or suggestions.

jellyfruit
11-08-2010, 06:45 PM
Thanks Nick, We are running 1.0 with the e-5000, We are using windows based vista 64bit ps driver (as this is are only option). Mostly using cs3 and microsoft publisher which are the same as before the problem started. We have even sent documents through ghostscript to see if the problem changed and still the same thing. Do you think it could hurt to have the tech install 1.01 and is this something they should have?

Nick_V
11-09-2010, 10:46 AM
Well, the tech should definitely have it (and the other patches available for this controller). Would it hurt to install all available patches and bring your E-5000 up to date? Probably not. In principle, EFI encourages users to keep their system updated.

In your case, I'm a bit leery about recommending a service call to upgrade the Fiery since what you're describing still sounds like something else happened. There's no specific patch or driver upgrade to address an issue like this. And if there were, such an issue would have existed from day 1.

Can you provide a sample/scan of what you're seeing?