Dual Booting Haiku R1/beta5 Alongside UEFI Windows 11

I have documented my experience as a guide and provide it at the following link in the hope it helps others save time.

If there is a better place and way to provide it, hopefully someone will let me know, and also hopefully the link is now “public”.

I am a sporadic connecter to the internet, so my responses are likewise. I will try add information/corrections anyone else needs as best I can, but I am no expert as in the “FOLLOW AT YOUR OWN RISK” caveat. I hope someone will take it and make the definitive installation guide as I am sure it could be optimised and corrected.

2 Likes

There’s an unofficial Wiki where you could add your guide:

Maybe you could even add it somewhere on the official Haiku website,but that needs to be approved by someone from the Haiku team.

1 Like

There is also an official wiki on Trac, why not use that instead?

3 Likes

Thank you @nipos. I reposted to wiki.beos.retro-os.live . I think I had missed this site because it seemed to be BeOS LIVE from the URL :innocent:
I uploaded the PDF version (the only document format it allows).

1 Like

Thank you for the suggestion @PulkoMandy. Call me stupid, but I just can not find an official wiki on Trac! Do you mean Trac as our project management and bug/issue tracking system. Down the bottom I see "Useful information

This Wiki stores some useful information that you might want to look at:" It looks well above my level/ability to contribute there.

I admire your posts on other threads I have read, showing your broad knowledge and understanding of Haiku. Thank you.

I thought you’d copy the text into a Wiki page,rather than uploading the complete PDF file.
That would allow other people to edit it later,when things get changed and information gets outdated.
Anyway,the PDF format is as good as it can get when uploading a document file,as it is supported everywhere and doesn’t require a specific software like M$ Word to read it.

Yes, that is what I thought too. I must have missed the link for uploading a WIKI page :roll_eyes: :upside_down_face: No time now. I am a non-programmer, non-Haiku expert and old, so don’t expect miracles. My post has copped a few views already, so maybe if there is no negative feedback or problems posted it would be a time to make a proper WIKI.
PS: somehow I quoted my original post in my previous reply and now I can not edit it out, so that shows my level :smirk: I am doing it from Haiku on a USB wireless link that came out of the ark: SLoooooooowwwwww!

1 Like

To create a Wiki page,you can simply type the page name into the search box and then follow the link to create it.
In your case,that could be the name of the site you want to create: https://wiki.beos.retro-os.live/index.php?title=Dual_Booting_Haiku_and_Windows_11&action=edit&redlink=1

Yes, it’s there, but I forgot that it is only editble by developers and some other people we manually granted permission for.

So it’s not really usable as a generic wiki. Sorry for that, I should take some more rest…

Your page on the wiki was floating around, orphaned and lonely, so I put a link to it here: Installing Haiku - BeOS & Haiku Fans Wiki?

2 Likes

You certainly deserve a break @PulkoMandy given the amount of posts you contribute :slight_smile:

Should I figure out how to get a bug fix ticket into Haiku about the failure of Haiku DriveSetup to set Partition Type to Be File System either when it formats a partition, or by the GUI menu option which indicate it should (but it doesn’t). Getting around that “bug” is the core of the whole procedure I posted and it would not be needed if that “bug” did not exist. It is the brick wall you hit. Without the “bug” UEFI Booting Haiku | Haiku Project is guide enough.

This “bug” thwarting many installs attempts, was previously discussed two years ago per the details below

waddlesplashDeveloper

Mar 2023

This sounds like a bug we should fix. Is there a ticket about this yet?

It’s this one: Making sure you're not a bot!

2 Likes

Thank you for instant reply @PulkMandy. I guess it is in good hands then, and people will have to do the work around until it is implemented :slight_smile: I will monitor the ticket and when it is resolved remove the guide/Fans WIKI and provide a redirect back to the official procedure.

Why the [Making sure you’re not a bot!] label?
Its 1:30am here so shutting up shop.

1 Like

The forum software tries to query the page title from the bugtracker, but it hits a bot protection page and can’t get the real title. All links to our bugtracker is shown this way, and I’m not sure search engines will index the bugtrakcer with this setup in place.

We may remove it when the crazy AI training bots stop downloading every webpage of every website on the internet over and over…

1 Like

It would be nice at least if the forums didn’t display that for our own bugtracker. Maybe @kallisti5 can add a whitelist for local access?

3 Likes

Great work, I will try to follow your tutorial.

Please post the link to the PDF-File again!
All this not helpful posts about HAIKU-WIKI and other links make your work confusing for me!

Only the PDF-FILE is needed!

Thank you for your time to look into this important case to install HAIKU belongside Windows…

Very nice thanks, I will try to follow it now!

EDIT: Did you have Windows 11 installed first?
I created a GPT Partition, then the efi system partition (fat32) and last I created the partition for HAIKU (BeFS)

Is it possible to install Windows 11 after installing HAIKU?

Here it is: https://wiki.beos.retro-os.live/images/f/fa/Dual_Booting_Haiku_R1_beta5_Alongside_UEFI_Windows_11.pdf

