Base volume do not detach

[Tore]

Hi Peter!

I get this message: Base volume do not detach


Tore

[PeterSt]

Hi Tore,

It is best to be 100% precise, because the message you mention does not exist (and quite a few similar do). Also, *when* do you get this message exactly ?

Do notice that when you keep open X: in Explorer, such a similar message occurs indeed and it is justified.

Kind regards,
Peter

[Tore]

Peter, the message is: Base volume did not detach
The last week this message has come everytime when i get from attend to unattend

Tore

[PeterSt]

Tore, please do this :

1. Boot into a RAM OS (be sure you are in Minimized OS);
2. Remove the RAM OS Disk;
3. Click Play Attended (Unattended must be Off);
4. Click Stop.
5. Click Unattended.
6. Click Play.

When/where did the message occur ?

Peter

[Tore]

Peter, RAM OS is the only one i have.

Nick still have my SSD OS and i don`t think he can help me with it

Tore

[Tore]

Sorry, i missunderstood

[PeterSt]

Peter, RAM OS is the only one i have.

That is the one you need !
(but I think you understood that by now )

Peter

[Tore]

I get the message in both cases, ones i press play


Tore

[PeterSt]

What is the content of the "Copy Settings to" field ? (in the Presets section)

[Tore]

X:\XXHighEnd\2.xx\

[PeterSt]

Hi Tore,

Tore, please do this :

1. Boot into a RAM OS (be sure you are in Minimized OS);
2. Remove the RAM OS Disk;
3. Click Play Attended (Unattended must be Off);
4. Click Stop.
5. Click Unattended.
6. Click Play.

When/where did the message occur ?

Peter

Did you do all this ? I really like to have it confirmed.
Also a few new questions :

In which OS is this happening ?
Can you make a screenshot of XXHighEnd's Title Bar and post it ? (photo is fine, if you first check yourself whether I will be able to read what is in the Title Bar).


You can imagine I don't understand much of this. It should not happen, does not happen to anyone as far as I know, and you too never had it, right ?
It should be related to the Saving of Settings, which happens when XXHighEnd is closed. Thus, only closing it (cross away) should also imply that message. But does it ?

Regards,
Peter

[Tore]

Peter,

1.yes i did all you asked me to do
2.it happens with OS 10586 and 14393
3.it also happens when i cross away XX
4.it started some days ago

[PeterSt]

Thank you Tore.

At this moment I have no idea.
Maybe you can help me with things you changed ? Try to imagine each futility. It is probably something dumn, but I can't think of anything.

Best regards,
Peter

[Tore]

Peter,

i just changed "Copy settings to" from X:\XXHighEnd\2.xx\  to D:\XXHighEnd\2.xx\

X:\XXHighEnd\2.xx\ is on Music PC, i think it is OK now


Tore

[Tore]

The harddisk on Music-pc looks like this from Audio-pc:
D on Seagate (\\Tore) (X)

[PeterSt]

i just changed "Copy settings to" from X:\XXHighEnd\2.xx\  to D:\XXHighEnd\2.xx\

In itself this is smart thinking, but in the end it will cause problems elsewhere. So it might even work for Saving the Settings etc. but not for "detection" of matter. On the other hand this is exactly what is now wrong in your system.
No, I really don't understand what is going on.

What you could do is :
- Set back to X:\ etc.;
- Imply the problem again (stop XXHighEnd and watch for the error message);
- Restart XXHighEnd;
- Zip the whole contents of the TemporaryData sub folder (where the log files are) and send that to me by email;
- Look at the date/time in your system and tell me that too in that email (with the notice that the date can be 2015 etc. and I need to know it to interpret the log files in good fashion).

You don't need to switch on logging beforehand as this (RAM OS) stuff is logged by standard.

I am pretty sure this will be helpful.

Kind regards,
Peter

[PeterSt]

This problem was caused by using Drive X: for something else (in this case a music disk);
This is not allowed as the X: Drive is reserved for the RAM OS Mechanisms.

Peter