There seems to be two fixes, one a different file extension as suggested
below, and two a CHECK SUM check in the pminstall program BEFORE the image
is sent to the PM3. Certainly the checksum of the non-binary image can't
match the checksum of the binary image! If the pminstall program said
something like: "Hey you idiot, you're trying to load an OS with a checksum
that isn't valid." I would have saved lots of time, shipping costs, and
frustration. My Cisco routers do this, and I'm very grateful for it.
(I guess I can chalk it up to newbie hazing.)
Dave
>> During the upgrade process, I received a message indicating an invalid
>> opcode
>> and the upgrade was aborted. At that point the unit was dead, so I
>> rebooted it to no avail.
>This happened to me. I forgot to download it in binary.
Had same problem after downloading from website. No harm done
tho. Downloaded via ftp and everything was fine.
LE could fix this by giving a different file extention!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Don Lashier dl@newportnet.com
Newport Internet http://www.newportnet.com/