From: <jh...@ne...> - 2004-01-26 14:48:33
|
Hi, I have found this site today, and I haven't a clue of what is being discussed here. Of course, I can get tons of computers etc' and load them up with the software and see what it does, but then again, it would be so much nicer and easier if someone could just tell me so I could know if it is worth the hassel. To be honnest, the previous paragraph is somewhat metaphoric, because I can understand that there is a Remote Desktop, and this in itself explains a bit, but: 1. Is this remote desktop separate and different than what the user on the server sees? Or are they both in the same desktop fighting over the mouse? 2. I undestand you provide the client side. What about the server side? Where can I get a server side? 3. Are there minimal hardware requirements for the client computer/ the server? 4. Can the client see TV say if the server has a TV card? 5. Can the client play 3D games? 6. Can the client watch movies which are on the server's disk? 7. Can the client listen to music which is on the server's disk? 8. What is the needed network bandwidth? __________________________________________________________________ New! Unlimited Netscape Internet Service. Only $9.95 a month -- Sign up today at http://isp.netscape.com/register Act now to get a personalized email address! Netscape. Just the Net You Need. |
From: Mrs. B. <mrs...@ni...> - 2004-01-27 12:40:09
|
On Sat, 2004-01-24 at 10:01, Jhony wrote: > Hi, > I have found this site today, and I haven't a clue of > what is being discussed here. Of course, I can get tons > of computers etc' and load them up with the software > and see what it does, but then again, it would be so > much nicer and easier if someone could just tell me so > I could know if it is worth the hassel. Chances are, you won't be using rdesktop unless you know that you will be using rdesktop (or at the very least, your network administrator would know). > 1. Is this remote desktop separate and different than > what the user on the server sees? Or are they both in > the same desktop fighting over the mouse? It _can_ be. With MS's implementation of RDP it _usually_ is, and yet MS's TS has options for "taking over" a users desktop, as well as having support for "remote assistance" where this is the default option. > 2. I undestand you provide the client side. What about > the server side? Where can I get a server side? It is packaged with Windows 2000 and later versions. There may be ways to get it to run on other systems. > 3. Are there minimal hardware requirements for the > client computer/ the server? Yes. > 4. Can the client see TV say if the server has a TV card? That depends. As a question of ability? yes. I'm not so certain you'd be using rdesktop to do this, however. > 5. Can the client play 3D games? That depends. As a question of ability? yes. I'm not so certain you'd be using rdesktop to do this, however. > 6. Can the client watch movies which are on the server's > disk? That depends. As a question of ability? yes. I'm not so certain you'd be using rdesktop to do this, however. > 7. Can the client listen to music which is on the > server's > disk? That depends. As a question of ability? yes. I'm not so certain you'd be using rdesktop to do this, however. > 8. What is the needed network bandwidth? That's a silly question. RDP is an interactive protocol. You can have a DS3 and still be "too slow" for RDP if your latency is too high, and likewise, you could use a 1K/sec link and be fine if your latency is low enough. Anyway. I'll tell you that none of these questions are in the most FAQ; those are usually broken down into: * International keyboard issues * Support for redirection * (up until recently) Sound, and hicolor support * Problems with their own X11 system * Problems compiling * Wanting an RDP server for Linux but really; most people who have found rdesktop already know what they need it to do- to stop buying another copy of pcAnywhere, another copy of Windows, to stop using VNC to connect to a windows box to use TSAC to connect to a windows box, and/or to stop switching displays, etc. And of course, the FGA's are: * Have you tried the newest version? Can you supply a patch? * Not yet, but we're working on it * .... * Have you consulted your systems' documentation? * Have you consulted your systems' documentation? * You have no idea what you are talking about. |
From: Matthew T. <te...@ya...> - 2004-01-26 20:09:49
|
I worked on a FAQ for a while but never got to submitting it... I may finish and submit it soon... I just need reminders, as I get carried away with other things I'm doing. (BTW: I'm just a user, but I use it on a 30+ machines at three different organizations). Let me answer some of your questions.. This is largely for my own sake, I want to know about what people are asking, so I can know how to better support my customers when they have the same queries: --- Jhony <jh...@ne...> wrote: > 1. Is this remote desktop separate and different > than > what the user on the server sees? Or are they both > in > the same desktop fighting over the mouse? No. If you are using Terminal Services, each user has his/her own home directory under C:\Documents and Settings\user (replace "user" with the user name). And each has his/her own Desktop subdirectory, etc. Even if you login the same user twice, they have their own cursor and apps loaded...but just share the same home directory. It's not like VNC. I think RDP becomes more and more like X, as time goes by... One advantage of RDP, however, is that your session can remain persistant.. In case you get disconnected, your session is waiting for you, just like you left it. That's virtually impossible with X, unfortunately. On the other hand, X has numerous advantages over RDP--better scaling and local 3D hardware exceleration, for example. > > 2. I undestand you provide the client side. What > about > the server side? Where can I get a server side? > It's intended to provide a GNU/Linux or UNIX-based client to Windows Terminal Services. A GNU/Linux based compatible server is an interesting idea.. But the developers here, have still got a lot of work to do, reverse engineering the whole protocol. I imagine, it'll always be that way.... As Microsoft continues to improve RDP. For example, RDP 5.x (requiring Windows 2003 Server) now provides better than 8-bit color resolution (16 & 24). > 3. Are there minimal hardware requirements for the > client computer/ the server? > It's incredibly small and simple.. Look through the source code.. Very well written, too. Requirements are likewise, as minimal as one could reasonably imagine. > 4. Can the client see TV say if the server has a TV > card? Amazingly, I have played videos and Java-based web games at my Cyber Cafe, over it. RDP does some local rendering, but those type of things are obviously just bitmaps going over the network. I would not recommend full screen at high resolutions, unless you have 1 or 2GB xfer speeds. > > 5. Can the client play 3D games? > No.. I doubt this will ever be possible. DirectX is not portable. > 6. Can the client watch movies which are on the > server's > disk? > > 7. Can the client listen to music which is on the > server's > disk? I think so, but never actually tried this. It's not a problem with X. In fact, X has a owesome module called, MAS, which basically tunnels other sound protocols and makes them seemlessly peer-to-peer distributable for good quality sound over low latency and overburdened connections. > > 8. What is the needed network bandwidth? > > __________________________________________________________________ > New! Unlimited Netscape Internet Service. > Only $9.95 a month -- Sign up today at > http://isp.netscape.com/register > Act now to get a personalized email address! > > Netscape. Just the Net You Need. > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and > Integration > See the breadth of Eclipse activity. February 3-5 in > Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > rdesktop-users mailing list > rde...@li... > https://lists.sourceforge.net/lists/listinfo/rdesktop-users __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it! http://webhosting.yahoo.com/ps/sb/ |
From: Mrs. B. <mrs...@ni...> - 2004-01-30 21:53:46
|
On Mon, 2004-01-26 at 15:09, Matthew Tedder wrote: > It's not like VNC. I think RDP becomes more and more > like X, as time goes by... One advantage of RDP, > however, is that your session can remain persistant.. > In case you get disconnected, your session is waiting > for you, just like you left it. That's virtually > impossible with X, unfortunately. On the other hand, > X has numerous advantages over RDP--better scaling and > local 3D hardware exceleration, for example. FYI: X has network-transparent 3d (GLX), and it _is_ possible to save/restore X sessions (including moving them to another screen or display) using a program called xmove, but also supports display multiplexing (xmx) which is really quite useful for giving presentations. > > > 5. Can the client play 3D games? > > > > No.. I doubt this will ever be possible. DirectX is > not portable. Well, it _is_ possible. As far as MS is concerned, RDP is simply a wrapper for various MS RPC calls against the display. There's no technical reason DirectX could ever be added to (Say) RDP 6.0 |