XXHighEnd

Hi Peter,

When upgrading to 2.09;

changed from ram to base os, changed to normal os.
pasted files to c:/xxhighend/2.xx

Xx did not start or respond at all
Deleted all xx files and reinstalled full version to 2.xx folder, still nothing

Probably done something wrong somewhere.
Any idea?

Hi,

Look at the properties of the files. Maybe they are blocked.

Regards

Thank you, yes xx exe was blocked.

Strange things ...

Is this solved now ?

Peter

Seem to be ok now, all files in xx folder was blocked.

Hi Peter,

unfortunately I found this topic right now and not already yesterday, when I obviously ran into the same problem.
As I wrote to you in my email yesterday, I got into deeper troubles furtheron, after I first got out of Min.OS and then copied back all files from my backup of the XXHIGHEND folder (version 2.07) to get it run again. Now I cannot switch back to Min.OS any more.

Kind regards
Richard

Hi Richard,

I think your problem now is a different one, and possibly the cause also. I think there is no need to go into it as the damage is (really) done. But no worries :

Backup / Restore (http://www.phasure.com/index.php?topic=3480.0)

Although in there it is more about back than restore, you will get the gist for "restore". Thus, you are going to set back the whole of the OS (takes a few minutes only).
Yours probably is 14393.0 and you will see the two files for that too.

Delete the normal one and copy the "copy" to the exact name as the one you delete(d).

Regarding the obsolete TRIAL it is best to just boot into one of the others, like 10586.0. Now look in Drive D: for the files.

---

To me it looks like you copied the whole new 2.09 over your previous version (like 2.08 or 2.07). This can't work. But maybe I judge wrongly. Anyway for a next time : RAM-OS disk users must paste the Upgrade Patch file.
And Richard, after this excercise you want XXHighEnd to be upgraded again (I don't know which version is in the backup file).

And yes, the base problem are these blocked files. See next post.

Best regards and good luck !
Peter

I suddenly think I know where these blocked files come from ...

The development machine I use here, runs on W7. The other day I had to upgrade that to W7/SP1. 2.08 was the first upgrade from that SP1 and W.09 also comes from there.

The strange thing is that I don't see this blocking myself. Not here, not on another PC outside of my network.
So I suppose I need the help of one of you to mimick this and to next/later check whether it has been solved.

Thanks,
Peter

Hi Peter,

thx a lot for your fast response. I did it as you suggested and copied a proper 14393.vhd file over the corrupted one.
Corrupting of the OS occured after I copied all files of a backup of the XXHIGHEND folder, which I have done two month ago, over the actual folder XXHIGHEND. I didn't even download the complete 2.09 rar file.

Yes, I also had the problem with the blocked files. But since I know about it, this is easy to resolve.

What I realized today:
As reported before, I have got a special LAN setup since a pretty long time: audio PC, music PC and LAN are directly connected to my router, the music PC even through Wifi only. And that's always working perfectly.
The only point that came up today is:
After moving out of Min.OS and back in again, the audio PC lost the LAN connection to my NAS (that's always done just with the local IP number of my NAS). Maybe this problem is connected to my settings in "Services and OSD". To optimize SQ, "Keep LAN Services", "Persist", "Keep PAN services" and "Keep Wifi-Direct Services" are all switched off. And that works great. But when I go out and back into Min.OS, the LAN connection to my NAS is lost, probably because of these settings. So, I believe, that this optimization should be done after already moved to Min.OS.
What do you think about that Peter? Could it be like this?

One final question:
Is it ok to paste the update files into the XXHIGHEND folder during Min.OS operation? I believe, I read something like this somewhere in the forum.

Kind regards
Richard

Hi Richard,


Yes, that is OK.


Keep LAN means : when going from Normal OS to MinOS, the LAN is kept. When this is not activated, the LAN is definitely set out of order when booting into MinOS. Persist does nothing in that case.
Keep LAN with Persist is No means : LAN is kept when going to MinOS but when Unattended Playback starts, it is not kept (and re-engaged when playbask stops or some functionality needs the LAN). With Persist is No, the LAN is always kept.

I know it is confusing ...

Are you OK again now ?

Regards,
Peter

PS: Maybe you don't realize it, but the fast volume was made for or on behalf etc. - you.

Hi Peter,

thx a lot for all these infos about the LAN switches. All these issues are much clearer for me now and I understand well why it's acting the way it does.
So version 2.09 is working now and it's pretty impressive. I will write my comment soon into the related topic.

Yes, fast volume switching and jumping to the next song is great! Thanks for that.

Kind regards
Richard