Yes, Fabio posted a much newer link (and yes, it should always bring you to the latest firmware for the device)
This is how Xerox does firmware versions
Generation is 072
Product identifier is 180
I don't remember the 20
6 is the last digit of the year (2016)
112 is the day of the year
00 is the version and build on that day
Hey Fabio: 072.180.206.11200 is not newer than 072.180.077.15201?
Does 206 vs 077 not matter?
Also, I see that link seems to be exactly the same URL as you posted here last year, I assume it is a latest and greatest permalink? Will that always reflect the latest SPAR for our machine?
Update to any watching this thread:
We had a hard drive failure on the 9303, and a Xerox tech installed a new one, our current software versions are:
I am assuming the previous SPAR was not a fork from the codebase, and that the fixes are still in this version.
Will let you all know if there are any adverse or really remarkably great changes in the performance of the machine...
So far, so good on the slowing GUI front!
We did notice a bug that preceded the SPAR install that continued after the SPAR, which will grind workflow scanning processing to a halt if you scan to searchable PDF with a certain type of grid paper anywhere in the job with handwritten numbers on it.
It shows the job as processing in the jobs list and in CWIS, and other people can scan their jobs in which are added to the job queue, but the job with the grid paper will take either hours (a 7 page one entered at 7am still had not finished processing by 11:30 am) or never finish. If you do a software reset the printer considers ALL jobs in the queue to be corrupt and deletes them all.
Once the printer gets into that statte, processing an OCR job that it has trouble with, it never times out, gives an error, or indicates that Scanning is unavailable. And you cannot successfully delete said problem job, so unsuspecting people doing scan jobs after the fact have no way of knowing their job is doomed.
When it gets into that state, it also shows SOME slowdown of the GUI responsiveness, but not in every screen and it does not progressively get worse to the point of unusability. I think this is probably unrelated to what the SPAR was intended to fix and unrelated to the problems we had been having since October of 2015.
I believe this SPAR was a success.
I probably won't post back here unless I see the original problem happening again with the same M. O. but will respond to anyone who finds the thread if they need help or my input.
Thank you all for getting this stuff noticed and fixed!!
Well, so far so good, no gui freezups so far since the installation of the SPAR.
It also did not require an AltBoot, so all setings / Workflow scanning templates etc were retained.
Will check back in in a couple of weeks and let you know if we feel we can put this issue to bed.
Thank you all for letting me know about the update, and proving that I ain't crazy.. well, at least not about this. :)