Gerard,

You put the lot in
c:\XXHighEnd\

not in
c:\XXHighEnd\xx\

that's why.

  Oen

So if you look at the XXHighEnd.exe in that folder, it should have a date of end 2017 or something like that. Run that, and you will see it is 2.10.
… But you probably won't find that end of 2017 version in there and thus you unzipped it somewhere else.

?

Peter

Yes, interesting.

At this moment I don't think that any software can really influence what you are  talking about, and where it can, it has been done already (this is mainly in the XTweaks section, although not explicitly visible - the result depends highly on the combinations in there).
But what I would do (and btw, do indeed) is look into the BIOS settings, the C States and how they cause "interaction" at various levels. So, I would look into that anyway, and whether (API) code exists for that … I wonder. But it surely could exist. Point would be that it always would require a reboot to change those settings.

Best regards,
Peter

Hi Gerard,

Yes, but the horizon is somewhere a the end of the rainbow.
But Yes.

The XX folder for the RAM-OS Disk is *always* in the C:\XXHighend\xx\ folder.
So fo 10586.0 too, as long as you booted into that (and you should with upgrading).

Yes, unzip the patch for 2.10 over it.

Regards,
Peter

Hi Anthony,

Scrollbars are a waste of space. But if you are more happy with them, please go ahead.

I know the resolution is too high for a small laptop screen to be readable. I also honestly don't know who wants to buy that if at the same time the advice is to set the text to 200%. So Yes, that all is clear to me.
That things don't match now was to be expected (and you found out).
I don't know … maybe if you set the Music Server PC also to 200% ?

I do NOT have any good reason for having XXHighEnd full screen. However, any tablet is already fairly small for physical size, hence our thick fingers. So the larger XXHighEnd can be, the better it is for the physically more small screen.

Btw, I always have XXHighEnd not fully full screen because the XXOSK must be visible somewhere, so it can be selected if needed (by touch screen). Yours is set horizontally (so must go above or underneath), mine is square, so will go besides for a small piece (see below).

… And you can use the in the right-hand edge to remove (or set-back) the border from XXHighEnd (drag by means of grabbing empty space).

Peter

Hey Anthony,

What I miss is the [2] slider. Well, in Before.jpg you can barely see it in the top-right corner. I would drag that leftwards to begin with. It may not help, but it may help determining what is going bananas.

A good idea for all RDC connections is not to use the normal RDC-Edit for it, but to rightclick on the icon and choose notepad (find Open With Notepad from the context menu which appears after the rightclick.

See the attachment; It contains a few examples with comment about very generally what can be done in there, but *always* keep on using notepad from now on, because the normal Edit function will kill your changes (the to be saved settings are way more rough in there).

Keep in mind that it is a play between the Music Server PC which controls (via RDC) the Audio PC and the tablet which in itself controls (RDC) the Music Server PC.
None should have scroll bars, ans none should have eggs for wheels. It all can easily be done, once you get the hang of it. ... I am just thinking ... Here is the part of concern of my Music Server PC (RDC to the Audio PC) :

screen mode id:i:1
use multimon:i:0
desktopwidth:i:1366
desktopheight:i:768
session bpp:i:16
winposstr:s:0,1,129,53,1425,859

The winposstr may do nothing (I forgot). The 1366x768 definitely is the size of my Surface (V2 IIRC). So set that part to what the Surface will be able to do.
Always keep the font size (Windows Monitor setting) at 100% everywhere.

You probably will end up with all too small to touch. Solve that with the Scaling functionality of XXHighEnd (set to 2.30 or so via de button near the bottom of the main screen.

I hope you can get it done ...
Peter

Bert, then "the" idea is too much of your idea. It is not mine.
The remainder is correct.

Peter

PS:
That looks like an odd a. observation or b. a desire.
Which is it ?

PS: If I misunderstood, then please say so.

Hey Bert,

Tidal is not supposed to work on the Audio PC itself.
Maybe if I myself would try a bit harder I could get it going, but for starters and not to forget : the Audio PC does not have an Internet connection. That is, it shouldn't have.
Thus :

Prepare (Tidal albums) on the Music Server PC, play at the Audio PC as usual.

Best regards,
Peter

Dear Friend,

So nice to hear that you got it all running again after your "long story", that you held on and that your expectations worked out.

Best regards to you and your family !
Peter

Ramesh,

Can you make a photo of the inside and the USB connectors involved ?
Make the photo from say a 45 degree angle so we can see what wires are there (wires from connector to connector). And only the USB connectors in de left leg.

Can you do that ?

Peter

Hi Shreekant - I am very glad that you could solve the problem by yourself. Well done.


There are no settings in the DAC so I can't understand what you mean by this ?

Kind regards,
Peter

Maybe if you go to Normal OS mode, and re-install the NOS1 Driver things start to work again ?
When you boot into 14393.0 BASE (don't forget to go to Normal OS), the Driver will be on drive D:.

I suppose it won't matter, but use an other album to rule out it is the album causing this.

Regards,
Peter

Hi Nick,


I am afraid that I had read that, but this is exactly the part that doesn't make sense to me.
You imply that you connected measurement wires to the d+/d- pads somehow (how ??) and you say that you move *the* (??) cable near *the* ?? connector and that this influenced the resistance.
For me this is 3 parts I each don't understand.
And oh, I am not saying that something is not - or can't be true … I just don't understand.

You seem to move the cable in a magnetic field and then the resistance changed ?
… So now you'll understand how I read your text, OK ?

Peter

Shreekant, if the USB cable is not broken (so please try an other !), then something else seems to be broken. Not good.
If I were you I would also connect the NOS1 to an other PC and see whether it still can play without that error.

Keep in mind that I told that it can also be an odd changed XXHighEnd setting.

Lastly, if you remove the cover so you can clearly see the green led in the left leg, what do you exactly see happening when

- The PC is up and running;
- You pulled out the USB cable (DAC side);
- You started the NOS1 Driver Control panel;
- You put in the USB cable.

Notice that the led may show blinking states, or that it can remain off, or may be on continuously.

Also, when the cable is in, tell me, or show me the bottom line of the Driver Control Panel (like Streaming is Down and that kind of messages).

Peter