Yes, according to the thread below (which I also quote above), the
problem is reputed to be a Windows only. Unfortunately, firmware is OS
independent and I did the upgrade on a Mac, so I think the Windows
specific nature of the problem is off base.
This morning I discovered that HP removed the firmware from the
Windows download site, but not the Mac site.
Most, but not all, people with the problem can eventually get their
printer to boot, either by removing the ethernet cord before booting
or by just power cycling. In my case neither option works.
However, I do suspect this is likely that this is a bug in the
firmware rather than a hardware problem, since many people experience
it when doing the firmware upgrade.
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
On Sep 13, 2008, at 1:10 PM, Peter M. Macdonald wrote:
This is a problem with the Windows version of the firmware upgrade.
It is not a manifestation of a damaged printer. HP are aware of the
problem, and will shortly put a new version of the file on their
website. There is a long thread on this on the printers forum on
Luminous Landscape. See http://luminous-landscape.com/forum/index.php?showtopic=27728
----- Original Message -----
From: toasterboy66
To: [email protected]
Sent: Saturday, September 13, 2008 9:02 PM
Subject: [HPDesignJet_Printers] Re: Z3100 firmware TR12-
TR_07_00_00-3_mvl40-x86-opt
--- In [email protected], "Michael Keller"
<[EMAIL PROTECTED]> wrote:
>
> This is the crap that makes me paranoid to install new firmware. How
> many times has a firmware upgrade choked the machines?
>
Well, the Z series is rather docile compared to the 500/800 series
when it comes to firmware updates, but with a several hundred meg
firmware file there's still a lot that can go wrong.
Never upgrade via a large network.
Never upgrade via a home-router/modem/hub type of network.
Never upgrade if you think there might be something wonky with your
connection or your computer.
Never, for the love of everything that's holy, upgrade via a wireless
network.
In fact, would always update via a direct connection from a laptop
(power plugged in, of course), no hubs, no switches, and wLAN
deactivated.
Firmware file downloaded twice and checked for errors.
Toasty