 |
|
| BeBits Single Quote Bug |
|
|
By Alexander G M Smith - Posted on January 23, 2007 - 19:48:23 (#21238)
Current version when comment was posted: 4.0-BeOS-AGMS-1.21 |
|
|
Using BeOS R5 here too, so I'm keeping it working with R5.
Oddly (guess someone fixed it) when I added the PowerPC version just now, there were no problems with single quote marks being excessively escaped. Or the retroactive editing of versions doesn't have the problem that adding a new version does.
- Alex
|
|
| bebits bug |
|
|
By Pete - Posted on January 23, 2007 - 13:48:29 (#21236)
Current version when comment was posted: 4.0-BeOS-AGMS-1.21 |
|
|
Yeah, here too. Very annoying. Tried with every browser, same result. :-(
|
|
| Thank you - it does seem faster |
|
|
By hey68you - Posted on January 23, 2007 - 06:28:22 (#21234)
Current version when comment was posted: 4.0-BeOS-AGMS-1.21 |
|
|
Using regular R5 - keep up the good work
|
|
| thank you for update, bebits server bug |
|
|
By BeOS Mr X - Posted on January 22, 2007 - 22:32:40 (#21233)
Current version when comment was posted: 4.0-BeOS-AGMS-1.21 |
|
|
any one besides me notice the new bug in bebits' servers... when ever a single quote is used on your app page a whole bunch of forward slashes form after the single quote. Strange, huh !
|
|
| Re: Leaping Firewall Chasms |
|
|
By Alexander G M Smith - Posted on May 6, 2006 - 08:28:56 (#19670)
Current version when comment was posted: 4.0-BeOS-AGMS-1.20 |
|
|
Ah good - it works when your friend connects from his workplace. Maybe there is an outgoing port ban at the place you were trying to use it from in their firewall?
A sneaky way around that is to use port 80 for the VNC server, if you're not running a web server at home. Then it will get through just like web pages.
|
|
| :-) |
|
|
By Meechmunchie - Posted on May 5, 2006 - 07:53:53 (#19661)
Current version when comment was posted: 4.0-BeOS-AGMS-1.20 |
|
|
Yeah, DSL router with integrated hardware firewall. A port 5900 is definitly forwarded to my home pc. And there is no other server for vnc or on this port in my ethernet at home. There is only one computer.
And I used the vncpasswd tool. I read about in the readme. It's a good readme.
And I know the VNC server is working. Another guy here at work was able to connect and control my PC. I saw it. He used stable Debian 3.1 and tight-VNC. No special parameters.
The other points you wrote I will checking tommorrow.
Thanks for your help and your tool. Good job.
|
|
| VNCServer Usage |
|
|
By Alexander G M Smith - Posted on May 4, 2006 - 19:14:28 (#19659)
Current version when comment was posted: 4.0-BeOS-AGMS-1.20 |
|
|
> A desktop firewall ob Be-OS ?
Oops, I meant a separate home hardware firewall!
If you can read that message on Terminal that it's starting, you should also see messages when someone tries to connect.
Also remember to set the password before starting it up, using the vncpasswd command line program.
You can also test it locally by starting up vncserver then running VNC Viewer or some other VNC client for BeOS, and connecting to your internal network address. You should see something like this:
Thu May 4 20:08:33 267 /boot/home>vncserver
Thu May 4 20:08:38 2006
ServerMain: Listening on port 5900
Thu May 4 20:09:06 2006
Connections: accepted: 10.1.1.12::49427
SConnection: Client needs protocol version 3.3
Thu May 4 20:09:12 2006
Connections: closed: 10.1.1.12::49427 (Authentication failure)
Thu May 4 20:09:19 268 /boot/home>
That's with entering the wrong password at the end. If you don't get even that minimal connection response, then something's messed up with networking (perhaps some other server using port 5900?).
|
|
| *hmpf* |
|
|
By Meechmunchie - Posted on May 4, 2006 - 15:02:05 (#19654)
Current version when comment was posted: 4.0-BeOS-AGMS-1.20 |
|
|
A desktop firewall ob Be-OS ? *curios*
When I'm starting "vncserver" on Terminal I can read "bla ... listening on port 5900".
|
|
| Re: no connect to VNC-Server on R5 with real-VNC-Viewer from Windows |
|
|
By Alexander G M Smith - Posted on May 4, 2006 - 07:20:09 (#19648)
Current version when comment was posted: 4.0-BeOS-AGMS-1.20 |
|
|
Perhaps you have a firewall on your BeOS system? Make sure that it's forwarding port 5900 (the default one, you can set it to use others) to your BeOS computer. As well, make sure VNCServer is running on the BeOS system before you try using it. Starting it from the Terminal command line is one way to see that it's working.
|
|
| no connect to VNC-Server on R5 with real-VNC-Viewer from Windows |
|
|
By Meechmunchie - Posted on May 4, 2006 - 01:46:15 (#19638)
Current version when comment was posted: 4.0-BeOS-AGMS-1.20 |
|
|
Hello, ...
I can't connecting the VNC-Server on my Be-OS R 5, Net-Server - Build, by Using a real-VNC - Client. I tried several Version, 4.1.1, 4.0 and 3.3.7, on Windows XP - SP².
|
|
| Re: No Mouse Pointer |
|
|
By Alexander G M Smith - Posted on October 8, 2005 - 19:00:10 (#17992)
Current version when comment was posted: 4.0-BeOS-AGMS-1.20 |
|
|
Two ways. One is to use a VNC client that displays a mouse cursor on its own. VNCClient under Windows does this - though the cursor is just a small black dot.
The other is to use the VESA safe video mode in BeOS, which draws the pointer into the screen memory rather than using a hardware cursor. The drawback is that VESA graphics are much slower. You can try it out by hitting the spacebar while booting to get to the boot menu, where you can turn on safe VESA video mode.
The real trouble is that I couldn't find any way to get at the mouse pointer shape from an application program - it's hidden somewhere inside the application server. Hopefully Haiku will have some way of reading back the current mouse graphic - we can always add one since Haiku is open source!
- Alex
|
|
| No Mouse Pointer |
|
|
By Tyro65 - Posted on October 6, 2005 - 14:50:17 (#17952)
Current version when comment was posted: 4.0-BeOS-AGMS-1.20 |
|
|
Everything works well, but I cannot see my mouse pointer in the VNC viewer when I try to control a BeOS (BONE) machine with a BeOS (BONE) machine. How can I correct that?
Thanks.
|
|
| Re: Use with a Windows client? |
|
|
By Alexander G M Smith - Posted on July 19, 2005 - 17:36:20 (#17265)
Current version when comment was posted: 4.0-BeOS-AGMS-1.20 |
|
|
Thanks for figuring it out - nice to know that screen savers can break VNCServer on BeOS. They must be hooking into the system in some low level way to miss the fake mouse events from VNC, as well as messing up the reported screen size somehow.
- Alex
|
|
| Re: Use with a Windows client? |
|
|
By marcone - Posted on July 18, 2005 - 17:04:30 (#17246)
Current version when comment was posted: 4.0-BeOS-AGMS-1.20 |
|
|
The problem was that the VNC server's BDirectWindow method does not work if the screensaver is running. It does work when the screensaver is not running. Also, when using the BScreen reader with the screensaver running, the screensaver keeps running even when moving the mouse or sending keystrokes.
|
|
| Re: Use with a Windows client? |
|
|
By Alexander G M Smith - Posted on July 17, 2005 - 12:22:30 (#17239)
Current version when comment was posted: 4.0-BeOS-AGMS-1.20 |
|
|
I get that error sometimes with VNC talking to a Windows VNC server. Usually that means a reboot of the Windows client machine is needed. But perhaps it gets shown for other problems.
As for the zero size window, perhaps the Voodoo doesn't support BDirectWindow properly. Try using the slower but more compatible screen reader, using this commandline to start it up:
vncserver ScreenReaderBDirect=0
- Alex
|
|
| Re: Use with a Windows client? |
|
|
By marcone - Posted on July 15, 2005 - 17:36:19 (#17223)
Current version when comment was posted: 4.0-BeOS-AGMS-1.20 |
|
|
What I said earlier is what I get with the RealVNC 4.0 and 4.1.1 clients. I can connect with two older BeOS clients as well as with TightVNC, however in all three cases only a tiny window is displayed. TightVNC in its "connection info" window says that the remote desktop geometry is 0x0x8, which seems a little small... :-/
(it's really a 1600x1200 desktop running on a Voodoo 3, in case it matters)
|
|
| Use with a Windows client? |
|
|
By marcone - Posted on July 15, 2005 - 17:00:59 (#17222)
Current version when comment was posted: 4.0-BeOS-AGMS-1.20 |
|
|
I'm trying to use this with a Windows client, and the client gives me the following message after connecting and entering my password:
SelectObject to CompatibleDC failed: the operation completed succesfully. (0)
Then it asks if I want to reconnect. The server outputs the following:
Fri Jul 15 14:56:26 2005
TcpSocket: in TcpListener::accept unable to setsockopt TCP_NODELAY, error
code 0, continuing on anyway.
Connections: accepted: 192.168.1.2::4704
SConnection: Client needs protocol version 3.8
SConnection: Client requests security type VncAuth(2)
Fri Jul 15 14:56:33 2005
VNCSConnST: Server default pixel format depth 8 (8bpp) bgr233
Connections: closed: 192.168.1.2::4704 (Clean disconnection)
SMsgWriter: framebuffer updates 0
SMsgWriter: raw bytes equivalent 0, compression ratio nan
|
|
| Re: Rock Solid |
|
|
By Alexander G M Smith - Posted on June 6, 2005 - 05:41:05 (#16803)
Current version when comment was posted: 4.0-BeOS-AGMS-1.18 |
|
|
Nice to hear that it's reliable in real world use, and actually getting used! I used a simple single threaded polling loop to help with that reliability, rather than having separate threads to check for network messages and scan the screen. Plus the RealVNC code I ported it from is fairly good now. It isn't perfect - temporarily dropping the ethernet connection in BeOS R5 Netserver makes it stop accepting new connections, though that's likely a Netserver bug.
- Alex
|
|
| Rock Solid |
|
|
By Double_S - Posted on June 4, 2005 - 10:53:45 (#16800)
Current version when comment was posted: 4.0-BeOS-AGMS-1.18 |
|
|
Rock solid. Did I say rock solid? I meant ROCK SOLID.
I have it running on my Zeta RC2 server. My previous server uptime was 156 days (crashed due to buggy Mozilla Release). VNC Server did run during this whole time, and I connected and disconected with different settings several times.
So much much better than previous releases. You're da man !!
|
|
| Re: PPC Namespace Hell |
|
|
By Alexander G M Smith - Posted on March 1, 2005 - 20:22:08 (#16042)
Current version when comment was posted: 4.0-BeOS-AGMS-1.18 |
|
|
Yup, definitely a problem. I de-namespaced VNC's code by using the trick Nathan mentioned in http://www.bug-br.org.br/pipermail/bedevtalk/2002-November/000714.html - I inserted lines into the C++ source files that look like:
#include <vector>
#include <list>
#include <whatever-STL-stuff-VNC-needs>
namespace std {
int ___foobar___;
}
#define std
#include "Some-VNCHeaders.h"
#include "More-VNCHeaders.h"
This makes VNC's headers stop using namespaces (std::string becomes ::string for example) and the PPC Standard Template Library (which in the Metrowerks compiler for PPC BeOS, doesn't use namespaces, or sort of half uses them) would get included and working before the fix was processed.
- Alex
|
|
| namespace hell |
|
|
By brian68 - Posted on March 1, 2005 - 18:03:06 (#16040)
Current version when comment was posted: 4.0-BeOS-AGMS-1.18 |
|
|
AGMS -
Aren't those namespaces *fun*? I remember crashing into walls with those when porting to ppc in the past. Fortunately there are some brilliant ppc-aware devs out there to help the rest of us slog through it. Thanks for your work on this!
|
|
| ppc version |
|
|
By Tenzin - Posted on February 27, 2005 - 16:48:33 (#15996)
Current version when comment was posted: 4.0-BeOS-AGMS-1.18 |
|
|
using it now to typo this on my thinkpad in win2k to net+ in R503 on my ppc 5500.
thanks AGMS :)
|
|
| VNCServer for PPC (PowerPC) Ready! |
|
|
By Alexander G M Smith - Posted on February 27, 2005 - 13:45:36 (#15992)
Current version when comment was posted: 4.0-BeOS-AGMS-1.18 |
|
|
After some hassles with STD:: namespace problems in the PowerPC compiler, I was able to get VNCServer working. Even the BDirectWindow fast screen update method works, on my PowerComputing Mac clone!
- Alex
|
|
| Re: VNC Client for BeOS |
|
|
By mmu_man - Posted on January 7, 2005 - 06:25:42 (#15311)
Current version when comment was posted: 4.0-BeOS-AGMS-1.15 |
|
|
I might have a look at that.
Meanwhile my latest version of the client is quite functional anyway, just need to add a mouse cursor so you don't get lost.
|
|
| VNC Client for BeOS? |
|
|
By Alexander G M Smith - Posted on January 6, 2005 - 19:13:36 (#15308)
Current version when comment was posted: 4.0-BeOS-AGMS-1.15 |
|
|
Nope, mmu_man, I haven't started a VNC client for BeOS and don't plan on doing one (too many other higher priority projects). Maybe someone else could take up the cause and make use of RealVNC's new source code to whip up a client? Their redesigned class structure should make it easy - they do the bitmap depth conversions and network encoding / decoding for you.
- Alex
|
|
| nice |
|
|
By mmu_man - Posted on January 6, 2005 - 00:32:14 (#15299)
Current version when comment was posted: 4.0-BeOS-AGMS-1.15 |
|
|
Just hope the code is readable :P
Let's try that.
Did you do any work on the client yet ?
I do have some unreleased stuff on vncclient around.
|
|
| Supported Video Cards |
|
|
By Alexander G M Smith - Posted on January 4, 2005 - 21:18:34 (#15291)
Current version when comment was posted: 4.0-BeOS-AGMS-1.15 |
|
|
It's useful to know that it works on the latest Zeta, and I can add the Voodoo3 to the cards list.
Yup, Dane did want something like this, and you can thank his persistent interest in getting me to get it half done. Plus I can use my BeOS system from work to double check our external web site availability (and NetPositive compatibility :-).
- Alex
|
|
| Great job AGMS! |
|
|
By Zaranthos - Posted on January 4, 2005 - 11:12:04 (#15286)
Current version when comment was posted: 4.0-BeOS-AGMS-1.15 |
|
|
I'm sure a lot of people are gonna appreciate this. Dane Scott wanted something like this long ago I think. :)
|
|
| Voodoo3 2000 |
|
|
By guildencrantz - Posted on January 4, 2005 - 09:21:24 (#15281)
Current version when comment was posted: 4.0-BeOS-AGMS-1.15 |
|
|
I'm running VNCServer on Zeta Neo SP1 with a Voodoo3 2000. It's done a great job.
~/Matt
|
|
| Re: Nice work |
|
|
By Alexander G M Smith - Posted on January 3, 2005 - 21:06:10 (#15276)
Current version when comment was posted: 4.0-BeOS-AGMS-1.15 |
|
|
Good to hear that it's working. Another Radeon and a Neomagic video board too, nice to know they work.
Unfortunately I don't have time to do a VNC client for BeOS (the server project was started in October 2003 - over a year ago!). Maybe someone else with C++ experience and more spare time (got a full time job now) can do one, since the VNC code is so nicely designed that most of the work is done.
- Alex
|
|
| Nice work |
|
|
By backupwww - Posted on January 3, 2005 - 18:46:40 (#15274)
Current version when comment was posted: 4.0-BeOS-AGMS-1.15 |
|
|
I test your work in LAN and than I show it a friend by WAN with a dyndns account. I show him my used Apps on a Zeta System with the Radeon Drivers from Thomas Kurschel and BeOS R5 Pro/Bone on my small 300 MHZ Thinkpad with the Neomagic Drivers from Rudolf Cornelissen. My friend was "begeistert". :) He explored my BeOS Systems and he had no problems to start and watch the apps.
Is there a chance to use a new BeOS Client soon? As Example to help new BeOS Users from my prefered OS. I run a test with VNC Viewer (http://www.bebits.com/app/2329) but this client has a problem with a visible mousepointer for the client user.
|
|
| Re: Compatible video |
|
|
By Alexander G M Smith - Posted on January 3, 2005 - 13:20:09 (#15268)
Current version when comment was posted: 4.0-BeOS-AGMS-1.15 |
|
|
Nice to hear that it works on Radeons, or at least one Radeon.
Yes, if BDirectWindow and your video card don't work for MESA, then they won't work in VNCServer (even more likely since VNCServer runs it in the more demanding windowed mode, not full screen mode).
- Alex
|
|
| Re: Mouse doesn't Work |
|
|
By Alexander G M Smith - Posted on January 3, 2005 - 13:15:34 (#15267)
Current version when comment was posted: 4.0-BeOS-AGMS-1.15 |
|
|
Possibly the input server add-on isn't installed. See the readme for how to install InputEventInjector, which simulates a mouse and a keyboard.
|
|
| Work very well |
|
|
By Fabien26 - Posted on January 3, 2005 - 12:57:17 (#15266)
Current version when comment was posted: 4.0-BeOS-AGMS-1.15 |
|
|
but the mouse doesn't work
|
|
| Compatible video |
|
|
By m_eiman - Posted on January 3, 2005 - 12:07:58 (#15263)
Current version when comment was posted: 4.0-BeOS-AGMS-1.15 |
|
|
Works fine on a Radeon. I'm guessing it won't work on the Matrox G400, since I get the same error when trying to run MESA on it.
- Mikael
|
|
| Video Board Compatibility List? |
|
|
By Alexander G M Smith - Posted on January 3, 2005 - 11:15:09 (#15262)
Current version when comment was posted: 4.0-BeOS-AGMS-1.15 |
|
|
Nice to hear that it's working Matt.
By the way, I'd be interested in hearing which video boards VNCServer (and thus BDirectWindow) works with and which ones it doesn't. I know it works with nVidia GeForce 2 and earlier ones, and not the default VESA video driver for unsupported boards. But does it work / not work for any other kinds of video boards?
- Alex
|
|
| Bless You! |
|
|
By guildencrantz - Posted on January 3, 2005 - 10:55:53 (#15261)
Current version when comment was posted: 4.0-BeOS-AGMS-1.15 |
|
|
Over the last few days I've definitely suffered productivity because BeOS won't work on my laptop and previous VNCServers were, well, unusable.
I can code in BeOS from my laptop now! Yeah!
~/Matt
|
|
| Re: Windowed mode not supported for BDirectWindow? |
|
|
By Alexander G M Smith - Posted on January 3, 2005 - 08:43:15 (#15260)
Current version when comment was posted: 4.0-BeOS-AGMS-1.15 |
|
|
If you get the message "Windowed mode not supported for BDirectWindow, maybe your graphics card needs DMA support and a hardware cursor)" then your video card isn't supported in this version. The code uses the BeOS "BDirectWindow" facility to read screen memory directly. However, not all video cards support that, and in particular the generic VESA drivers don't support it.
I have it working here with my nVidia GeForce 2 MX 400 card, you could pick up a similar one (GeForce 2 or earlier) fairly cheaply, and use the http://www.bebits.com/app/1622 driver. Or wait for me to try implmenting a backup screen reader using the "BScreen" facility, which I think supports more cards but is much slower since it copies the image to a separately allocated bitmap buffer every time it reads the screen.
- Alex
|
|
| Windowed mode not supported for BDirectWindow ? |
|
|
By hey68you - Posted on January 3, 2005 - 05:27:54 (#15258)
Current version when comment was posted: 4.0-BeOS-AGMS-1.15 |
|
|
I get the following error:
Windowed mode not supported for BDirectWindow, maybe your graphics card needs DMA support and a hardware cursor)
Please advise :)
|
|
|
|
|
