[DriveSetup] various issues

[diver]

In this video a user is very confused by DriveSetup and runs into all sorts of issues with it.

​https://youtu.be/2jdmcLHU3Vw?t=266

Here are some of the issues I spotted:

Wording problems:

• <empty or unknown> should probably be renamed to Unallocated (done: hrev54869.
• it is not clear that "(Be File System)" in File system column means type and not actual file system (done: hrev54869).

Workflow problems:

• don't disable Format menu if a volume is mounted but can be unmounted (done: hrev54875)
• creating a bfs partition should format it to bfs at the same time (#15634)
• when creating a bfs partition Active partition flag is not set (​https://youtu.be/2jdmcLHU3Vw) (#7930)
• Change parameters menu opens an error alert ​https://youtu.be/2jdmcLHU3Vw?t=416 (#11641)

Partitionning system problems (#9108):

• Intel Partition Map disappeared after reboot and became GPT instead (​https://youtu.be/2jdmcLHU3Vw?t=1055)
• creating Partition Map recovered previous partitions instead of creating new layout (​https://youtu.be/2jdmcLHU3Vw?t=1109)

Invalid:

• creating a partition doesn't show "Active partition" checkbox (​https://youtu.be/2jdmcLHU3Vw?t=493) it's expected, the drive was initialized with GPT which has no concept of "active partition"

[X512]

creating a bfs partition should format it to bfs at the same time

+1. This is implemented well in discmgmt.msc in Windows. Creating partition without formatting it have no meaning.

[bruno]

Drive Setup is a real important first step into Haiku. Fortunately this user made a video out of it. It is therefor a gift to have and to do it much better now...

Formatting a drive to run Haiku on it should be almost automatic. Something like use this drive for Haiku and install it autocratically Creating and formatting a drive to BFS and set it active by default! +1

[X512]

Also it should be possible to change active partition of existing partition without reformatting.

[pulkomandy]

It's supposed to be in the "change parameters" menu but it's broken currently (#11641)

[pulkomandy]

So, after a bit of investigation it turns out we already had tickets for several of the problems here, which I have added to the description and "blocked by". Moved them all into beta3 milestone as well.

For the changes that had no tickets attached, they were rather simple fixes and I have done them. I think they could even be enough to help with the most common problems (sometimes, giving just a little better user feedback goes a long way). Not to say the other tasks shouldn't be done, still.

[pulkomandy]

I'm moving this out of beta3 milestone. Most of the issues have been addressed, with only two left that I think are less important. We will see if this is enough for reviewers to manage a succesful install this time?

[pulkomandy]

I think the remaining issues are less critical, so this ticket does not need to be a release blocker anymore.

[pulkomandy]

I am closing this because each of the sub-item has a ticket now, so this one is not really useful.