RDP and XXHE aren’t compatible on my Win 7 PC

[DannyD]

This is a bit long and involved, but please bear with me.

I remote control my PC with my macbook pro (using remote desktop connection) and my ipad (using jump desktop).

Both don’t work in exactly the same way.

The initial connection works fine but I often can’t reconnect even once, and almost never more than once. I have to reboot the PC and then I’m okay for the first and sometimes second connection, but then it stops reconnecting.  I’ve been living with this with my MBP because I don’t have to reconnect very often.  I just leave the connection up in a window.  But if the connection breaks, I usually can’t reconnect until I reboot the PC.  The iPad is another story.  Since it doesn’t multitask, I want to disconnect and reconnect a lot: every time I used the iPad for something else (e.g. Safari). 

This is not new to 0.9z.

It works fine if I’m not running XXHE.  It even works fine if I’m running J. River. (It doesn’t realize how bad it sounds in comparison!)  I can connect and reconnect all day long.  So you see why I’ve concluded it’s a problem with XXHE.

I also have a Vista machine, and it works fine with that.  I can reconnect at will, making the iPad a lovely remote control and more.  But it’s my second (and clearly inferior) system.  Where’s the joy in that?

Any idea of what the problem is or how I can troubleshoot further?   I appreciate your help.

Dan

[Calibrator]

G'day Dan,

When you play XXHE are you "stopping the services"? If so, try again without that option ticked.

Do you have problems in both attended AND unattended mode?

Have you tried alternatives to RDC? RealVNC comes to mind.

Cheers,

Russ

[DannyD]

Russ,

I like the way you think!  I too reasoned that XXHE must be killing some process or service that is necessary to recreating the RDP connection.  I played with the "stop services" setting before and did it again just now and it didn't make any difference.  I mostly use attended mode anyway.  Believe it or not, I can't find an alt key on the iPad!  Anyway, I do think it is that XXHE is killing a necessary process/service.  But which one?  I'm hoping Peter has some ideas.

When you suggest other protocols, I'm really looking for something that will work on the iPad.  That's my only limitation.

Thanks  again, Russ.
Dan

[PeterSt]

Dan, keep in mind the behaviour Vista expressed at using XXHighEnd (although that may be before your times here). Thus, because XXHighEnd eating all the resources, all kind of services shut down automatically, but with a message telling so. I am not sure W7 does this too, and in anyway I have never seen the messages about it.

You might investigate which services belong to RDC (because you can shut RDC off), and next look whether they have stopped when all stops working. If they stopped, well, then we at least know that. What to do with it next I don't know yet.

Peter

[DannyD]

Can anyone confirm that remote desktop is working for them on a Windows 7 PC when XXHE is running? 

My details are that I’m connecting to my PC wirelessly from both a macbook pro (using remote desktop connection), and an iPad (using jump desktop).  Everything works fine unless I’m running XXHE on the PC.  Is this working for anyone who is running Windows 7 (ultimate, 32-bit in my case)?

Thanks for your help!

[earflappin]

Danny, as I mentioned in my e-mail to you (just thought I would throw it up here in the forum) I had the exact same problem you are having....i.e. you cannot re-establish a RDC connection to the Win7 server once you have run XXHE.  I'm not sure if is the stop/start services or the CPU assignment stuff Peter does.  I did not have any issues with JRMC or Samplitude.

Father, forgive me for I have sinned.....I have abandoned PC/Windows/XXHE/AES/Berkeley Alpha DAC for Mac/OSX/Pure Music/Firewire/Metric Halo LIO-8....  I'm sure Peter is continuing to ensure XXHE remains the top player for Windows....now if he would just get his NOS1 DAC to market...

[PeterSt]

I too should add here, for the forum - and after a couple of PMs with Danny, that by now I am looking into this (which I actually never did).

Hey David, that is ok. If you are only sure you listened to 0.9zb, because the difference is rather huge ...

Peter


PS : An update on the NOS1 is to follow soon.

[PeterSt]

Ok, I am as far as this :

