Hi Ramesh,

This is strange... I did reverse the long and short Clairixa, but the problem was still persisting... I have tried with the long Clairixa and a blue USB cable (shorter, but still ~ 40cm) and the same was happening. I could have tried more USB cable (not that I have so many of them), but when shutting the NOS1 OFF then ON was the remedy (until the next boot).

I normally leave the NOS1 ON almost all the time, except when I leave for a few days or at least once a week, with the rest of the chain.

Not having this problem before made me wonder... The Silverstone PCIe USB 3 controller card does not seem to exhibit this kind of behavior. so I imagine that the power is more stable and strong to not act that way...

Anyway, this laptop is a temporary solution. I already miss not being able to load all in ram For the moment, while it seems to be sensitive to power, the Intona is an important addition to all the SQ that we get from XXHIghEnd, NOS1, Clairixa, the os-ram drive and Intona, I feel so comfortable "Lonely at the very top" like it is written on top of the forum

Regards,

Alain

Hi Pedal,

Maybe the first question to ask would be "What cable do I need to do this ?". One with a connector that would fit in your tablet, one that would have the standard protocol to connect either in a USB port on the dedicated PC or through a USB to ethernet converter of some sort. It would require some searching to see how other are doing this.

Another way to do it would be to use wi-fi between your tablet and the PC, but there may be a "cost" in SQ - I don't know... There are tools to connect on a PC, something that would look like the Remote Desktop Connection.

It is the old "convenience vs compromise"...

Regards,

Alain 

My Audio PC (with XXHE and os-ram drive) is actually down, so I am actually using a Toshiba laptop that has some years under the belt (8GB ram, i5 (4 cores), USB 2 ports only. At least I can use a ramdisk like I was using prior to the os-ram drive, but I have to reduce the memory allocation to make all work. I use Windows 10 build 10586.0.

I use 2 Clairixa USB cables for the links between Laptop > Intona > NOS1, same as I do with my Audio PC.

To my surprise, there is something odd happening. Whenever I boot (same if I restart or do a shutdown then start Windows), I need to turn the NOS1 OFF then ON again. I would like to try disconnecting one of the two USB cables, but I feel better to turn OFF the NOS1 instead. Not that I think it is good, but I am quite sure that there is DC offset when playing with cables. So...

That was not happening with the Audio PC, but the big difference is that the Silverstone PCIe USB 3 card that I use (like many others) does not seem to require that kind of intervention. I never had to turn the NOS1 OFF then ON when booting.

I believe this has something to do with the Intona. In Computer Audiophile forum, there has been lots of reports about a certain sensitivity with the Intona USB 3 Isolator... It is also said that Daniel (from Intona) is looking for a solution about these situations.

But of course, as soon as I get my Audio PC back, all should be ok again.

I can't point the culprit - USB 3 vs USB 2 ? Has someone tried this with a USB 2 port right from the motherboard (not a PCIe USB card) ?

Regards,

Alain

Hi Stanley,

I am happy that things work for you

It is certain that a process of some sort (or more than one) is responsible for that behavior under Normal OS, but once in Minimized it is stopped so a different behavior

Regards,

Alain

Hi Stanley,

When you are playing unattended, are you in Normal or Minimized OS ? I now recall that disconnection was happening when attempting to play unattended in Normal OS mode... This could probably be because some processes (that are normally shut down in Minimized OS mode) are having this consequence... ?

I have to admit that I ensure Defender and the Firewall are not active though...

Regards,

Alain

Well yes it is quite early. Even birds are not singing already, but they are probably getting dressed for the cold and having breakfast

Alain

OT... My audio PC decided to fail on me... it does not start anymore. Don't know what is happening (PSU, motherboard, ON/OFF switch... I will sing in the meantime, but I already know that the SQ will be baaaaad...

Alain

Hi Juan,

Can you express more details about the noise(s) that your server makes ? This may help to find a solution, even if getting a silent computer could solve the problem...

I don't know if this would be of some help, but if you install XXHighEnd on the server also - just to use its Minimize OS capability, maybe the server will also be less noisy ? It normally allows to reduce the CPU clock speed and turns down a lot of processes and services, so it should require less ventilation ?

Peter, am I right to assume that we can install more than one XXHighEnd software without having to pay for a second licence ?

Alain

Could it stand for NOS1 "barebone" ? Maybe Bert will squeeze the NOS1a in the PC case, eliminating the need for a USB cable

Alain

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

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

I have had this problem recently and in my case it seemed to be related to the date.

Since I only intend to use Win 10 build 10586.0 from the os-ram drive, I have ajusted the date to be the same as my server and this hasn't occured since.

I must add that I rarely play more than just a few songs at a time in unattended mode. Sometimes it is a mix of things that triggers these situations, but on the other hand, maybe nothing of this is related...

Alain

Peter,

You nailed it ! My room is not "absorbent" and I also feel that things are more defined that way...

I never really thought things that way, but you spoke my mind.

Alain

Hi Steve,

I noticed this in Windows explorer, so when I rip my CDs, I always ask for the tracks to be numbered with a 2 digit mask, like:
01 xxxx
02 dddd
03 aaaa

I exceptionnaly had to use a "999" format once, since the download was containing more than 100 songs... 001, 002, 003, etc...

You may not like that numbering in certain situations though...

Regards,

Alain