Updated Vnc Viewer For Sharp Roms, New features added to keypebble Options

[TimW]

Here is the latest.

This wouldn't by any chance act as a terminal services client would it?

No - there is a terminal services client for the zaurus, though. Search for rdesktop. The ELSI entry is on this page and the ZSI one is on this page. I'm not sure which you need for your ROM but I'm pretty sure I'm using the ZSI one on my Sharp ROM.

[ken]

No - there is a terminal services client for the zaurus, though. Search for rdesktop.

Thanks, had hoped to do 2 birds with one stone. I installed that one before, but was never really successful with it. I guess I can take a second crack at it again.

[chyang]

Ivhave posted the english one sometime before, the qtrdesktop is cey good.

[undrwater]

I've added some more trace to help track down problems with unusual server pixel formats, and added some extra code to cope with them - I may even have caught them all, this time 8^).

I've also done a little bit more optimisation by forcing the pixel format to little endian which reduces the amount of byte shuffling and is more likely to match the server (unless you have a PowerPC Mac).

Here is the latest.

Got your PM, thanks! I'm getting the same error as stated above. I don't think the problem is on the server side as I get the same error regardless of the IP.

Opie-keypebble 1.0.0 connects (without error) but won't accept the correct password.

Has anyone else tried this on a 6000?

Thanks for your work Tim!

[TimW]

Got your PM, thanks! I'm getting the same error as stated above.  I don't think the problem is on the server side as I get the same error regardless of the IP.

Opie-keypebble 1.0.0 connects (without error) but won't accept the correct password.

Has anyone else tried this on a 6000?

Thanks for your work Tim!

The problem is that none of that trace is generated by my code so I don't know how far you're getting. Is it possible to do

teakettle 2>errs.txt

from a terminal and then send me the errs.txt file?

[undrwater]

Got your PM, thanks! I'm getting the same error as stated above.  I don't think the problem is on the server side as I get the same error regardless of the IP.

Opie-keypebble 1.0.0 connects (without error) but won't accept the correct password.

Has anyone else tried this on a 6000?

Thanks for your work Tim!

The problem is that none of that trace is generated by my code so I don't know how far you're getting. Is it possible to do

teakettle 2>errs.txt

from a terminal and then send me the errs.txt file?

I'm still not getting the trace. All I see is:

CODE

QGDict::hashStringKey: Invalid null key
QGDict::hashStringKey: Invalid null key
QGDict::hashStringKey: Invalid null key
QGDict::hashStringKey: Invalid null key

even when doing teakettle 2>errs.txt

I should add that I installed using ipkg install, and no errors were thrown.

Curious!

[TimW]

I'm still not getting the trace.  All I see is:

CODE

QGDict::hashStringKey: Invalid null key
QGDict::hashStringKey: Invalid null key
QGDict::hashStringKey: Invalid null key
QGDict::hashStringKey: Invalid null key

even when doing teakettle 2>errs.txt

I should add that I installed using ipkg install, and no errors were thrown.

Curious! 

I didn't realise that was the entire trace! I am completely stumped.

The whole app is in a single executable file which I run directly from the command line when testing - I don't even install it usually - so installation location shouldn't matter. I'll try putting up just the executable when I've got it to hand, if you want to try. I generally just do:

/mnt/cf/teakettle

or, if I'm testing for speed

/mnt/cf/teakettle 2>/dev/null

since printing to the terminal is very slow.

Has anyone else succeeded on a 6000?

[TimW]

Another update. A few more percent speed increase and I've found the correct functions to use to set the cursor but under Qtopia there are no cursors so they still don't work....so I've just taken it out. This means that the "Local Cursor" setting cuts down on network traffic but removes the cursor (providing the server understands that encoding).

Attached File(s)

 teakettle_0.5_arm.ipk ( 51.92K ) Number of downloads: 62

 

[periodontist]

Tim,

Just a little feedback. I installed an earlier version of TeaKettle and had no errors connecting to my WinXP box which is running the TightVNC server.

I tried a setting of Scale = 0 and it seemed to work flawlessly...although talk about a tiny display...

