XXHighEnd

Hei, Peter

I just ran into a problem With RAM-OS. everything went fine until I rebooted into min-os in Version 10856.0. then XXHE would not start. Got an error Message about XXHE.exe could not start- serching for a problem............
Then I checked win-defender, witch was running.
Had to copy and reset, Shut off Defender and booted into min-os. and everything is ok now.

Regards
Arnt

Hi there Arnt,

Man, I now see you are right !!
But strange that I never noticed myself ? or what about other users ?
And why did you need that "restore" ? In there it is the same ... (as you noticed).


Interestingly on about the last day before I started to make the Disks, I had similar with 10565. So XXHighEnd just does not start and a small screen with as I recall a lot of dots (.....) pops up instead. I ended up in setting back a copy myself. So maybe 10565 has the same problem ?
It is only that I wonder what the trigger is to let it go wrong.

Thanks ...
Peter

I just checked and in 10565 it is the same. 10074 is OK.

Thinking back ... I just never had to shut it off myself. I actually only recognize it from making the Tutorial (which I made under 10074 - that's why that one is fine).
Windows 8/10 Tutorials - Shut off Windows Defender
 (http://www.phasure.com/index.php?topic=3222.0)

Regards,
Peter

I could not start XXHE 10856.0 again, so I just copied it, and deleted the old one. I don`know if that was right way to do it. But it seemed easiest to me at that point.
Had not much time lately, so mabe I should read some more instructions later.
Anyway - It Works well now. and the sound is outstanding.

Regards
Arnt

Hi Arnt,

Can you describe possible "unique to you" situations ?
I don't trust this, since it happens to nobody else.

Did this happen in the BASE version, the RAM version or both ? (but also tell me which the two you actually tried when it happened).

Last question for now :
On the disk are two green stickers. Do they have markings on them ? If so, please decribe ...

Peter

It happened in the base Version, but it was no problem before I booted into min-os. After booted into min-os, I could not start XXHE. I knew about the active defender problem. and checked defender. defender was not shut of, I used Your prosedure the turn it of, but I could not start XXHE (still in min-os).
Then I reboted Windows from the start button, and booted into the 10565 Version, and copied the 10856 Version. and deleted the old one. Booted into the New copy of 10856 Version and checked defender, and shut it off. Then rebooted into min-os, and everything was ok.

There are two green stickers With no markings

Regards
Arnt

Thank you Arnt.

But can you confirm :

What you just wrote is about the first time that it happened (and not the second time). Is that correct ?

Peter

Yes the first and only time. because I checked Defender after copying.

Arnt

Yes, but this was a second time, of at least not being able to start XXHighEnd.
True ?

Did the message "stopped working" or something, show exactly the same as the first time ?

Thanks ...
Peter

Turned off Defender in 10586 Base and am now in Ram mode and everything runs faster.  8)

Hello Peter
After the reboot and copying I shut off defender before I started XXHE, so then it was no problem, I did not try starting XXHE before that.

And about the first "stopped working" Message: It showed "stopped working" the first time I tried to start XXHE, after that there was something flashing on the screen, when trying to start XXHE, I suppose it was the same Message but I could not see because it disapeared to fast, and nothing more happened
XXHE did not start.

I had then shut down defender.
Rebooted with the Windows startbutton, but XXHE did not start, just the same flashing "Message".

Regards
Arnt

Peter
I have played in RAM-OS for 2 days with no problem. But now I Just started and album, unattended in 10586. Nothing happened, after 20-30 Seconds, and there was the error Message again "XXHIGHEND Stopped working".
Playback won`t start and I can not bring up XXHE again.

Arnt

Ok, let that be for now !
So don't touch anything.

Must think ...

Ok

In my 10565 situation I saw a "missing component" in the Windows Event Log. I don't know anymore whether that was the System or Application log. I think Application.

I had to apply tricks to let that work (view the logs) but possibly it worked without tweaks as well. So first two questions now :

1. Can you go to Explorer, Rightclick This PC, choose Management and then Event Viewer. In there those logs. CAn you get to that or does it give an error message ?

2. How "accessible" is you PC for Teamviewer ? This is just a question because it is an option, although I don't know yet what to do. But if you did not set it up for the Internet (from 10586.0 BASE) then better don't, yet.

?

Side note :

I saved my 10565 same (?) situation, so I should be able to debug that ...

1. I can not do anything, because I can not come out of unattended playback when I try alt-x. Then " XXHIGHEND stopped working " Message appeares

Aha ...

Does Alt-R work ?
It should bring back the desktop. But possibly it goes wrong for the same reason.

No it does not, for the same reason.

Is this a boot from RAM ?

If yes, just reboot.
You must of course hard-power off for that. But this is no problem.
If it is a boot from the BASE version, just do nothing but tell me.

It is a boot from RAM.
Rebooting now, just a minute.

Meanwhile my "bad" denoted 10565 is just fine or I forgot what was the matter with it.
So that is not much helpful.

I have rebooted into 10856 BASE.
Teamviewer is ok through my Laptop.

But Arnt, I was not asking that. I just said "reboot". This means that it will (should have) booted back in the same RAM Boot.

Please do that ASAP and don't touch anything else. I want to know whether it still works.
But I guess it did or otherwise you could not have booted into the BASE, right ?

Teamviewer is useless (now) because nothing is the matter.

More in a next post.
First now please boot into the 10586.0 RAM and see whether all is fine. Do not start playing music in the BASE (also not 5 seconds).

What I suspect is that something is wrong in general, but I can't tell what. Bad memory is perhaps too far sought but possibly you see something in Device Manager, like unrecognized Devices.

What MoBo do you use there ?
Btw strange : I was quite convinced that you have an XXHighEnd PC, but can't find anything (invoice) about that.

Did you (need to) do anything for Driver installs etc. ?

Yes I tried to boot into 10586.0 RAM, but it did not work. So I booted into 10856.0 Base

Ah ...
And why did it not work ?

Messages ?
How did you try it ? (switch on PC I suppose).

I have the same mobo as the XXPC.
No drivers installed.
A lot of unrecognized Devices in Device manager.
Will check what Devices it is in vendor/device search

OK Arnt, then I suppose that should be solved first, with the notice that one might remain :

(http://www.stordiau.nl/xxhighend/XXHighEnd PC Device Manager 01.png)
See at the mouse pointer. I never could/can get rid of that and I don't even know what it is (maybe other people know ?). So I always disable that (see little black arrow).

PS:
After you know it plays all right from RAM, do not forget to boot into the BASE again in order to apply the Drivers etc. *there* !!
Doing that in the RAM version is useless (it will vanish after a reboot). Ok ?

And dont forget to unminimize in BASE.

It playes all right for now, hope it lasts.
Have disabled the suggested Device.
But there are many more. all of them are Intel Devices.

Hmm ... that doesn't look te best. :)

Go to the BASE and make that Normal OS as Gerard suggested.

In the c:\Installs folder (of each OS) there's an "ASRock xx 64" folder (it is named something like that (van be 8.1 in there which is fine) and I do not refer to the "ASRock Extreme Tuning" folder. Now :

In there, there's an INF folder. Run the Setup.exe and notice that it really can take two minutes before something gets back to you.

N.b.: When you're asked to reboot, just do that.

Next do the Sata folder (setup.exe in there).
Next the LAN.
Next the USB.

That is all.

What does that bring ?

Seems to be ok, no missing Devices anymore ;-)

Ok, case closed for now. I mean, now all should be and remain fine. And when not ... well ... we will see about that then.

Now, back to MinOS and from there to RAM.
Btw, officially this should be done for the other OSes just the same. So if you are going to try one of the others, don't forget about this, ok ?

Well done !!
Peter

Ok, thanks for now

Arnt