W10-14393 won't boot into RAM-OS

[Stanray]

I wish you all a happy and healhty 2017!

I had hoped to start 2017 in RAM-OS because I received the disk a few days ago and together with XXHighEnd 2.07 I was ready for the next level of SQ. But there's a rock on the road 

Here's what happens: Installed the RAM-disk, boot and land in W10-10586.0 TRIAL. Start XXHighEnd, rightclick STOP and reboot into W10-14393.0. Start XXHighEnd, set all settings, connect to network/MusicServer PC. This all works fine.

Then reboot into Minimized OS, Start XXHighEnd and play some music. All is fine.

But then when I boot into W10-14393 RAM Memory I end up with the successive screens below. The only thing I can do is boot back into W10-14393 BASE.

It's not likely that the message that there's not enough memory is the real reason. My Audio PC has 24GB RAM.

Any suggestions?

Regards,
Stanley

PS: what could be an issue is that the memory consists of 2x4 and 2x8 GB and that pc/software likes to see memory banks of the same size. (??)

[PeterSt]

Stanley,

I may wonder whether your 24GB is a too odd number in itself. Not because it wouldn't be allowed as such, but because I never really anticipated that. It is or 16GB or 32GB. And now I am looking at this number which starts with 512, while the number in Joachim's (also Mani's) screenshot (in that topic behind the link) shows 266, which is about half of your 512. The 32GB is also twice the 16GB ...

I feel this can be a tough one because I have no means to check (or I regard that too difficult). All I know is that exactly this disk (SSD) goes to those with 32GB of memory (including the Stealth) and that I have another one (this is another version) for 16GB. So all we "agreed" in ad-hoc fashion is that you'd better have the version for 32GB of memory because otherwise your additional 8GB would be a waste (can't be utilized). But I never thought of the possibility that the version that goes into RAM would be too large for your 24GB. I don't even know whether that is so, to be honest. Or ? ...
Uhm ... look below.
That's actually your RAM-OS Disk ... it was given the size of 24GB (so the 266 vs the 512 would be the comparison for this indeed, as the one for 16GB is 13GB in size).

Houston ! ...

Two options :
1. I give you a quite long guide to shrink your OS with 8GB (and I see a small possibility you running in troubles with that (it took me very long to find this long-threaded procedure);
2. You get yourself an additional 4GB of memory (which may come down to buying 8GB and take out the 4GB which may occupy too many DIMM slots).

3. Bonus option : I send you a new one for 16GB (and no, I am not going to make you a version for 24GB because it is all way too much error-prone - sorry !).

My advice is #2 but making 32GB out of your current 24GB system could also be a bit challenging (you must start looking for free slots, may not find any, must remove the 4GB which is replaced by the 8GB and your system must be able to take that).



Peter

PS: By email I told you that by guarantee it would not be about too few memory (because for nobody that appeared to be the case). But I must withdraw that now, obviously.

[Stanray]

Interesting case Peter 

What I will do, and had planned, but I was too false economical, is remove 2x4 and replace with 2x8.

Question: does the RAM-OS disk has to be "adjusted"?

Thanks,
Stanley

[PeterSt]

Hi Stanley,

If you have 32GB ... the RAM-OS Disk you have there is just made for that (and more explicitly than I recalled at first ). So nothing needs to be adjusted in that case. Also not the enlarging of it as I told you at first (by email); this has already been done.

Kind regards,
Peter

[Stanray]

Hi Peter,

Expanding the memory from 24GB to 32GB resulted in booting into RAM smoothly and everything works perfect.

 

Tonight it's time for a good listen.

Regards,
Stanley

[PeterSt]

Hey Stanley, that is super !

Best regards,
Peter