I typically can find what I need good enough from deduction and forums that I solve my own problems but this has definitely got me.
I have a Doc 12 with a Fiery X12 FrontEnd running MS NT 4.0 (Build 1381:SP6) [Upgraded using the composite patch was originally SP5] 64 mb.
The problem I'm having is [after some time of storage I have pulled this monster out for some usage after clearing a sensor error on the transfer belt reflective pads, and a thorough cleaning aswell as a HD wipe and a revert to factory default after an HD issue] the Fiery WILL NOT communicate test pages and the like with the D12.
The D12 is working just dandy doing copies and the like, however I cannot send anything from the Fiery. I just cannot seem to figure out why it isn't going through. I tried checking my cables and any other basic. Even upgraded using the 400mb composite patch. Does anyone have any thoughts, this copier's scanning ability is a vital element in a job currently being worked on here.
The Fiery can recognize when the D12 is off flagging the "Check power and cable" error. Also when the Fiery reaches the Blue screen with the system info and the "...."s (Which I add is where the boot stays after loading up.) it initiates warm-up over on the D12.
I can communicate with the Fiery through Command Workstation, CMD Ping, and PageScope just fine.
Any help would be greatly appreciated, particularly procedural help Thanks
Bookmarks