1 Like

Hi Bruno @brunobastardi I did what most noobs would do. I had Windows, which I detest, and have tried Linux, but in my case the BeFS extended attributes are something I think I can use, so I tried the easy to create Live USB. Then to test the files system having Haiku on my internal drive was a logical step (then I hit the brick wall). I figured, from what I read, I was not the only one experiencing this problem and from two of the posts that worked (I have acknowledged), I cobbled together the PDF you have.

The Simple answer: Yes. Windows (and only Windows) was installed already with existing partitions except the one for Haiku. That is explained in the document.

You are by far more experienced than I am (from reading your posts) so hopefully you can fix things I did that were not actually needed or optional. As soon as I get things to work I get on using (I am a limited ability user who struggles even posting to these discussion boards correctly: not one of the brilliant developers, programmer, and clever people making Haiku come to life).

From your posts I read, you are creating a dual boot from scratch, creating all the directories etc, and in that sense is goes way beyond what I did, or have skills to advise upon. Given the Windows EFI/Microsoft/Boot/***.EFI already exists in the existing EFI partition with Windows installed, the Windows install isn’t an issue. In your case, given Windows does what Windows does, I suspect it will just overwrite everything as if it owns cyberspace. Why not instal Windows first, then my procedure should work.

I do not feel confident writing WIKIS for others to follow when I crash into every problem imaginable and most of it is magic to me. Maybe you can take mine as a draft an extend it to cover what you are attempting (that is what I did), with all of your knowledge going back years with Haiku.

Also, I mainly wrote it in the hope that the brilliant Haiku developers could see what methods noobs would try, and suffer, and that if they fix bug 19194 in Haiku DriveSetup, the standard UEFI boot instal procedure would be workable. They were and are aware of it, so it is now up to them. It may be a good thing that noobs don’t find it too easy, as my experience has been that Haiku is not quite there for everyday end users of the modern generation with massive expectations. Better wait in excitement than abandon disappointed.

Good luck finally getting your system installed.

2 Likes

i will try to see if it works

Good luck and post back what you experienced please. It would be nice to have a post saying yes it worked for me too :slightly_smiling_face: I can fix errors in the original doc and add modest extra stuff you might provide, or perhaps you can create the WIKI. Developers can then decide what could be changed to make the “official” posted process more seamless :grin: They are on to it, so I imagine it is a matter of priorities. It seems there is not a whole lot of love for Windoze users (not hatred, just that they can not see why Windows users would want to escape, or be able to cope with limitations. Windows has always been limiting, but it is/was the 800lb gorilla that for one reason or other “normal” people could not avoid) :upside_down_face:

That said, many Windows users probably should not attempt to use Haiku and many Windows users are not at all computer literate and usually have “consumer” attitudes, so I can see why they would be a burden (That is lack of computer skills, not Windoze). It is whether more true end users are needed in the current plan for Haiku development and financial support. My personal IMHO is that it needs planning and streaming such users through “Non-developer oriented” streams, along with a “curated” release of Haiku that “just works” that they can access by prescribed donation (The official Curated Haiku Distro). Is that what they call a freemium product? You waste hours setting up and downloading and tweaking. I would just download a styled version that “just worked” if the cost was sensible, as hours cost money if it isn’t fun for you. Of course the “just works” would be limited to having the identified hardware (a lot of older hardware seems to and that is a niche to exploit in the first instance, just a Linux always did), not the Windows “just works” on everything. It may also require a more stable LTS version to ensure it keeps “just working”, but my experience so far is that Haiku is very robust (compared to early Windows) and keeps working even when it spits the dummy. I am thinking older people who used windows 3.0 and win 95 might “get it” in the first instance.

I can see why Linux users are the good Haiku people (they are normally better at Windoze than Windows users, though they would never admit it :laughing: ), but to me as a user, Haiku is closer to Windows and Apple in its focus, how it appears to the user and in how it superficially works. Being able to port Linux software is a huge bonus to expedite it being usable for users. Yep, Apple is now BSD based and Windoze is POSIX aware, Zorin 18 is more like Win10 than Win10 etc, but hopefully my point is clear enough.

Also, to all wonderful developers on this discussion, my above musings are not imagining any changes to current arrangements, except maybe the changes to stop end users ending up where they will annoy you and distract from the wonderful work being done. The current release arrangements could remain identical for anyone wanting to develop, hack and otherwise do what is currently done (Styled desktops and user protections just get in the way). The upside would be a money earner and real users to really test good stuff and probably a more secure future if planned and implemented right at a time right for you.

I am not expecting existing flat out developers to do this development, or it to be instant. I am sure contributors other than myself would be happy working on such a project, if it was established. Programming wizards are wasted doing Curation and Styling, and are often so close to the coalface they can miss what end users experience and struggle with.

Having Iceweasle working has changed everything for end users and how sensible it is to use Haiku! (My Iceweasle crashing whenever I try download is a killer, but I am sure that will get resolved, and otherwise it has done what I normally use so far).