Hmm, nice find on the 'fmwr' resource!
I'm not sure why the progress bar doesn't come up...it probably means that something in the updater script failed and it decided not to try replacing the firmware. I think I saw that happen when I had a checksum wrong on my B&W G3 updater, but we haven't messed with the checksums so it's not installing for some other reason. For whatever reason, the Open Firmware script decided it couldn't update the firmware. Hmm. You did power it down, push the paper clip into the programmer's button, power it on, and wait for the long beep, right? Then it acts like it's going to update, but it reboots instead?
It's possible that the 1.2 firmware changed something and now the 1.0 firmware updater script doesn't know how to handle it. That would take more digging in, but since you have the floppy working, it's probably not worth it
I'm glad you got it working! Woohoo! I am not sure what possibly could have re-enabled the floppy drive though if the firmware didn't install. Maybe nobody ever bothered rebooting back into an older OS back in the day to see if that was part of the problem?
I'm not sure why the progress bar doesn't come up...it probably means that something in the updater script failed and it decided not to try replacing the firmware. I think I saw that happen when I had a checksum wrong on my B&W G3 updater, but we haven't messed with the checksums so it's not installing for some other reason. For whatever reason, the Open Firmware script decided it couldn't update the firmware. Hmm. You did power it down, push the paper clip into the programmer's button, power it on, and wait for the long beep, right? Then it acts like it's going to update, but it reboots instead?
It's possible that the 1.2 firmware changed something and now the 1.0 firmware updater script doesn't know how to handle it. That would take more digging in, but since you have the floppy working, it's probably not worth it
I'm glad you got it working! Woohoo! I am not sure what possibly could have re-enabled the floppy drive though if the firmware didn't install. Maybe nobody ever bothered rebooting back into an older OS back in the day to see if that was part of the problem?