I did try this on one of my machines. Created a script similar to yours, made it executable and tested it. Next, added /home/user/vncstart to /home/user/.jwmrc right below "pcmanicons on". Works for me every time. Not sure what the issue may be.

I just want to say thank you again to M0E-lnx and nightflier for all of your help and suggestions.

What I need is to be able to connect to this machine remotely through vnc. I thought I would need to autostart vnc to achieve this. But I have discovered a better way. Instead of having vnc running all the time with 5900 open. I can just have 22 for ssh open and then start x11vnc(btw I switched from tightvnc to x11vnc cause I can control local display of remote machine) from my desktop like this:

Actually, if I were you i'd enhance security by forwarding my port 22 to something else.I used to ssh then vnc to my box @ home from work, using the standard ports, until one day, looking @ the logs, I discovered thousands of attempts to hack my box. (maybe automated scripts)..

to avoid that, you either change the ports your ssh server will listen on or forward your 22 to some other port.

On another slackware server I setup in the past I had the exact same problem with tons of login attempts showing up in the logs. So in the past I've done what you suggested and forwarded some weird random port number from the router/firewall to 22 on ssh server.