Opened 16 years ago
Closed 15 years ago
#3965 closed bug (fixed)
DriveSetup: reversed behavior for (un)mounted volumes
| Reported by: | mmadia | Owned by: | bebop |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Applications/DriveSetup | Version: | R1/pre-alpha1 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | x86 |
Description
rev30841
The Partition menu seems to have reversed behavior for most partitions. eg, Mount and Initialize are available on currently mounted BFS partitions. The reverse for unmounted.
See attached images for visuals.
Attachments (3)
Change History (9)
by , 16 years ago
| Attachment: | drivesetup-1o3.png added |
|---|
by , 16 years ago
| Attachment: | drivesetup-2o3.png added |
|---|
by , 16 years ago
| Attachment: | drivesetup-3o3.png added |
|---|
comment:1 by , 15 years ago
comment:2 by , 15 years ago
| Summary: | reversed behavior for (un)mounted volumes → DriveSetup: reversed behavior for (un)mounted volumes |
|---|
comment:4 by , 15 years ago
DriveSetup still mixes up partitions, sometimes not letting you unmount a mounted partition, resulting in you not being able to repartition or format as you need to. It can make you unable or unwilling to install Haiku. Alpha newcomers can not be expected to know about the workarounds.
comment:5 by , 15 years ago
| Owner: | changed from to |
|---|
Reassigning to Bryce. Maybe he's motivated to have a look. :-)
Note:
See TracTickets
for help on using tickets.
Still seeing this very frequently. It seems that the only way for me to correct the behavior is to use DriveSetup to Partition->MountAll, Rescan, Use Tracker to unmount all Volumes (except boot), Use DriveSetup to Rescan, and then finally Initialize.