Hi all
Well once again many thanks for your replies, most appreciated and especially Synthohol.
Good news, I have managed to fix it.
So for the record and completion of this post this is what I did.
So back tracking and picking up on what you suggested Synthohol:
Back when we picked up the machine I had activated the restore point feature for reasons such as these. I had run it twice, going further back each time. It completed sucessfully, however this made no difference. Next I shut the Fiery down, took it apart, thorough clean, inc. dust and contacts cleaned. OS booted up fine as before, but still no Fiery system.
I happened to come across a post on
here which discussed using the setup file located at C:\CD2\Fiery\setup.exe to reinstall the Fiery system. I did as set out in the post, including renaming the files that didn't overwrite at first go... once completed, rebooted the machine, os ran up fine, but still no Fiery system. So tried again, this time creating a new folder E:\EFI2, I created a new folder because it would not allow me to simply rename the existing folder E:\EFI.old or something as access was denied. Anyway, ran the C:\CD2\Fiery\setup.exe application again mapping it into my new folder E:\EFI2, rebooted and much to my surprise all is well! So, it was the Fiery System software that has become currupt and thankfully not the hardware!
Now in case anyone should be reading this as they are in the same predicament. We own our machines, and we fix our machines and have been doing so for 10+ years, so I am happy to take the risk. Should anyone else try this, you do so completely at your own risk.
So, hats off to you all and on to the next fault!!
which today is a J9401 ADU issue and I've already replaced all the clutches in the ADu about 6 months ago!
Have fun
Mark
Bookmarks