Title: How to make persistent changes in the BASE versions? Post by: juanpmar on February 04, 2016, 11:05:06 pm Hi Peter, IŽd like to know how to make changes in the BASE version in order to maintain those changes in the RAM version. E.g. do I need to deactivate Windows Defender each time I reboot?
Regards, Juan Title: Re: How to make persistent changes in the BASE versions? Post by: AlainGr on February 05, 2016, 12:32:14 am Hi Juan,
If you boot into a BASE OS (not in RAM), then you can normally do the modifications you want (shutting down Defender for instance). Just to be on the safe side: do one modification, then reboot. If it holds then it means that it has saved the update. You may then do the modifications you like, then boot in RAM. Hope this helps... Alain Title: Re: How to make persistent changes in the BASE versions? Post by: juanpmar on February 05, 2016, 12:57:18 am Hi Alain, it's impossible to boot from any BASE version, it always boot from RAM versions.
Juan Title: Re: How to make persistent changes in the BASE versions? Post by: AlainGr on February 05, 2016, 03:57:12 am Juan,
Are you trying to boot through RDC ? If so, I would suggest that you boot with a screen, keyboard and mouse connected to your Audio PC. You should see a menu that will allow you to choose the Trial Windows 10 build 10565 BASE OS. When being in it, start XXHighEnd and then right-click on the STOP button, then select "Boot into" that will show you the RAM and BASE OSes that you wish to boot with. Once you have chosen a BASE OS, click the Apply Button, then the Reboot button. Stay with the monitor, keyboard and mouse still connected to the Audio PC. RDC will be for when all except XXHighEnd is at your convenience. Do not forget to Minimize each OS if this is your intention to have each of them in a Minimized state. Each time you are done with the adjustments for each of the OS of interest, you start XXHE in each of them and right-click on the STOP button, then select the same (Boot Into), to go to the next BASE OS of choice. When all will be done, one OS after the other (or the only ones you wish to adjust to your liking), then do the same routine, but return to the TEST OS (Windows 10 build 10565 BASE). Start XXHE again, then right-click the STOP button, then select the Boot into, select the RAM OS of choice, then click Apply and finally, click Reboot. This time it will start the RAM OS of choice, reflecting the adjustments you did previously. For the moment, this has been the way I do it, but I certainly will not pretend there isn't an easier way. My interest only goes to Windows 10 build 10586.0, since it seems to be the best (as stated by Peter - I hope it is how you described it Peter). I am not interested in the other OSes builds. I already have listened to Win 8 and Win 10 buiild 10074. I hope I have not just confused things more, but if so, I would ask Peter to remove this post (please). Regards, Alain Title: Re: How to make persistent changes in the BASE versions? Post by: juanpmar on February 05, 2016, 09:03:44 am Hi Alain, thanks for your explanation it is very clear. I followed Peter's tutorial and I think I made correctly each step but I did it with a cloned disk that I made to have a backup just to know if it was working. The first time that I installed it Windows repaired it automatically. Maybe that cloned disk had some errors although it appeared exactly as the original. I'll try it again today with the original because I made the test yesterday night and it was too late to make more tests
Regards Juan Title: Re: How to make persistent changes in the BASE versions? Post by: PeterSt on February 05, 2016, 09:19:07 am Hi Juan,
I am sorry, but right from your post #1 you testify that you did not read anything of any tutorial. So to be honest it annoyed me a little bit that Alain took so much time to explain the things you should have read in the Tutorials (http://www.phasure.com/index.php?board=27.0) and then out of everything you also say that you work with a clone of the disk. :fool: Addendum Sort of part of the subject is that you actually can not clone the disk and resore it when needed. Now I am not sure whether I should have said : Sort of part of the subject is that you actually can not clone the disk and use it when needed. or that the typo in there ("resore") made it unreadable ... but ... Best regards, Peter :) PS: I will adjust that text a little, to be sure it is not that for the next person. Title: Re: How to make persistent changes in the BASE versions? Post by: juanpmar on February 05, 2016, 10:30:32 am Hi Peter, of course I read the tutorial from the beginning, I even printed it to have it in my hands while I was doing the tests. I haven't said at any time that I haven't read the tutorial.
I could made a mistake cloning the ram disk, just to have a backup, but it doesn't mean that I'm a fool. Well, at least I don't think so about my self. Again a sunny winter day here, that's usual in this part of South Europe and, to be honest ;), it contributes greatly to keep the mood. Kind regards Juan Title: Re: How to make persistent changes in the BASE versions? Post by: PeterSt on February 05, 2016, 12:49:28 pm Juan, nobody said you are a fool. Maybe you feel like that ?
Even if so, nobody is saying that. You can not use the clone, exactly for the reasons you layed out nicely. Well, without you understanding it, which is exactly the problem if you use a clone; Then you can't understand what is happening. Use the original and your eyes will open. Bet ? Regards, Peter PS: It is that "bad" with using a clone that even I have difficulties in understanding what you will see. From there easily sprung my "you didn't read the Tutorials". So I have to withdraw that - apologies. Just look at the original and then you will understand yourself how easy it is to see that nothing of the Tutorials was followed. Your questions would be "n/a" ... Title: Re: How to make persistent changes in the BASE versions? Post by: juanpmar on February 06, 2016, 12:55:23 am Peter, I could finally set my system up correctly. It is definitely the best sound so far. Congratulations once again.
Regards, Juan |