Base volume did not detach

[Leo]

Hello Peter, probably a mistake by me of some sort but whatever I try the base volume cannot be detached when in OS RAM ( 14923). I did not pay much attention to this message before and just removed the os disk when booted in RAM. But after reading more in the tutorials this is not the proper way probably. I have made sure all the referred to files are identical in both 14923 OS (ram and not-so-ram). What steps can I take to remedy this? regards, Leo

[PeterSt]

Hi Leo,

Which XXHighEnd version is this ?

Peter

[Leo]

2.07 (very happy with the sound as it is...)

[PeterSt]

Hi Leo,

Are you sort of 100% sure that the message is that the volume can not be detached ? I mean, I see such a message myself regularly, but it only looks like it is saying what you suggests. In reality it says something like "could not be detached because not found" or very similar. Anyway with the implication that it was not detached in the first place (and regard this a bug in itself).

Otherwise I don't recognize it ...

One pitfall : if you looked into it via Explorer by means of accessing Drive X: and Explorer is still open in it, yes, then the message is for real because you "lock" it.

If you don't recognize any of this, let me know what you actually do in sequence before this happens.
Oh wait ... I think I already see ... :

I did not pay much attention to this message before and just removed the os disk when booted in RAM.

Now don't laugh ... because this is what I do too and which is the proper thing to do. So in that situation it has never been attached (although logically you might think it was). But then really the message should end at something like "because not found".

?

Best regards,
Peter

[Leo]

Ha Peter,
You are surrounded by snow tonight anyhow so I present you with a photo album which more or less corresponds to the steps I describe below
All steps with minimised OS
stap 1 reboot into disk version of OS 14923
stap 2 checked whether all files mentioned are referring to the same shared X in both OS:
Detachment of volume is not possible here, but that seems normal to me
step 3 Reboot into ram based os 14923

And than I cannot detach the disk based os 14923, the top line of the drop down menu, from right clicking stop button,  is checked red. When I go to the second line to select a volume to be detached I get the same message as before ' base volume was NOT detached'. So not a friendly reminder but a stern warning. Does not make a difference if the harddisk is removed from the Stealth or not.
Hope this gives you some more information to proceed with. All the best Leo

[Leo]

sorry about the picture size. That is new territory for me

[Leo]

After I started remote operation, don't know whether that is related, and after having removed the hdd I tried to detach again from the remote desk and got a different message:

Something wrong with finding the BASE file system; must bail out

after OK to that

The XXHighend base disk is needed for this, retry ?

choice of Retry or Cancel

well how about that...

[PeterSt]

Hi Leo,

Photo albums are old fashioned by now. And especially those who are more than one meter wide. Anyway, I resized them so I can see myself what you are talking about. I see a couple of issues :

a. Never try to show off with a new camera on a forum;
b. Don't put up photos with nothing in them (08);
c. Proof your work before finalizing it.
haha
d. Do not try to detach any volume which never has been attached (see my previous post, but I don't think you got the message of it);
e. Do not use drive X: in any circumstance because it is reserved for this mechanism. Hence, your music is not allowed to be on X:.
f. Never use the \Data\ folder elsewhere than default, unless you seriously know what you are doing. So put that to c:\Data\ (and maybe find yourself deactivated).
g. Never change such data from the RAM-OS Disk to begin with. I mean, why ? it worked when you received it.
h. The field "Copy setting to" *IS* correct. So leave that as it is (pointing to that X: location);
i. Very very good that you showed your settings, because I could not have guessed that these things were the matter (and the culprit !).

Lastly, keep in mind : after booting from RAM no volume is attached as such. This means you can also not detach it. Call it "computers" that the message in such circumstance can be "BASE Volume did not detach". Correct it is, but it is completely misleading of course. Thus :
- Boot from RAM;
- Pull out the disk.
that's all what's needed.

Want to use it again in explicit fashion ?
- Put it in;
- Attach it;
- Do what you want on Drive X: (because there it now sits);
- Close Explorer which still might view drive X:
- Detach it.

Or Want to save your settings explicitly ?
- Put it in;
- Attach it;
- Save Settings via the menu on the Stop button;
- Detach it (but maybe this goes automatically).

Or want to shut down the system (or reboot) ?
- Put it in;
- Shut down (or reboot).

And do notice that in each of the circumstances a message may tell you that "The BASE Volume was not detached because not found". This is a bug (and springs from me writing the program ).

Also notice another bit of misleading thing : When you'd have attached the BASE volume explicitly and it is thus available under drive X:, if you then close XXHighEnd it is detached under the hood (this is on purpose for reasons, but not obvious at all and times inconvenient).

Best regards and take it as it is (just fun !).
Peter

[Leo]

I will read this a couple of times and try to digest the deeper meaning of it all