I finally tried installing Haiku Beta 4 on bare metal. Well, I have 2 64 bit builds on my daily driver… I just added a dedicated Haiku build to it’s own 500 GB SSD card to see if it would behave better when it was all alone on some hardware, plus I really want to build a lot of AQEMU virtual machines on that drive and see if I am able to use one of those as my daily driver for awhile.
My landlady gave me her old 32 bit pc, which I am fixing up to run the 32 bit version of Haiku Beta 4. I’m actually really looking forward to that.
Anyway, onto my issue. Every time I install a single package, regardless of whether it is from HaikuDepot or from Terminal, Haiku wants to reboot. Now, I can install more packages, and it seems to work, however, after I reboot, I am missing a ton of application names in my application menu.
The applications are installed. I’ve verified that, by trying to install them again at the terminal. They simply don’t show up on the menu.
Another thing, when I reboot, I’m using rEFInd, and moved the Haiku bootloader to a folder named Haiku under EFI and renamed it to haiku_loader.efi
I love rEFInd as a bootloader and have used it for years. I added 5 themes to the project along with 98 OS icons as a thank you to the creator, including Haiku.ico. My most popular theme is rEFInd-chalkboard. rEFInd finds both of my Haiku Beta 4 builds, no problem, however, it is incredibly cumbersome to launch them every single time.
It asks me about resolutions, and I have to select the one I want, which is the one it initially gives me. But the really difficult part is the versioning bit. Honestly, I don’t recall doing this myself, so I’m guessing it just does this? On every boot up I get a list of how many times I’ve logged in, the most current one being the first entry. Honestly, I’d just as soon as skip this and boot straight into my system. This is such a chore tbh.