XXHighEnd

Oh the Horror.

After upgrading to v2.11 I noticed that XXHE stopped playing after a while. I thought this was due to the limitations of my XX V1 PC. Because of lack of time and pure frustration I didn't do any listening with the machine for a while. Yet now trying to resolve the matter I discovered that I have lost activation somehow during the upgrade.
Well, that's my theory. This behaviour is consistent with being unactivated and under 'Minimise OS' is the marking 'Activate'.

Now performing a backup-restore procedure does not help, it still is not activated after the freshest reboot of a copy of the '...-Copy'. Neither is the other working OS (10586) activated anymore.

It appears that something got awfully wrong. I have no clue why all versions got deactivated (is that normal behaviour?) or how to make it work again.

regards, Coen

p.s. I also did a back-up and restore from an off line '...-Copy' version. Also no success.

ehh ... Coen ... Restore your (ever back) original Workgroup Name to WORKGOUP.

?

Regards,
Peter

Hi Peter,

I'm in the '...-Copy' unpampered version. It seems that it is on WORKGROUP. I've attatchs some (compressed) photos

FWIW I'm directly on the XXHE PC, no network involved.

Hey Coen - Did you upgrade to 2.11 in each of the OSes ? ... hard to imagine that.
Also, did you apply the UpgradePatch or the full upgrade/install ?

Regards,
Peter

PS: Why does your title bar you just showed in Red (hence not-Demo) ?

PS: I now see that the red title bar you showed is from 2.06 anyway ...

Hi Peter,


No only on the 14393. It's the only one I use. I can only start 10586, the others refuse probablye due to the infamous systemclock/OS clock mismatch. I don't bother.


Well, maybe I goofed here. I can't recall what I did exactly. Ususally I unpack both versions in the /user directory before pasting the files over the existing version. However I might have accendentally started XX from this unpackung location in stead of the .xx folder. It very well possible that I unconsiously slipped into my (very) old way of upgrading with a separate folder for the new version.

Anyway I pasted the upgrade/patch files to the old directory.


You tell me! The photos are of a copy of the version that was shipped with the OS RAM Disk (MyWin10-14393.vsd with v2.06d on it) not the one that stops. Didn'd test this one though.

If you copied back from a backup, then that should just still be activated. If you only don't apply that full upgrade over it (better do nothing at first).

If it not clear to me whether that 2.06d stops. But if it does not, it is good to go for that patch.

Peter

Good news, 2.06b keeps playing! I can proceed with the setup.

One more thing:

In the problematic OS I tried to make a bootentry in the OS selection list for a boot I named 'W10-14393 V2 BASE' to be able to switch between the not working version and the fresh copy of the ...Copy (the V2). I renamed the fresh copy .vhd to 'MyWin10-14393-V2' yet this combination didn't go. The RAM and BASE versions are created but the "Repair With" column was empty for the BASE entry. I could not boot into this version.
Creating this V2 entry in the fresh version works like a charm, now I can boot into (the renamed) problem OS directly.
Maybe above issue is related to the activation?

Thanks for the support!
regards, Coen

Ah Coen, that is good news.

By now I forgot a litte, but at least all versions of everything related should exactly match. Thus the "-V2" should be in everything related. E.g. "the boot I named 'W10-14393 V2 BASE'" does not, at least not if I take you literally (the dash is missing).
Somewhere in the back of my mind it tells that you can't have two versions of the same OS because you won't be able to differentiate between two times 14393.0 (or 14393). Thus if the OS name itself is also part of the "everywhere" you can only get there if the OS versions are different. But as said, by now I forgot a little ...

Hi Peter,

Fortunately it turned out a quite simple to resolve the bootentry issue. I discovered that the (re)naming of the OS files does not allow for spaces. This was the difference between the successful and failed bootentries. 'MyWin10-V2.vhd' works perfectly, 'MyWin10 - V2.vhd' does not.

regards, Coen

Great !
And thank you for sharing that. I wonder whether I knew about that ...

Have fun again !
Peter

Thanks Peter, that should be no problem!