I have an original BeBox Dev kit - a few details missing, but appears otherwise healthy. Early Dev kits shipped without the front faceplate with the iconic blinkenlights, so I may have to 3D-print a replacement like @Dr_Slump did here:
I was able to use the firmware update floppy to bring the bios to version 1.1d7.1.
Startup shows the Be logo, and pressing left shift or space at the Be logo should show boot options. However, I appear to have none.
The machine has one SCSI HDD and one IDE CDROM drive. I will check the cabling to make sure they are wired correctly, but my problem is another: how do I boot to start the install? I have the install CD for 1.1d7, but I presume IDE CDROM was not bootable back then… or was it?
I just spent the last two weeks bringing a BeBox back to life - it’s pretty fresh in my mind. For whatever reason, under various releases including the 1.1d6 that came with my machine I was unable to boot from an IDE cdrom, trying three separate drives.
I ended up using a scsi cd-rom.
Other things that blocked my progress initially were:
A bad floppy drive - my rom updaters kept reporting a bad checksum for the image - sounds like your floppy drive is in better shape.
The scsi hard drive was so dead that scanning for drives failed hard and blocked the boot.
So make sure you are using known good drives - there’s a guy on eBay selling the toshiba XM-3601B scsi CD-ROM drives.
The 1.1d7 on archive.org is good - I was able to install it if the boot rom was DR8 or lower. After a couple of rounds of this sort of thing I ended up using scsi2sd - v5 works but is slow - V6 with a large card split into multiple scsi IDs. Device 0 I set as a 1gb drive and used ISO Buster (as other threads suggest) to extract the correct session on a given distribution cd image as raw, converted to ISO, then dd’ing that .iso to to the start of the sdcard. When you boot you’ll see the “cd” as device 0 along with whatever other devices you defined on the card.
Also, as other threads note (posting this mostly for posterity and future digital archaeologists):
Do hook up a serial terminal or terminal app via a null modem to serial port 4 (the bottom one) 19200-8N1 and hold down the F1 key during boot until output starts. There will likely be clues as to any issues, though many “warnings” are spurious or handled.
This isn’t an issue yet - since you can’t see any boot devices yet - but some of the releases I tried would fail as the kernel came up with 128mb RAM installed. This took a while to sort out, I ended up reducing the RAM in my Box to 64mb to reliably boot any or every release.