v2.1.0 VHD RDB non-writable

[Maccara]

Hi,

First of all, I would like to know if someone else has run into this issue before I delve too much deeper into this, and if I'm doing something wrong.

I have a strange issue when I create a dynamic volume, where WUAE needs to be QUIT and have the configuration saved, or the dynamic disk will become write protected.

Steps I can produce this in:
1. Quickstart A500+ (KS 2.04 + WB 2.04 Install disk)
2. click "Set configuration"
3. Go to hardfiles tab and CREATE f.e. 20MB dynamic hardfile
4. "Enable RDB"
5. Start

With HDToolbox, any changes to HD partitionin etc + save results in "Error 28".

Now:
1. SAVE a temp configuration
2. QUIT WUAE
3. start wuae & load the config
4. Start

Now everything works with HDToolbox (partitioning) and then formatting etc.

If I next hit the restart button in wuae and load a A500 quickstart (KS 1.3 + WB1.3) and add the just prepared hardfile, it is write protected in WB1.3.

I can fix this again by saving the configuration and completely quitting wuae.

Noteworthy is that I absolutely need to save the configuration and use that after restarting. If I just quit and try to add the hardfiles again, they're write protected.

I don't have this problem with non-dynamic hardfiles. Didn't try this in earlier versions of winuae (yet, at least), so I have no idea if this is a new or old issue.

My system may definitely affect this, as I'm running WinXP x64. However, it seems like it might be some dangling filehandles in wuae, but I haven't debugged this further at all yet.

(dynamic hardfiles work in other (virtualization) apps so it is not a general problem of the tech on this OS)

Edit:
Configs added:
- "Not Working.uae" -> immediately saved after A500 quickstart, which did not work
- "Working.uae" -> immediately saved after quitting and loading "Not Working", this works.
- As you can see, there's no difference
- Logs of the same "sessions"

Edit2: I can replicate this on WB 3.1 also (A1200 basic non-expanded quickstart configuration)

[thomas]

I can confirm that VHD files are mounted as write protected, no matter if R/W switch is checked or not.

The same VHD file works fine when mounted under Windows using VHDMount and added to WinUAE using Add Harddrive.

[Toni Wilen]

It was caused by unrelated transparent archive support handle leak, VHD is internally considered "an archive" (VHD is a container that contains a HDF), parent handle was leaked in this case.

VHD is opened as "an archive" to view first 8 bytes of data in HDF GUI. Fully automagic this way

[Maccara]

Thanks for looking into this!

Originally Posted by Toni Wilen

VHD is opened as "an archive" to view first 8 bytes of data in HDF GUI. Fully automagic this way

Ha! That's a neat trick to do it.

Originally Posted by Toni Wilen

It was caused by unrelated transparent archive support handle leak, VHD is internally considered "an archive" (VHD is a container that contains a HDF), parent handle was leaked in this case.

So that was it? And here I was thinking I was going nuts... Looking back at my bug report with fresh eyes/mind, I could've been much more clear & concise what actually works/doesn't - glad you figured it out without needing to elaborate.

Sounds like simple fix then? I'll try that again in some future version (not a terribly important feature for me at the moment and I hear next beta is not too far away anyway ).