Hi Peter,

The size of W8 is : 13,414,401KB and the copy has identical size (I attempted 2-3 times with the original disk and was starting again with a fresh copy from "MyWin8 - Copy.vhd").

Win 8 is bigger by approximately 102Mb compared to the 3 different Win 10 OSes (all are 13,312,001Kb including the copies).

There are 2 green round stickers at 2 corners of the HDD. Just in case: there is also a tape with "ram os" printed on it.

I disabled the graphic card 2 days ago in BASE mode but I suppose that this is not enough ? I should remove it physically ?

It is probably what you mention (something in the BIOS). I could start from scratch, reset the BIOS for "factory settings" and retry ?

In the BIOS I have attempted to (with success):
- reduce CPU clock speed (1.2ghz is the lowest possible with the Asus Sabertooth x79)
- disable the "C1" and its siblings
- turn the spread spectrum of the CPU and PCIe OFF
- disable some fan controls
- shut the virtualization and some other details of that order.

Apart from this, I did not disable anything else as I am walking into that like a blind person...

Side notes (Windows 8 ):
- I loaded the correct driver for the "Simple PCI communication" at some point but I also tried without it first
- I increased the minimal CPU speed from 5 > 100%, while modifying the XXHE settings. At next boot, I put it back at 5%
- in "Control Panel > System amount of ram is exactly 16Gb, no decimal, no less.

Side notes (BIOS)
- The Sata config is in AHCI mode (just mentionning - I did not touch it)
- I do not recall seeing a "shadow" something, but I will check if there is.

That it about it. NO personal adjustement in Windows. The lesser, the better

Regards,

Alain

Hi Peter,

After catching 3 mice (yes, 3 of them where having fun on my kitchen counter and I don't know how they got there), I slept a little.

By "genuine", I mean the original disk. I have retried again this morning: same result. But as you say, I wished (not a necessity though) to compare. I do have Win8 plain vanilla on another drive (the one I have from before the os-ram drive). But it's ok with me, unless you come to the conclusion that Win8 can be the better one.

Up to now, nothing has showed me that working with a different disk has a different behavior in the results.

As you know, I always make a backup (or an image to be more precise), as it is good practice. I have a backup and the original disk. That is all there is to it.

I may eventually add 8GB of ram to allow more "breathing space", but I will then need to replace the whole ram set since I want to have the same brand and model (I was told that what I have has been upgraded and I don't want 16GB of one model + 8GB of another).

Regards,

Alain

While you are waking up, I am about to go to meet the Sandman

Peter, the last attempt was done with the genuine, after copying from the "MyWin8 - copy"...

As for the CPU: Intel 3930k.

Alain
PS: would you think that adding 8GB of ram may reduce this ? My belief is that this is non related, but...
PSS: the Memory indicates a straight 16GB by the way...

Hi Joachim,

Is there a particular reason why you prefer attended ? Is it a matter of practicality ?

Alain

Hi Peter,

Everything goes well now. At least up to the point where I want to go into ram. It still displays a lack of space, but the file is still the same exact size as the "- copy.vhd" version...

Alain

Funny, I thought about increasing the minimal CPU from 5 to something higher, but the messages I was receiving while just trying to access the XXHE settings was telling me that it would not work... I should have known by now that... I should try

Not that I have retried, but just to continue on my journey before I wrote here...

I finally was able to minimize the OS and then things got more normal (CPU at 1.2ghz), but it was not the end of my problems...

It refuses to go in ram, with the error that was reported by Joachim and Mani.

I started many cycles of back and forth in attempts to understand if I could make it work.

I will copy from the "MyWin8 - copy" again to see if it will be possible to go in ram.

I am very stubborn and I always try to do attempts from different angles - explaining the time I spent. I am ok with that, but I must admit that I should have taken some breaks in between. Now I feel a little exhausted.

As you know I never use the genuine disk, because I prefer to play around and am aware of the consequences. I can at least tell you that I tried with a SSD (Acronis), then a conventional drive... To finally resolve to take the genuine hard drive. The results were absolutely identical...

Now I will take an hour break, listen to whatever birds that are singing around and be back for a few other attempts...

Err... It is a lot faster with the SSD by the way (not all but to load)...

Thanks for your patience Peter. I can be a PITA with all my emails... I know.

Alain

Hi Peter,

Since I received the os-ram drive, all I did was use Win 10 build 10286 and nothing else.

Yesterday, after reading what you wrote about your listening tests with Win 8, I decided to setup Win 8.

I ran through a lot of errors, to a point where I can only conclude that my copy of Win 8 is corrupted.

Before I start taking screenshots of all that happens, I would appreciate if you could send me a copy that you would first have attempted to load in ram.

If necessary I will take screenshots, but I already have spent about 10 hours on this...

Regards,

Alain

Hi Joachim,

Strange indeed I have 3 different brands of sata controllers on my motherboard... Go figure...

Alain

No need to be sad Peter... Maybe your scratching is my itching here ? 

There can be so many specific aspects in each system. And if this is hearing related, there is not much to be done... I am still wondering what is that I have forgotten to verify...

Alain

Ah... I haven't touched my sig for quite some time... I am always listening to Win 10 buil 10586, with the os-ram drive and Intona... I have tried Windows 8, but the one I have on another HDD, for comparison purposes about this "voice" thing.

I am not listening but I am reading

I will not tell what I did, you will throw bird names at me

I will do some more tests and be back, even if I can't be on par with you (no LPSU powering my audio PC for instance)...

If you ever go back to Windows 7, I will go outside to scream

Alain

Sorry to contradict you, but the two Esata ports are not from Intel and no one of them works with the os-ram drive in BASIC mode (not from ram) with Win 10... That is why I suggested to add a back plate that is Esata externally, but connected to a bug standard internal sata from the motherboard.

Alain

Peter,

I don't know why I haven't tried these 2 external Esata ports before with the os-ram drive. I was lucky to have that Esata back plate. I have it as an accessory from an external HDD enclosure kit.

If you type "Esata back plate" in Google, you will have a good idea...

Alain

Side notes:
- The 2 Esata ports are from AsMedia (sata 6gbit)
- My external connection works, because I wanted to have Sata 2 speed only (...), so the third connection is through an internal sata connection, to an Esata plaque at the rear. At the time I also wanted a third external drive,

Alain

I don't know if this is related, but I ran through a strange situation a few days ago.

My motherboard (Asus Sabertooth X79, from 2012) has two Esata ports (one also carries "power", the other is standard_. The 2 of them are not from Intel.

If I try to boot from any of them:
a) With a regular OS drive = Works (Windows 8 "plain vanilla")
b) With os-ram drive in base disk mode (Win 10) = does not work
c) With os-ram drive in ram mode = Works, but can't reconnect it to save settings at the end of the session.

Edit: It has been a long time since I have tried these 2 ports. I never tried them with a Win 10 standard drive.

I have no driver problem with the controller that manages these 2 ports with a regular OS drive, but it does not seem to be compatible with the os-ram drive when the OS is loaded as a base OS (not in ram).

Alain