XXHighEnd

 Last week my audioPC started acting up, and instead of finding the problem I decided to ditch Win10 10585 and start over with a clean slate with win10 14393.

After I got all that running, I decided to start using a RAMdisk.
I had never done this before, but as I am rather lazy, I thought to streamline Peter's process a little.

So I rewrote parts of his Rama.bat file, and this resulted in RAMDisk_XXHighend.cmd (attached)

I put a link in the start-up folder so  if all goes well:
- at boot the XXhighend control panel is started. (Peter put this link in himself)
- at boot two RAMdisks are created.
- all needed XXHighend data and software is copied to these two RAMdisks.
- XXHighend is started in RAM.

This works well in MAXos, but for some reason not so peachy in MINos.

So now I wonder, what am I doing wrong? Is anybody willing to take a look at the cmd file and suggest improvements?

Sidenote:
Before this cmd file can be used, I need to create the RAMdisks once, otherwise I can not make the necessary changes to the XXhighend settings before I start using the ramdisk version.

Regards,

Henk

Hi there Henk,



I suppose you can guess that this is hardly a description I can deal with. Agreed ? haha



That. Your lazyness is fine though. :)

I am not sure whether you read / used this topic :
Installing and using a RAMDisk (IMDisk) (http://www.phasure.com/index.php?topic=2915.msg30750#msg30750) but notice that at the bottom in there there's this link which includes a RAMA.bat.
If you already used that, then I suppose your problem is that you removed the aiding texts from it, so now you don't know what to do any more (?). Anyway, I'd keep that A: en B: drive the same because otherwise the drive letters may be occupied (A: and B: never, unless you you still use floppy drives :whistle:). Now you can not make mistakes if you follow the "guide".

I don't know better as that this works for everyone, also in MinOS.

Best regards,
Peter

Hi Peter,

Thanks for the quick response. It's not exactly what I had hoped for though....

Of course I have read your Ramdisk topic, otherwise I would never have gotten it going.

And of course I used your rama.bat, it says so in my original post in this topic.
And if you compare your rama.bat with my command file, you will see that they are very similar.

The reason I am not using A:\ and B:\ is quite simple. Both these drive letters are used on my music PC, and shared on the network with the same drive letter on the audio PC.

Is the drive letter significant? If needed I can change them, but I never saw the point.

My only concern is:
- Use of Ramdisk, as you describe it works well, both in MAXos and in MINos.

However:
If I reboot in MINos, my own .cmd file does not work as intended. It either never even starts copying files to the E:\ drive, or it does it way too late.

Yesterday I rebooted the pc in MINos.
After 3 minutes I got fed-up, used your procedure to start up two RAMdisks manually, and started XXhighend in RAM, and had Music.

15 minutes later, a command window pops up, which shows files being copied to the E:\ disk and it too starts up XXhighend in RAM. This all happens while I'm playing music in MINos, with the Ram XXHighend that I had started manually.

So now I have XXHighend running twice, which obviously causes problems. I can not remember when exactly I got the error message in which I am asked if I want to keep running both or not, but of course that message also appears.

The only answer I am looking for is:
Why does it take 20 minutes for my command file to run, it is called in the same startup folder as your XXHighend Control Panel, so I expect it to run immediately after boot?

Could this be caused by a difference between MAXos and MINos which prevents all links in the startup folder to be executed?

Regards,

Henk

Hi Henk,

I was referring to the topic and the consistency plus the help in the .bat itself, so you could not make mistakes. That is all.

And that you very clearly do not at all what's in that texts, is also clear, right ?
In other words :

If you think you can automate things, which for a reason is not in any help or topic described, you are on your own. Also, might you be able to find the topics/posts of concern about automatic start etc., you will see that I explicitly NOT advise that. So you can do it, but now it is *you* who must know how. And strangely enough, there it goes wrong. Funny eh ?


The service taking care of these things won't run. Later it might start for other reasons (decision of XXHighEnd) and again later it will shut off again (XXHighEnd again). And then later it will start. And so on.
Good answer eh ?
haha

In Normal OS all services just happily run, so there you can't have the problem.

Now, follow the procedure as I have written it, be a bit less lazy and all will be fine. OK ?
:)
Peter

PS: Another advice : don't try to force that (whatever) service to run because it will be one big mess. I promise !

Peter, This was exactly the answer I was looking for. I had expected something like this.

So all I need to do is start my command file from the desktop after boot, and I am fine.

It would be nice though if I could just boot the machine and start playing...

Yes Lazy You. That is why I never shut down any PC wherever I am. :)

Best regards,
Peter