Puppy Linux Discussion Forum

[gliezl]

downloaded the the pup file. installed it. even checked with dot pup manager, the applcation was installed. but when i run it, nothing happens. i just typed vncviewer 192.168.0.3:5900 then comes back to the prompt. nothing happens.

[rarsa]

The correct format is vncviewer 192.168.0.3:0

There is always confusion. The port is 5900, the display is :0

[rarsa]

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

[gliezl]

Ok! Thanks for this one. Atleast it nice to learn. Yeah, get confused about that port & display thing. I'll download your new version. I'll keep you guys posted.

Again, thank you

[gliezl]

I typed at the console, vncviewer 192.168.0.3:0, and still it just goes back to the prompt and nothing happen. It's supposed to prompt me a password, right?

Sorry, I'm quite new to this thing. Yet VNC in windows works fine in my machine. Please do assist me. Thanks

[Guest]

If you just type
vncviewer
it should prompt you for an IP address in a pop-up, then for the password. I don't enter the screen number, and it works for me.

[gliezl]

when I type vncviewer it just goes back to the prompt. It does not prompt me a password either.

[rarsa]

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

[gliezl]

Reinstalled dotpup. I installed it from this thread. Puppy 1.0.4 running from live CD.

tried the echo $?, ithas an output of zero. "0"

It's ok for me if you teach me some console commands.

[pakt]

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.

[rarsa]

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)

[pakt]

[gliezl]

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)

[rarsa]

Please notice that there are two packages: vncviewer and vncserver.

You need to install vncviewer.

Please post the result of the following command:

[gliezl]