On Thursday 30 October 2003 12:12, Damon Register wrote: [stuff deleted]
The problem is that this seems to be a very recent development. In trying to find that kdenetwork3-vnc that a few mentioned earlier it appears in a more recent kde than is with SuSE 8.0. I am not an expert here but I suspect that one cannot take a module from one version of kde and stick it into an older one. Therefore I would likely have to upgrade kde which seems like a difficult task. From all of the kde upgrade discussions I have seen here in the past, I don't think I want to tackle that.
While it might very well outdo XP out of the box, I am still disappointed that it took so long to get to a point that has existed in Windows for years.
Even though my SuSE 9.0 may arrive soon and this issue might be overcome by events, I can't accept being beaten so I will pursue this. It seems that xf4vnc is the only hope for older kde that doesn't have kdenetwork3-vnc. If anyone has had experience with xf4vnc with display :0 on SuSE, I would like to hear from you.
Damon Register
You are going to have to upgrade something somewhere to get access to :0 with VNC on a SuSE 8.0 box anyway. You are either going to have to upgrade KDE or XFree86 one. You can use VNC or XDMCP either one with what you currently have but not on :0. XF4VNC, while I haven't used it, has some special instructions for pre 4.3 versions of XFree86. You obviously won't be running a 4.3 version without an upgrade to XFree86 with SuSE 8.0. I can't remember what version was with 8.0, I do know that 8.1 had XFree86 4.2, so it isn't likely that 8.0 had XFree86 4.3. As to getting to a point that has existed in Windows for years, I was doing remote X sessions long before I could do remote Windows sessions. Remote X sessions go back to the beginning of X without any additional software required, while remote Windows sessions only arrived with WinXP (without any additional software required) on the desktop. There have been things like PC Anywhere, Citrix, Terminal Services, but they were additional or server machine functions, not desktop. The early remote desktop access in X was no to :0, but it was remote X none the less. I actually find much less need to be accessing the desktop than I do to just have access to the machine remotely at any rate. Accessing the desktop is only useful to show someone how to do something. There is much more that can be done on remote X sessions. -- Kelly L. Fulks Home Account near Huntsville, AL