JV3 160SP printing previous jobs without resend

[SARTampaBay]

Odd problem today. Had a color issue with a file and took the printer out of remote and shut down. After reboot, the printer began printing a small file that we had run the previous day (and had not been resent). Shut down again, and it did it again. We thought it may be a production manager issue (ripping through flexi 7.5), so we removed and reinstalled production mgr, but no change.

Is there some residual internal memory that can be purged? We already shut down and unplugged the printer, but the mystery file still printed.

Thanks for your thoughts. Please let me know if I've left out info that may help find a solution.

Mark

 

[4R Graphics]

Not really sure what is going on but you can try when you restart the printer if its in remote take it out of remote and press the DATA CLEAR button then press the ENTER button I like to do it 2 or 3 times just to make sure it dumped everything.

After you do that put it back in remote and it should be fine.
if it errors out when you try to data clear it then you may have to just let it run it out and see what happens.

Good Luck.

 

[SARTampaBay]

Thanks. Will try that. We let it run out a bit last night and it seemingly started to loop, printing the same image several times. Will start fresh this morning.

 

[Masseria]

what software are you using?

 

[SARTampaBay]

Flexi 7.5. Thought the file was gone for good, as we ran this morning without incident. However just after noon, the same stupid little file printed after putting the printer back in remote after another job. The random job that printed is no longer in production manager, yet its ghost seems to be hiding somewhere in there.

 

[SightLine]

Parallel connected? Just a thought.... if so it's probably got multiples or something in the print spooler. Hope you are on firewire though, parallel is godawful slow.

 

[4R Graphics]

Sightline,
I forgot about that good call.

I couldnt imagine runnig one by parallel.

(love my USB JV33)

 

[SARTampaBay]

Thanks. Yep, we're running FireWire.