a press on the '3' button actually sending the code for the '6' button instead.

Yeah, I fixed that once. It must have worked it's way back in... not sure how. It will be fixed in the next release.

Tom

Is it possible to put in a non-owner mode in there?

I already do this now, a little bit. If allow_commands=0 is set in config.ini, some of the things in the playlist page are hidden, like the my commands drop-down, the remote, and the play icons.

It should be very easy to take the ftp page out, just don't upload it and remove the two links to it.

Tom

Hey Charcoal, just wanted to say that this thing is really cool, thanks for all the work you've put into it. It certainly adds to the "drool factor" especially if the person is geeky enough to comprehend the fact that you're "surfing" your car stereo. The VNC applet takes away what was my one gripe, which was the slow updating of the screen image. It's "little things" like your stylesheet (little in size, not in the work you put into it, I'm sure) add so much in the long run.

My only gripe is I that have to re-write the /proc/empeg_notify parser I wrote for one of my projects... But hey, you need to break a few eggs to make an omelette.

Any idea why the VNC display only works the first time I open up the page.

I have the SAME problem. wfaulk said he had a couple ideas what it could be. I know it worked for me before I installed J2SE 1.4, but I haven't confirmed that as the cause.

I don't think it's possible to update the "Now Playing" when the track changes.

Tom

Thanks yn0t_. I get a kick out of showing off that I can surf my car stereo too.

Sorry about changing the format of empeg_nofity. I did ask mark to use empeg_nofity?EXT=.js and make it an option. I'm not sure why he made it the default, but I'm sure he had a reason.

Tom

Eh, it's no biggie. It actually makes the parsing rules easier because you've got quote characters to begin and end the strings. Short term loss = long term gain.

I get the basic screen, with the flyout remote, and various links on the side. but no ftp browser link, and no no playing text or icons.

It sounds like you have an older version. Is it possible you didn't overwrite index.html? I have no idea why the ftp browser link would not show up, it's just html, and I'm sure it's in there...

Tom

It sounds like you have an older version. Is it possible you didn't overwrite index.html?

This is the first time I have ever installed it :-)

I will completely delete it, then reinstall it again.

Suggestion, distribute it as a plain tar file, since empeg's have tar onboard -- then we can transfer the tar to the empeg and untar it.

rjf&

distribute it as a plain tar file, since empeg's have tar onboard -- then we can transfer the tar to the empeg and untar it.

I think I'll wait for the App Installer project.

Tom

I probably exaggerated somewhat. I'm fairly confident that it's because when you end the java applet, it doesn't really get ended, and it's still attached to the VNC server somewhere. (Maybe it's just closing it's end without notifying the server?) And since the VNC server accepts only one connection at a time currently, the applet just sits and waits for it to respond.

And since you're using IE, there's not really any way to totally shut down the browser to make sure that the applet is no longer running (which wouldn't necessarily prove anything, because if it never sent a FIN packet to the server, the server still wouldn't know).

I'm not near a place where I can figure this out right now, but if someone can reproduce this problem and then log onto the empeg and run ``netstat -atup'', that would help out. (Does the empeg even have a netstat binary on it? If not, I could compile one I guess.)

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name   

tcp        0      0 192.168.1.3:5900        192.168.1.2:3008        ESTABLISHED 26/empegvnc         

tcp        0      0 192.168.1.3:80          192.168.1.2:3007        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:3005        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:3004        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:3002        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:3001        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:3000        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2999        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2998        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2997        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2996        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2995        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2994        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2993        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2992        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2991        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2990        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2989        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2988        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2987        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2986        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2985        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2984        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2983        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2982        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2981        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2980        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2979        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2977        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2976        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2975        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2974        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2973        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2972        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2971        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2970        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2969        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2968        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2967        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2966        TIME_WAIT   -                   

tcp        0      0 192.168.1.3:80          192.168.1.2:2965        TIME_WAIT   -                   

tcp        0    306 192.168.1.3:23          192.168.1.2:2959        ESTABLISHED 12/telnetd          

tcp        0      0 *:8301                  *:*                     LISTEN      33/player           

tcp        0      0 *:8300                  *:*                     LISTEN      33/player           

tcp        0      0 *:21                    *:*                     LISTEN      -                   

tcp        0      0 *:80                    *:*                     LISTEN      -                   

tcp        0      0 *:5900                  *:*                     LISTEN      26/empegvnc         

tcp        0      0 *:23                    *:*                     LISTEN      12/telnetd          

udp        0      0 *:8300                  *:*                                 33/player       

.

I just realized that I should have been a little more specific about when that information should have been gathered. Was that taken during the first connection or between connections or during the second (attempted) connection or afterwards?

That was after:

1. Hitting the Empeg's index stylesheet and bringing up the VNC applet.
2. Closing the browser.
3. Bringing up the applet again and having it fail to load

Then I did the netstat.

Just to make sure, try doing it after you close your browser, but before you bring it up again. Then do bring it up again after you run the netstat to make sure that it fails.

Again, my guess is that IE is not really closing the Java applet. Or, perhaps, that empegVNC never sees the applet close because it's been killed abruptly (I didn't write the applet; I just ripped it out of the WinVNC implementation). The reason that it would work with WinVNC is because WinVNC would just kill the old session arbitrarily when it got the new connection. empegVNC waits for the old connection to end. Maybe I should figure out how to change that.

I've noticed the same thing with the web server when testing this util.

I was having the same problem. Here's what I did:

1) Download the TightVNC Java viewer from tightvnc.com (tightvnc-1.2.8_javabin.zip as of today).

2) Rename the original vncviewer.jar file (/drive0/opt/khttpd/charcoalgray99/jar/vncviewer.jar) to vncviewer.jar.orig (if you want a backup)

3) Drop the VncViewer.jar from TightVNC into the jar directory and rename to match the original jarfile's name -- case sensitive (I renamed VncViewer.jar to vncviewer.jar)

4) Modify jscripts.js (/drive0/opt/khttpd/charcoalgray99/js/jscripts.js) such that parameters which TightVNC likes are passed to the applet. The first few lines of the drawFascia(url) function (approximately line 189) should look like this:

function drawFascia(url)

{

	if (useVNC == true)

	{

		document.write("<applet CODE=VncViewer.class ARCHIVE=\"/drive0/opt/khttpd/charcoalgray99/jar/vncviewer.jar\" WIDTH=\"300\" HEIGHT=\"93\">");

		document.write("<param name=\"PORT\" value=\"5900\"/>");

		document.write("<param name=\"PASSWORD\" value=\"\"/>");

		document.write("<param name=\"Encoding\" value=\"Raw\"/>");

		document.write("<param name=\"Restricted colors\" value=\"Yes\"/>");

		document.write("<param name=\"Show controls\" value=\"No\"/>");

		document.write("</applet>");

	}

.... function continues, but I do not list it here.


TightVNC's applet code seems to work better than ATT's when navigating between pages, etc.

I am using J2SE 1.4 with the plugin and it's pretty solid. Just don't try to connect twice (as wfaulk has mentioned) or you will crash the vnc server and will need to restart it.

The parameters I added were just my first guesses, so other combinations will likely work also. Here are my guesses and why I chose them:

PASSWORD="" -- don't use authentication
Encoding="Raw" -- guessed based on the att java client patchfile
"Restricted colors"="Yes" -- empegVNC doesn't like 24-bit connections
"Show controls"="No" -- don't add the GUI buttons (Options, etc) to the TightVNC client applet