Opened 6 years ago

Closed 6 years ago

Last modified 5 years ago

#9609 closed bug (invalid)

BootManager in Haiku x86_64 Installer is not available

Reported by: Luposian Owned by: nobody
Priority: normal Milestone: R1
Component: - General Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: x86-64


When I go to install a boot menu, using Haiku x86_64's Installer, it says it's not available. Or, more precisely, it says it exactly this way:

"BootManager, the application to configure the Haiku boot menu, could not be launched."

I end up having to use the standard Haiku's (x86) Installer to create a boot menu, which is, at the very least, an inconvenience, because I have to boot up the CD to get to it.

Change History (4)

comment:1 Changed 6 years ago by anevilyak

Resolution: invalid
Status: newclosed

Please don't file tickets for missing components on x86-64. There is already a ticket tracking the list of those, and there are a lot of components from a standard Haiku install that are not yet 64-bit safe. As an end user, there is simply no good reason to be using it at the moment, the images are primarily available for development testing and nothing more at this point.

comment:2 Changed 6 years ago by Luposian

Where is this ticket you speak of (for tracking missing components)? I'd like to know, so I can follow it. My apologies, but it's sometimes hard to know what is a "missing component" (not yet implemented) and something that is broken (should work).

comment:3 Changed 6 years ago by umccullough

The simplest way to track what is missing intentionally is to compare the targets between these two files currently:

The first one is obviously for building the x86_64 image, while the latter is for all other images types.

To see a list of x86_64 tickets, you could just use the "View Tickets" feature and create a query. This will allow you to more easily track the status of x86_64-specific issues if you're so inclined to use it before it's officially ready.

comment:4 Changed 5 years ago by kallisti5

fixed in hrev46825

Note: See TracTickets for help on using tickets.