Tight VNC Server/Viewer (Now with GUI!)
Thanks you again for your input.
I have uploaded a new version of the installer.
Now it should works nicelly from the menu.
You can read the change log in the original post
I have uploaded a new version of the installer.
Now it should works nicelly from the menu.
You can read the change log in the original post
Try reinstalling the DotPup.
If there was something wrong you would get an error.
Did you install it from this thread?
What version of Puppy are you running?
Are you running from CD? HDD install? USB? how?
===========
If you installed from the DotPup in this thread, do the following.\:
- Open a terminal
- execute vncviewer
- Just after it comes back to the prompt type "echo $?"
- Copy the text in the console and paste it in your response
If there was something wrong you would get an error.
Did you install it from this thread?
What version of Puppy are you running?
Are you running from CD? HDD install? USB? how?
===========
If you installed from the DotPup in this thread, do the following.\:
- Open a terminal
- execute vncviewer
- Just after it comes back to the prompt type "echo $?"
- Copy the text in the console and paste it in your response
rarsa, after some experimenting, I have found a solution to the problem of fvwm95 hanging when clicking on 'TightVNC Server' in the menu if the password has not been set.
This way, a rxvt terminal opens on the server PC with the password dialog. Afterwards, the terminal stays open showing which display is used and any connection messages (useful for knowing the display number when starting up a VNC viewer). The terminal will automatically close when a 'vncserver -kill <display>' command is issued (from another rxvt terminal).
These changes should make TightVNC Server easier to use.
Here are the changes I've made:
in dotpup.sh
---< snip >---
# Register with fvwm95 menu
if [ -f /root/.fvwm95rc ]
then
egrep -i vncserver /root/.fvwm95rc >/dev/null 2>&1
if [ $? -ne 0 ]
then
cp -f /root/.fvwm95rc /root/.fvwm95rc.bak
awk '{if (/AddToMenu "Network"/) {print $0;print "+ \"TightVNC server%pc-2x.xpm%\" Exec rxvt -e vncserver"} else {print $0};} ' /root/.fvwm95rc.bak > /root/.fvwm95rc
fi
fi
---< snip >---
in vncserver
Add in MAIN SCRIPT:
---< snip >---
echo "Display :$displayNumber listening on TCP port `expr 5900 + ${displayNumber}`"
wait
exit 0
---< snip >---
I have also added/modified the following lines to the runXstartup() function. This adds the icons and a nice blue Puppy-like background:
---< snip >---
echo "#xrdb $HOME/.Xresources" >> "$xstartup"
echo "xsetroot -solid lightblue" >> "$xstartup"
echo "xsetroot -cursor_name top_left_arrow" >> "$xstartup"
echo "#xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &" >> "$xstartup"
echo "fvwm95 &" >> "$xstartup"
echo "rox -op /root/Choices/ROX-Filer/PuppyPin" >> "$xstartup"
chmod 0755, "$xstartup";
---< snip >---
Works nicely for me. Let me know what you think.
This way, a rxvt terminal opens on the server PC with the password dialog. Afterwards, the terminal stays open showing which display is used and any connection messages (useful for knowing the display number when starting up a VNC viewer). The terminal will automatically close when a 'vncserver -kill <display>' command is issued (from another rxvt terminal).
These changes should make TightVNC Server easier to use.
Here are the changes I've made:
in dotpup.sh
---< snip >---
# Register with fvwm95 menu
if [ -f /root/.fvwm95rc ]
then
egrep -i vncserver /root/.fvwm95rc >/dev/null 2>&1
if [ $? -ne 0 ]
then
cp -f /root/.fvwm95rc /root/.fvwm95rc.bak
awk '{if (/AddToMenu "Network"/) {print $0;print "+ \"TightVNC server%pc-2x.xpm%\" Exec rxvt -e vncserver"} else {print $0};} ' /root/.fvwm95rc.bak > /root/.fvwm95rc
fi
fi
---< snip >---
in vncserver
Add in MAIN SCRIPT:
---< snip >---
echo "Display :$displayNumber listening on TCP port `expr 5900 + ${displayNumber}`"
wait
exit 0
---< snip >---
I have also added/modified the following lines to the runXstartup() function. This adds the icons and a nice blue Puppy-like background:
---< snip >---
echo "#xrdb $HOME/.Xresources" >> "$xstartup"
echo "xsetroot -solid lightblue" >> "$xstartup"
echo "xsetroot -cursor_name top_left_arrow" >> "$xstartup"
echo "#xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &" >> "$xstartup"
echo "fvwm95 &" >> "$xstartup"
echo "rox -op /root/Choices/ROX-Filer/PuppyPin" >> "$xstartup"
chmod 0755, "$xstartup";
---< snip >---
Works nicely for me. Let me know what you think.
Thank you patk,
1. Actually I implemented exactly that soultion for the password as soon as it was reported and posted it along with your proposed solution for the missing .vnc folder.
2. I also thought about puting a wait or a read at the end of the vncserver script so the user had time to read what was happening, but then I thought that it's not a very good practice as the script may be executed automatically at start up or by other script. I actually played with another wrapper script 'vncserverfrommenu" that would ask for some basic parameters (geometry, depth, etc) then call the vncserver script and then wait for the user to press enter. I decided not to include it as it may confuse new users. Experienced users can launch it from the command line.
3. Thank you for the customization example. Other people may base their personal customization on yours. Great!
4. Do you know tclck or XDialog? A solution for new users executing the VNC server could be a UI where they can select the vncserver parameters graphically. I can then save those parameters to a configuration file ~/.vnc/.vncserver. So, if you want to do it, I can include it in the package, if not, I'll implement it as soon as I get some time.
Currently the defaults are in the vncserver script. That's where the original tightVNC server script has them so I just did a semantic translation. (I want it to work as close as the original to avoid confusions)
1. Actually I implemented exactly that soultion for the password as soon as it was reported and posted it along with your proposed solution for the missing .vnc folder.
2. I also thought about puting a wait or a read at the end of the vncserver script so the user had time to read what was happening, but then I thought that it's not a very good practice as the script may be executed automatically at start up or by other script. I actually played with another wrapper script 'vncserverfrommenu" that would ask for some basic parameters (geometry, depth, etc) then call the vncserver script and then wait for the user to press enter. I decided not to include it as it may confuse new users. Experienced users can launch it from the command line.
3. Thank you for the customization example. Other people may base their personal customization on yours. Great!
4. Do you know tclck or XDialog? A solution for new users executing the VNC server could be a UI where they can select the vncserver parameters graphically. I can then save those parameters to a configuration file ~/.vnc/.vncserver. So, if you want to do it, I can include it in the package, if not, I'll implement it as soon as I get some time.
Currently the defaults are in the vncserver script. That's where the original tightVNC server script has them so I just did a semantic translation. (I want it to work as close as the original to avoid confusions)
Oops , missed that one. That's what I get for having too many versions of tightvncserver laying aroundrarsa wrote: 1. Actually I implemented exactly that soultion for the password as soon as it was reported and posted it along with your proposed solution for the missing .vnc folder.
I see your point, but being a new user to VNC myself, I found it confusing to have no feedback when starting the server from the menu. I really find the terminal window useful for seeing the display # and connection messages, also as a reminder that a VNC server is running.. Perhaps two scripts are called for: one adapted to be started from the menu and another that can be executed at startup or by another scriptrarsa wrote: 2. I also thought about puting a wait or a read at the end of the vncserver script so the user had time to read what was happening, but then I thought that it's not a very good practice as the script may be executed automatically at start up or by other script.
I don't know tclck or XDialog. It may not be that obvious, but I'm just a newbie in shell scripting. Took a lot of searching on the net and head-scratching before finding the solution in my previous post. I'm honored by the fact that it turned out to be the one you also came up with.rarsa wrote: 4. Do you know tclck or XDialog? A solution for new users executing the VNC server could be a UI where they can select the vncserver parameters graphically. I can then save those parameters to a configuration file ~/.vnc/.vncserver. So, if you want to do it, I can include it in the package, if not, I'll implement it as soon as I get some time.
As to your suggestion, I've been looking through Barry's scripts to learn how he writes his wizards. Perhaps a VNC Wizard? Don't have the details at hand, but I believe he uses Xmessage to create his dialogs. May be similar to what you're suggesting? I'll let you know if I come up with something.
Meanwhile, thanks for all the work you're putting into this
Sorry, it seems that the vncviewer command is not working for me. In my previous post, I was pertaining to vncviewer rather than vncconnect. The error was "command not found", something like that. Have I really installed the DOTPUP properly? I just followed the procedure. (GUI interface)
I don't have the binary file itself. (vncviewer)
I don't have the binary file itself. (vncviewer)
Please notice that there are two packages: vncviewer and vncserver.
You need to install vncviewer.
Please post the result of the following command:
You need to install vncviewer.
Please post the result of the following command:
Code: Select all
ls -la ~/my-applications/tightvnc
rarsa, I've been working with TightVNC for some time now learning how it works and trying to understand some problems I've had with it. I've also got a prototype 'Puppy VNC Server Wizard' working using xmessage in a script a la BarryK's Video Wizard (actually, I've borrowed a lot of the code from that wizard ).
First off, I've discovered why I couldn't get the xterm line in xstartup to work (after removing the # of course ). There is an error when xstartup is created by vncserver. Here is the original code:
echo "#xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &" >> "$xstartup"
which results in:
#xterm -geometry 80x24+10+10 -ls -title X11 Desktop &
Note that the quotation marks have disappeared from around 'X11 Desktop'. This turns 'Desktop' into a parameter, which xterm rejects and therefore fails to start. The line in vncserver should be:
echo -e "#xterm -geometry 80x24+10+10 -ls -title \"$VNCDESKTOP Desktop\" &" >> "$xstartup"
preserving the quotation marks.
Now for the main problem that I seem to have (finally) fixed. I haven't had any problems starting VNC servers from within fvwm95, but when running Puppy in text mode and starting a VNC server, I only got an X window and mouse cursor on the client - the lines in xstartup didn't seem to work. It appears that this was caused by the DISPLAY variable (set in vncserver) not being exported. When vncserver starts the xstartup script, $DISPLAY is blank. I changed this line in the vncserver 'runXstartup' function from:
DISPLAY=:${displayNumber}
to
export DISPLAY=:${displayNumber}
now vncserver works like a charm when running Puppy in text mode!
First off, I've discovered why I couldn't get the xterm line in xstartup to work (after removing the # of course ). There is an error when xstartup is created by vncserver. Here is the original code:
echo "#xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &" >> "$xstartup"
which results in:
#xterm -geometry 80x24+10+10 -ls -title X11 Desktop &
Note that the quotation marks have disappeared from around 'X11 Desktop'. This turns 'Desktop' into a parameter, which xterm rejects and therefore fails to start. The line in vncserver should be:
echo -e "#xterm -geometry 80x24+10+10 -ls -title \"$VNCDESKTOP Desktop\" &" >> "$xstartup"
preserving the quotation marks.
Now for the main problem that I seem to have (finally) fixed. I haven't had any problems starting VNC servers from within fvwm95, but when running Puppy in text mode and starting a VNC server, I only got an X window and mouse cursor on the client - the lines in xstartup didn't seem to work. It appears that this was caused by the DISPLAY variable (set in vncserver) not being exported. When vncserver starts the xstartup script, $DISPLAY is blank. I changed this line in the vncserver 'runXstartup' function from:
DISPLAY=:${displayNumber}
to
export DISPLAY=:${displayNumber}
now vncserver works like a charm when running Puppy in text mode!
Appreciate your feedback, miamuy. Glad it worked for you toomiamuy wrote: a big thanks there, pakt! i'm have that same problem, done your solution & works for me. thanks!
You may be interested to know that I've been in contact with rarsa and sent him a prototype VNC Server Wizard that I've made. I was thinking he might be able to use it as is or modified to his liking in his VNC-pup package.
I've released a new version of the vncserver. It was a necessary update for puppy 1.0.5, but it will run in older puppys.
http://www.murga.org/%7Epuppy/viewtopic.php?p=5943#5943
Thanks to all the feedback and testing from patk (forum name), it has a substantially improved interface for new users.
patk created a prototype wizard from which I built uppon. The result was quite pleasing to both of us. Hopefully it will also be for you.
Here is the changelog:
# 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 his patience and feedback testing the following 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.
So there it is for you to try and provide feedback.
http://www.murga.org/%7Epuppy/viewtopic.php?p=5943#5943
Thanks to all the feedback and testing from patk (forum name), it has a substantially improved interface for new users.
patk created a prototype wizard from which I built uppon. The result was quite pleasing to both of us. Hopefully it will also be for you.
Here is the changelog:
# 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 his patience and feedback testing the following 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.
So there it is for you to try and provide feedback.