[pmrid (Peter)]

This is one for the 'automators'! I've been able to push my wireless network out to my observatory - the idea being to save freezing my buns off in winter by controlling things from the house. Good in theory. No problem getting remote access to work. That's easy. But I have come up against a real mission-critical problem with using it while imaging/guiding.
I use PHD to guide and Nebulosity to image. But I have noticed that I get a lot of guiding errors - subs I have to scrap - when I try to operate remotely. I have started to monitor the circumstances in which this happens and there seems to be a direct correlation between when I log into the imaging computer remotely and when guide errors occur. Leaving the graph function of PHD running seems to confirm that after guiding away happily within quite decent parameters, whenever I log in remotely, there are major Dec and RA guide errors.
I have also noticed that Nebulosity can be a real resources hog at various times during the process of imaging and downloading.
My feeling is that this is what's causing the problem - remote login demands instant resources from the remote CPU/RAM and Nebulosity is hogging it so it comes a the expense of PHD.
I'm running XP SP3 on a 3GhZ PC with plenty of RAM.

Anyone else seen this or something similar?

Peter.