Puppy Linux Discussion Forum

[rarsa]

Here is the tight vncserver for puppy.

[See here for description of Wizard]

tight VNC server is part of the tightvnc suite applications. I decided to split the viewer and the server in two different packages to make it more puppy friendly.

I still need to add the 'man' page puppy style.

It registers with pupget and adds itself to the fvwm95, icewm and Jwm menus

I translated the original vncserver perl script to run as a bash script. It is a semantic translation not a literal translation so it still needs testing although I haven't been able to break it.

To lean how to use it type vncserver -help at the console after installation.

It installs about 1.4 Mb. to the /root/my-applications/tightvnc
Plus it installs a cursor.pcf font to the /usr/lib/X11/fonts/misc

The VNC viewer is also under this thread.

===== Change log ======

# Edit March 23, 2008 -> New version uploaded
- Updated to the latest tightVNCserver version 1.3.9
- Fixed problem with Rox startup parameters as reported by paulh177

# Edit May 18, 2006 -> New installation version uploaded. (didn't change the number 1.2.9-0.7)
- Fixed the bug where /root/.vnc/xstartup was not being set as executable
- Added the .desktop file so it shows in the 109CE menu.

# Edit Oct 7, 2005 -> New installation version uploaded. (1.2.9-0.7)
- Added feedback window while starting a new display.

# Edit Sept 29, 2005 -> New installation version uploaded. (1.2.9-0.6)
- New vncserver-wizard included. Thanks to pakt for the initial prototype and for testing the alpha versions.
- The xstartup executes jwm by default
- Faster vncserver -l command
- Rox cursor and Pinboard lanunched by default on the new displays. Thanks to pakt for the advice.

# Edit Aug 7, 2005 -> New installation version uploaded. (1.2.9-0.4)
- Create ~/.vnc folder if there isn't one. (Thanks to pakt for finding the bug and sending the fix)
- Show the number of displays found when option -list selected.
- If the pid file does not exist when trying to kill the display, show a meaningfull message.
- From the menu, execute the vncserver in a xterm to give feed back to the user.

#Edit Aug 5, 2005 -> new installation version uploaded. (1.2.9-0.3)
- Fixed the vncserver installation script, It now registers into the fvmw95, icewm and jwm menus
- The vncserver script now uses the standard shell instead of bash
- Start fvwm95 as the default WM. (It can be changed by editing the ~/.vnc/xstartup file)

=====
Known bugs:
The installer does not remove the previous vncserver menu entry. If you have previously installed the vncserver, you can remove the older menu entry manually. The new entry executes the vncserver-wizard

[rarsa]

Why tight VNC viewer if we already have "TkVNC VNC Client"?
- It supports secured servers. It will ask for the password.
- It can run in full screen. Actually you can flip between full screen and windowed
- It's a quite fast native binary
- It supports a large variety of parameters
- It provides automatic scrolling for when you are connecting to a computer that has higher resolution.
- It required just the binary and one extra library. Making it 244K to download and just 543K installed

It installs to /root/my-applications/tightvnc and creates a symlink in /root/my-applications/bin.

I am including the original README file

To learn how to use it just type vncviewer -help
To start the viewer just type vncviewer
It will prompt for the server address. use the xxx.xxx.xxx.xxx:p format where xxx is the IP address and p is the screen number. e.g. 192.168.1.100:1 (it goes to port 5901 of server 192.168.1.100)

Please try it and send me your comments.

[Lobster]

You are a smart Puppy

This is now linked on the wiki news page
http://www.goosee.com/puppy/wikka/LatestNews

[dvw86]

Not bad, not bad at all! I definitely like the TightVNCviwer better than TkVNC. I had a little trouble with the server though, but was still impressed. For some reason it opened up a whole new window session. This may be because I didn't set any options when I started it. I'll have to look into it further to find out. The Pinboard does not start on the remote window. I had to start it manually. This is probably because none of the Puppy startup scripts were ran. One other suggestion is to mention that all of the TightVNC applications need to be started from the terminal (rxvt session). You can not just click on the icon and have it work. All in all this is great, just what i was looking for. Thanks!!

[rarsa]

****EDIT
I just noticed a bug in my vncserver DotPup. It adds the vncviewer entry to the menu instead of adding the vncserver.
I will fix it tomorrow as I just came back from camping and I'm quite tired.
****

Actually they can be started from the menu.

The vncserver script runs with defaults if it is executed from the menu.

If you need to change those defaults, you just change the script. That's what's normally done in the thightVNC server original script.

If you read the top of the script you can also see that one of my TODO's is to add a configuration file where to put the defaults without having to modify the script.

As for the viewer: If you run it from the menu, it pops up a little window requesting the address. It is not clear that you have to enter address and display, that's why I explained it in my post (xxx.xxx.xxx.xxx:d)

Alternativelly you could change the entry in the menu to add all the parameters you normally use.

[menno]

It works great !

You can use it from windows and linux . With server in windows you should give only the IP without any port (or :5900) .

I thing it better to change the #!/bin/bash into #!/bin/sh (vncserver script) because older Puppy's do not have a bash .
In the server xstartup you use as window manager icewm , but this is not avaleble in all the Puppy's . Maybe it better to fill this in when your looking for what window mannager is used , as done in dotpup.sh .

[rarsa]

Thank you for your input.

Change log:

- Fixed the vncserver installation script, It now registers into the fvmw95, icewm and jwm menus
- The vncserver script now uses the standard shell instead of bash
- Start fvwm95 as the default WM. (It can be changed by editing the ~/.vnc/xstartup file)

The new version is in the same link as the previous one, the new version id is 0.3

[BlackAdder]

Have tried the viewer controlling an XP machine.
The only problem was with scrolling. The viewer would only scroll once in any direction and then it was stuck.
Has anyone else observed this behavio(u)r?

[Guest]

Yes, I have.

That's why I do one of the following:

a) When setting up a linux VNC server, I set a geometry equal or smaller than the expected clients.

b) When connecting to a server that has a higher resolution, I press F8 and select 'Full screen' from the popup menu. When running in full screen, the viewer does an automatic scroll as soon as you get to the border of the screen.

[rarsa]

Oops, the previous post is mine,

[BlackAdder]

Thanks for that rarsa.

[pakt]

[rarsa]

Good catch! I'll try to fix both errors.

That's what happens when you only test in the computer where you do the development. You give certain things for granted.

[gliezl]

my TkVNC VNC Client is not working. I can browse the internet. I can check my mails. I can do SSH in out servers. But tkVNC hangs. I go to FILE then CONNECT, fill in the values, then it hangs! What did I do wrong? My officemates connects via VNC using windows. Please help...

[BlackAdder]

The problem may be that tkVNC does not support the use of passwords; the server most likely requires a password before allowing connection.

The tightVNC viewer does support password entry, and is a dot pup downloadable from within this thread.