If it is a botched FW update, is the problem just a bad firmware file
stored on the hard disk, which causes the formatter not to boot?
If so is it possible to plug the disk into a PC and replace the
botched file?
John Anderson
On Sep 13, 2008, at 1:39 PM, toasterboy66 wrote:
--- In [email protected], John Anderson <[EMAIL PROTECTED]>
wrote:
>
> With regard to being careful about network connections, etc,
during
> the upgrade, this is probably good advice -- but the way upgrades
> probably work these days, the file, once received in the printer,
is
> verified against a checksum for any transmission errors. Only
after
> the correct file is received does the upgrade take place, and that
> doesn't require a connection to your computer.
>
> John Anderson
Technically, yes.
But even if the file is correctly transmitted, if the printer is
interrruped during the actual file replacement by a void network
command or botched Printjob, it all theory.
In theory, this should not happen either... but.
Going for a direct x-over connection not only improves the
reliability of your own connection, it eliminates the rest of the
network from the equation as well, esp. mixed networks with all their
funky mac protocolls can be the devil.
Practically, I've seen botched FW updates on harddrive based machines
aplenty (Z's, T's, 4x00s, 5x00s)
One of the small Zs would be a first for me, but I've changed a
formatter on the almost identical T1100 after botched FW update.
Sometimes it just comes down to (bad) luck.
A 08:11 is not a firmware error (that would be a 79:04) it's usually
a "formatter not found" error, and that's quite a lot worse.
