Octagon wrote:
Hi Pearse,
I am not sure what you mean with "compacted VHD File"? But I understand you have the whole OS in RAM, not just MQn loaded onto a RAMDisc? Your comments show you got there :D great!
As mentioned before the whole R2 2012 will work without any compression if you build a 10GB VHD. That will leave 2GB space for other files like MQn and music files. ;) Boot this VHD with Grub4Dos into RAM which leaves 6GB RAM of a 16GB RAM availability for the RAM OS. You will be able to confirm what Pearse, myself and others are reporting for yourself.
What I see from a lot of reports trying to reduce the size, that is where the trouble starts. Mainly this is tried due to less availability of RAM. I do not to use the R2 possibility to reduce storage use as it harms again the performance as it adds additional compression/decompressing tasks. My lowest RAMOS VHD is 8GB and I have heard about versions where R2 has been stripped down to 2.9GB which allows 8GB RAM system to be used. But I am not concentrating on the lowest storage for the moment but sq. ;) In case you are interested in more details, I would be happy to share more of my learnings from trying to reduce the size of R2. But I didn't want to go to much off topic.
And yes, having tested MQN, BHE, JPlay and Foobar, MQn is still best in sq. Pearse, i can also confirm your measurements about activity in general.
I can only encourage everyone to try, it is a major improvement.
Just my 2cents
Thomas
Hi Thomas, I am going to go through a lot of what you already know but still explain what I did for those who have no idea of what we are talking about here.
I created a full VHD 12 Gb (System 2) off a copy of Server 2012 R2 Essentials I had on a USB stick.
When I got this setup with Autologon, Drivers, etc, I ran AO 1.26b to change the installation to Minimal Server mode, not sure if this makes much of a difference to the compacting step but I did it anyway so as to have a full working VHD in Minimal Server mode.
Next I ran the compacting tool on this Full VHD (Minimal Server) which strips away files in the background and ended up with an Small VHD on another 7Gb VHD with a couple of Gb to spare in there after the compacting /stripping away had finished and this becomes System 3.
Both of these VHD's are now sitting in the C Drive and are bootable along with the original OS, these 3 choices are available as multi boot options on start-up.
After System 3 was compacted I booted it (small VHD with a unique name allocated by the compacting tool) and indeed a lot was stripped away and I think the OS was about 3 or 4 Gb.
I seen that JPlay, my MQN folder, AO folder had been stripped out during this compacting so I had to copy these back into the now running small VHD OS.
Each of these programs were installed again and on running music I found that all the PPA USB Card and Amanero drivers for the DAC were OK as music played fine again.
I then ran AO 1.26b again and the Optimiser to really clean it up and shut off all unnecessary services, drivers, etc. and still everything was working OK, including Mqnload and JPlay.
At that point then I ran the Grub4dos which was added as a fourth option on boot and selected the Firadisk RamDisk option.
This is the only point where I had difficulty in the whole process which I had repeated twice with 2 different SSD's with a Server 2012 OS on them.
Once I got the RamDisk to count to 7000 as it loaded to memory and it started up finally it has been very reliable since.
Going back and editing the Compacted VHD (select it on reboot) by adding latest MQN files and the Japanese File ReWriter did not cause any issues.
The only hiccups I found were when I edited the boot files to have the initial computer boot file set with Grub4dos as top selection and then Grub4dos application set to have RamDisk as first selection.
After making these changes the loading of the RamDisk would stop once or twice as it counted up to 7000, once I rebooted and it counted up OK it then would reliably boot again once it got there once.
To summarise I have 9Gb available in RAM after RamDisk boots and the Boot process from power up shows a multiple boot selection first with a short timer where I have Grub4dos as defaulted top selection (it is easy to go down to the other 3 systems when needed).
Then Grub4dos window opens with about 5 system options (there are options in there I could just edit out) but I have Firadisk RamDisk set with a very short timer so it boots to a window which counts to 7000 quickly and then RamDisk Windows OS appears and I am good to go like a normal installation of windows.
Takes about a minute from start I think.
I will do some edits on the latest guide and post it to a DropBox soon to help explain better.
Cheers, Pearse.