The only thing I noticed (and I didn't really run it through a lot of tests) was that the screen was inverted when running in landscape mode (I was not running teakettle in magnified mode if that makes any difference). Luckily, when I turned my Zaurus 180 degrees, everything looked right!

Thanks for your many efforts. Your OPIE Reader is the most used program on my Zaurus...it would be hard to live without it.

Matt

[sidmoraes]

Does not work with realvnc...

[TimW]

Tim,

Just a little feedback.  I installed an earlier version of TeaKettle and had no errors connecting to my WinXP box which is running the TightVNC server.

I tried a setting of Scale = 0 and it seemed to work flawlessly...although talk about a tiny display...

The only thing I noticed (and I didn't really run it through a lot of tests) was that the screen was inverted when running in landscape mode (I was not running teakettle in magnified mode if that makes any difference).  Luckily, when I turned my Zaurus 180 degrees, everything looked right!

Thanks for your many efforts.  Your OPIE Reader is the most used program on my Zaurus...it would be hard to live without it.

Matt

Thanks for the feedback. It is nice to know it does work for someone other than me 8^).

The scale = 0 option probably isn't much use for windows boxes where the size of the served display must be the same as the physical display - although I do use it for monitoring sometimes (control is pretty much impossible with buttons about the size of a pixel 8^)).

It works okay with my linux and Mac boxes, though - but even then for serious work I wouldn't use it - but it is "nice to have".

The rotation direction was chosen for my convenience on my SL5000 - I can easily flip it 180 degrees (I'll make it configurable). See the next release 8^).

[TimW]

Does not work with realvnc...

It does for me! RealVNC is my server of choice both on Windows and XP (mostly because it lets me try out the latest encoding I've added and is more compliant to the standards - but generally, when I'm not tweaking vncviewer code, I use tightVNC on windows, RealVNC on linux and OSXVnc on Mac).

How about a little more detail....

For example, run "teakettle 2>trace.txt" and send me trace.txt, or just teakettle on its own from the console and let me know what it prints out, or what operating system is the server on, what screen res and colour depth its using, whether it crashed or failed to connect, whether you were using 0.5 and it used to work with previous versions, etc.

Then I may be able to help 8^).

[TimW]

The rotation direction was chosen for my convenience on my SL5000 - I can easily flip it 180 degrees (I'll make it configurable). See the next release 8^).

I've got all orientations working (0, 90, 180, 270 degrees) so if anyone is in a hurry for this functionality post here and I'll put it up. Otherwise I'll leave it until there are a few more improvements to make it worth while.

Oh, and I think I've got a version which'll work on Opie ROMs - which is good as I started doing this specifically for my Simpad running Opie! I'm just testing it out on 3.5.4 (typically I got it working on the previous version the day the new version came out).

Let me know if anyone wants to test an opie version....

[loji]

I'm using teakettle_0.5 and i recieve the same errors as stated:

OGDict: hashStringKey: Invalid Null Key
KRFBConnection: Socket error 1


I am running a 5600 w/ Wapaton 1.6.1 ROM, No overclocking
I have a Linksys wifi card, on a wep enabled home network.

I have TightVNC running on a winXP box that accepts local connections, so it's running. The VNC server log files don't even show a connection attempt form the Z, so i guess the socket error means it's not even getting out.

What could be the problem here? IPK installed fine - no dependancy problems.

[TimW]

What could be the problem here?  IPK installed fine - no dependancy problems.

How far have you got after starting up teakettle?

Do you even get the dialog displayed?
Have you managed open up the new bookmark?
Have you managed enter everything on the server screen?
Does it crash when you hit the connect button/the okay button/any other button?

Sorry for the tedious questions but this is really puzzling so I have *no* idea what is going on. There is a reference in the original keypebble readme to a bug in QSocket which causes a mysterious crash when connecting to a non-existent server. I can't reproduce this but maybe this is what you are hitting and it is caused by the Zaurus not being able to see your desktop?

I've used tightvnc on against a WinXP box without problems - though I was hitting the problem where tightvnc wanted a 32 bit session and the Zaurus wanted something less but wasn't filling in the whole of the response correctly - but that is all fixed in 0.5. (BTW, have you configured the XP firewall to let VNC through?).