I am not sure the Wallpaper settings are related, but maybe they do; when I shut them all off (including OSD stuff) I was able to start XXHighend and disconnect - reconnect (btw, LogOff/On doesn't seem to make a difference).
I also removed the normal wallpaper (and now have a fixed color instead).

The real issue seems to be *or* the Core Appointment settings other than "No Appointment" or either or both of the Priority settings. Set this all to NoAppointment / Nothing respectively (and reboot after that), and it works.

After 20-30 reboots I seem to know enough now : it can't be solved and is a W7 bug. Ok, it can be solved at the moment by not using the exactly whatever it is (see above), but I am not sure that is a real solution. But if it is, it is just there already.

Since I give up for the moment, if someone determines (by accident or explicitly) what it exactly is that holds this back, please let it know.
In either case I would start with the Appointment and Priorities, and if that doesn't help, do the Wallpaper things as well.

Sorry for now !
Peter

[DannyD]

Oh my God! You're a genius!  I want to have your children!     It must have been a busy day of posts on phasure and your post quickly rolled off the main page, so I didn't see it.  Thank you!  Since my CPU hardly every gets above 1% (adaptive/1024) I'm really not losing anything sonically by not setting these parameters, am I?

Speaking of posts of phasure, I'm drooling over today's on the NOS DAC.  Are you taking orders or at least reservations now?  Will you be making a US (110V/60 cycles) version right away? And what interface will I need?  I currently have a Lynx card and a jkeny-HiFace.

Dan

[PeterSt]

Haha, so I take it that works for you too ? But remember, it is not a real solution.

The Phasure NOS1 will be for 110V allright, if I only know it in advance (which is very likely hehe).
You can store the Lynx and the HiFace somewhere; all what is needed will be in the box (but the box is still under construction ).

Thanks Dan,
Peter

[DannyD]

I've done some testing and have found that the only setting that matters is the Core Appointment Scheme.  As long as I leave that on "No Appointment", I can set the other settings however I want and RDP continues to work for me. 

[PeterSt]

Yo Dan !

I am kind of finalizing 0.9z-3, and was up to this one. But, at this moment my network connection is broken from the audio PC, so I can't test it anymore (that being the only W7 machine I have). So I wondered, if you can test something for me ... It must be in this exact sequence though ...

0. Do NOT have the RDC (RDP) connection (not even once after a reboot).

1. Set the Appointment scheme in XXHighEnd to what you like (preferrably the Scheme you used before when all didn't work);

2. Be prepared for Unattended, but set Stop Services Not active, and Show Wallpaper also Not active (this will give you access to the deskptop lateron - see below).

3. Click Play.

4. Establish the RDC connection. Notice that maybe already now you can't get it to work. In that case here it stops, but let me know.

5. When it works, bring up XXHighEnd again. Don't touch anything further yet.

6. Start TaskManager (you can just as well have it running already) and kill Engine3.exe.

7. Click Play again.

If now your connection is still there I can solve it theoretically. Practically I don't know yet.

If it stopped somewhere I don't know what to do to solve it. If you have connections to Bill Gates maybe give him a call. I think he's out of a job anyway.

But let me know ...
Peter

[DannyD]

As always, I can't get past step 4.  Once I have XXHE running with an appointment scheme set, I can't connect with RDP.  Why did you think it would be different this time?  Maybe I'm not understanding you.

[PeterSt]

Hi Dan - I think you understood me always allright, but why would you have applied the sequency I just presented to you ?
So if you now did ... I have no solution for it, other than a Windows 7 SP which solves it (like it just works in Vista). I 'm really sorry ...



But who is going to tell MS about it ?

[PeterSt]

Why did you think it would be different this time?

Dan, I have been thinking about this again, and I am not sure whether I offended you somewhat, or that you maybe didn't apply that exact
sequence, which is the most strange - and I can imagine you ever did something similar before.

So, this is about the CHANGE of Affinity (and stuff you can't see yourself) which this sequence avoids. Thus, by starting RDP - that process later nog changing anything for these matters, it could be solved;
If you applied that exact sequence (which actually should start with a reboot), then it's clear ... it doesn't help.

So, what's left is that the OS allows the change of these things (Processor Affinity and more), while it can't bare it. This can be two-folded :
1. In Vista (etc.) it didn't allow the changes and therefore all was ok, while now it does allow it but can't bare it (and never could) and/or
2. In Vista it could bare the different Affinity etc., while now it can't anymore.

This still theoretically allows for a solution from my side, namely, leaving the particular proces(ses) alone. But, at this moment I can't see those processes (I think) because my (mobo) Ethernet adapter took an early retirement. In any case I already know that many processes can't be identified, and if this one is amongst them, I don't know which one to leave alone (look at the serveral "host" processes which all have the same name).

When I have a network connection again I can look into it further.
In any case, sorry for the inconvenience ... but it's not my fault.
Peter