Zenja

Excellent news Augustin. A lot of interest will be generated by R1B1 news, and lots of fresh installs will be attempted. My biggest concern on the hardware side are the following 3 items:

• XHCI crashes (KDL) for USB3
• HDA (unmapped audio ports) which can work if the user reboots into Haiku from another OS
• UEFI boot which can be resolved with separate install image

A nice warning message on the download page should alert users about this issue.

My second concern is the 32 compatibility port for x86_64 systems (I expect most downloads to be for 64 bit system). Ideally, Jerome’s work on the compatibility layer should also make the R1B1 release, but if it cannot, then at the very least we should alert the users to know that it’s coming.

Lastly, some promotional screenshots would be nice. Screenshots for apps like LibreOffice, Blender, QtCreator etc should ease the migration to Haiku.

Having said all that, I really need to spend more time on my native Video Editor (missing audio editing and titles, however the video effects work very well using GLSL effects). My goal is to launch just before R1 final.

1 reply

kneekoo

After such a long wait, it’s amazing to see the first beta soon to be released. A lot of great work has been done, and Haiku is in the right place to receive a lot more attention.

I also share concern about the USB3 issues - my Skylake-based PC restarts almost instantly when trying to boot from USB3, so it is plausible that others will have this kind of issue. But we can’t realistically expect a fix with the proposed timeline, and I think the Beta 1 is far more important than USB3 boot.

I can’t believe we’re so close to this milestone. Awesome!

2 replies

mazbrili

i’m very happy that R1/Beta is soon to be release… thank for All Haiku Dev…
thumb up…

i will do my part my best as translator…

apgreimann

Hooray! The Beta is coming!

waddlesplash Developer

We’ll see. I believe @pulkomandy said he’d try to devote some time to investigating XHCI. But, yeah, unlikely there will be anything truly revolutionary at this point.

Almost certainly not getting any big fixes in on this one, unless someone else steps up to the plate.

We have a WIP that should be deployed in the next few days or so to add the UEFI loader to the anyboot images.

It will not. It was already merged once and started causing too many strange issues that it’s too big a risk, so I’ve requested it not be included. I don’t know what major things it prevents one from doing – certainly running BeOS applications and 32-bit applications in general is nice, but I don’t see how it’s such a must-have…?

The release notes will have them, for sure.

1 reply