XP's RemoteDesktop is not inhibited in any obvious way (that I could
determine) and is based on Terminal Services.
It is excellent!!
==============================================================
ASB - http://www.ultratech-llc.com/KB/?File=~MoreInfo.TXT
==============================================================
"Errors have been made. Others will be blamed."
>-----Original Message-----
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]]On Behalf Of Patrick Sweeney
>Sent: Tuesday, August 21, 2001 12:29 PM
>To: NT 2000 Discussions
>Subject: RE: software v.s hardware emulation - More Info
>
>
>There isn't.
>
>They conflict - end of story, don't waste your time. I've
>been there on
>this one. (I haven't tested XP's RemoteDesktop Functions
>but I expect the
>same. It limits us, but not in an entirely bad way. It has
>shelved a
>harebrained scheme to scrap WTS farms in favor of having
>users VPN in and
>then Remote their own desktop.)
>
>Explore third-party remote control options, I have a
>personal preference for
>anything that can be effectively managed from a central server.
>Unfortunately I usually use SMS remote control for this
>reason, and it has
>the same issue with DirectX. PCAnywhere can use NT
>Authentication, but it
>the settings are managed per machine, and logging is per
>machine. I have
>not investigated if there is a means to centrally manage
>configuration of
>VNC, but I can attest that it is a solid little remote
>control tool. I've
>used it to manage my Parent's machine from a variety of
>devices including
>both my Palm and an IPAQ.
>
>
>Venting
>I can understand your frustration but you imply that being a
>single company
>should preclude conflicts. I don't disagree that Microsoft
>should work to
>make their products work together, but with a product base
>as large as
>theirs conflicts are inevitable.
>Being one company in no way precludes the release of
>conflicting products.
>In this instance you have a set of functions which has been
>seen as a luxury
>for gamers - DirectX. Then you have a set of functions
>which is seen as
>useful for peer-to-peer document sharing and enterprise
>support. If those
>assumptions about these functions were accurate then there
>would not be much
>of an intersection.
>
>Of course, the assumptions, especially about the utility of
>DirectX, are
>innaccurate. We have business uses for it. That doesn't
>change the fact
>that DirectX and Remote Desktop don't play together.
>
>
>
>
>
>
>----Original Message Follows----
>From: Avi Smith-Rapaport <[EMAIL PROTECTED]>
>Reply-To: "NT 2000 Discussions" <[EMAIL PROTECTED]>
>To: "NT 2000 Discussions" <[EMAIL PROTECTED]>
>Subject: RE: software v.s hardware emulation - More Info
>Date: Tue, 21 Aug 2001 11:01:32 -0400
>
>yeah but then how can I connect to the machine afterwards.
>It seems weird that ms would come out with two conflicting products?
>there must be a way for them to live in harmony so that you
>can use both at
>same time?
>
>
>
>-----Original Message-----
>From: Ryan Malayter [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, August 21, 2001 10:56 AM
>To: NT 2000 Discussions
>Subject: RE: software v.s hardware emulation - More Info
>
>
>I think you answered your own question. Turn desktop sharing
>off... <SNIP>
>
>-----Original Message-----
>From: Avi Smith-Rapaport [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, August 21, 2001 6:23 AM
>To: NT 2000 Discussions
>Subject: software v.s hardware emulation - More Info
>
>
>I need some help here.
>Running a Win2k Pro SP2 system with remote desktop sharing enabled
>(netmeeting), with a 32 meg nvidia mx geforce video card,
>but when I run
>direct x diag under display and directx features, direct x draw
>acceleration, direct 3d acceleration and agp texture
>acceleration are all
>greyed out and not accessible. any thoughts?
>
><SNIP>
>
------
You are subscribed as [email protected]
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe send a blank email to [EMAIL PROTECTED]
