Two Haiku partitions cannot change settings independently

[HAL]

If I boot up Haiku hrev33234 and the other HD with Haiku R1/alpha1 enabled from the BIOS, it takes on all the settings of Haiku R1/alpha1. The About This System says R1/alpha1 hrev33109. The partition size is slightly larger for Haiku on the other partition and when I right click the Haiku drive desktop icon then click get info it shows the drive size as if it was the other partition. If I boot with the the other HD that has Haiku, disabled from the BIOS, in About this system it shows hrev33234. I can then change the settings independently. If I booted up with Haiku hrev1 alpha1 on the other enabled and then tried to change settings in hrev33234 then rebooted into Haiku hrev1 alpha1, I would find the changes reflected there. I tried to get a screenshot of DriveSetup in R1/alpha1, but could not save it anywhere because the partition with hrev33234 was enabled. Clicking the save button would not do anything. To see this bug:

1. Have two SATA (or maybe PATA) drives and one PATA drive
2. Have Haiku hrev33243 on first partition of second SATA drive.
3. Have Haiku R1/alpha1 on first partition of PATA drive
4. Boot up hrev33234 PATA drive/R1alpha1 enabled.

Result is: Haiku has exactly the same setting as Haiku R1/alpha1 hrev33109. Have a look in DriveSetup and there is no partitions shown for the second SATA drive. Partitions are shown for the PATA drive as if it is the one booted but it is not. Expected: after booting Haiku on Second SATA drive to have different colors settings and its own partition info in DriveSetup. Also all the other partions are missing on second SATA drive:: linux reiser partitions and a swap partition. If I do the same steps above with the PATA drive disabled from BIOS, everything behaves as expected. The proper Haiku partition is visible in DriveSetup along with the Linux partitions.

[HAL]

DriveSetup when PATA drive disabled

[HAL]

DriveSetup when PATA drive disabled

[HAL]

First attachment I forgot to put png suffix. Second is the same attachment with suffix.

[HAL]

SATA controller is Sil 3512 There are two SATA drive connections on the mainboard IDE storage controller is nforce2 IDE The PATA drive is on the first channel. Mainboard is Gigabyte GA-7N400Pro2 (REV2)

[stippi]

This should be another problem with BVolume and how it manages mount points. If you rename one of your partitions to something else than "Haiku" does everything suddenly work as expected?

[bga]

I used to see something like this unde4r VMWare when trying to mount a second image file (where the second one was an exact copy of the first one. I just wrote it off as a VMWare problem but maybe it was not the case then.

[HAL]

DriveSetup when PATA drive enabled

[HAL]

This seems to be another feature of this bug, that files cannot be saved from R1/alpha1 when the PATA drive is enabled but can be saved from hrev33243. This is how I saved the the picture "DriveSetup with PATA drive enabled". I did try renaming Haiku on the PATA drive to Haiku2 but I only renamed the volume icon on the desktop. Do I have to rename the volume from DriveSetup or Partd in Linux?

[HAL]

Replying to stippi:

This should be another problem with BVolume and how it manages mount points. If you rename one of your partitions to something else than "Haiku" does everything suddenly work as expected?

I tried renaming both partitions not just the PATA partition: PATA, R1/alpha1; Haiku2, SATA, R33243; Haiku1. I renamed both from the volume icans on the desktop. It doesn't help. I also tried to see if I could give the partitions a different label from gpartd in linux but it doesn't support it with this type of partition, as the message informed me.

[HAL]

Bug seems to be fixed in hrev33745. I don't know from what version, or near, because this is the first I have tried since the version I reported the bug with.