Hi

I'm looking for a VNC server and client to run under AOS4.

I can't find zvnc for classic Amigas anymore and AmiVNC crashes my A1.

Is there a functional version available for classic Amigas and native AOS4 for A1s?

Thx.

_________________
A computerworld without MS products and Windows!
Connect your Amigas ...
...The Red ONE-A1XE G4 - A3000T- A3000 - A4000 - A2500- A1000 - A600 - CDTV - CD32...
and your PDAs and laptops ...
Psion 5mx Pro - Psion NetBook - Apple iPhone - MacBook Pro

@mbilla

[Via AmigaOneProductions]

http://s.guillard.free.fr/AmiVNC/AmiVNC.htm
That's the server... which works very well on my A1
Client...
http://dspach.free.fr/
On the left hand side you should find a VNC viewer for the Amiga.

Are you running the planar & chunky version of the server?

_________________
I came, I saw, I want one!

nettor si swodniw
leurc si swodniw
liame ym eta swodniw
oot evi

@mbilla

I've got vva running on my Amiga One. It is a VNC client only. I can connect it to my linux machine over ethernet, and it works. Screen refresh is a little slow, but that's to be expected.
This is available from here .

On the same site, there is also a VNC server. It looks like it should work, but i can't get the OS4 version of Picasso96 to pick up the fake graphic board it uses. This is apparently a rather odd implementation of VNC according to some comments I've read elsewhere on the web. It is very amiga-centric, since it basically sets up a virtual graphics board driver called p96fb.board, which actually sends VNC data over ethernet instead of to a monitor. You then set up a Picasso96 screenmode and attach the settings to this board, using Picasso96Settings in Prefs: Then select this screenmode in the application you want to serve to the remote machine.

Anyway, the installation instructions say where to install the fake graphics board driver, but this directory doesn't exist in AOS4. Instead, Picasso96 looks for a board driver called AmigaOne.board inside the kickstart drawer. However, if I put p96fb.board there, Picasso96 doesn't find it on startup. It seems like the AOS4 version of Picasso96 doesn't look for mutliple boards any more but just defaults to AmigaOne.board. i can't find any tooltypes, ENV variables, or startup-sequence items that tell me how to redirect Picasso96 to pick up this board. It may not be possible.

The other VNC server, AmiVNC does not crash here, but doesn't work correctly either. if I set Workbench to be a 16 bit screen, then AmiVNC will serve the virtual Workbench screen to my linux machine, but the mouse doesn't work. If I go to the AmigaOne and use the mouse there, the mouse pointer on the linux screen will follow, but if I use the mouse on the linux screen, the AmigaOne mouse pointer will not follow it. However, mouse clicks do work. If I use the AmigaOne mouse to position the pointer over an icon and then double click on it from the linux screen, the icon will open and both screens will update to show the open icon. The keyboard works (if I remember correctly), but again, the keyboard mouse positioning commands using the arrow keys do not work. So currently I can see my Amiga screen, click on whatever my mouse happens to already be pointed at, and type text into a window that my pointer happens to be over. Not exactly productive.

Besides this, the colors aren't right. It looks like the color bytes are RGB the but linux screenmode I'm using is BRGA. There are tooltypes in the AmiVNC that are supposed to change the color byte order, but they don't seem to do anything. This is as far as I've been able to get. If you have any more success than I did, please let me know. If you would like to see the settings I used on AmiVNC, send me a private message here at amigaworld.net giving my your email address, and i can send the stuff to you.

Hope this helps.

--Stuart Anderson

@mbilla

This is a really important thing we NEED for OS4. I've emailed dspach@free.fr about ten times without a reply. It's really sad cos I want a good X-server ported to OS4 as well.

I still belive!

/shoe

@mr_homm

Unfortunately, I have the same problems as you, mr_homm. VVA works very well (and is as fast as the Linux client I used on my A1 before I installed OS4). AmiVNC (the server) runs quietly in the background waiting for a connection, authenticates properly on a remote connection, sends the screen to the remote client, doesn't accept any mouse input. All keypresses from the remote keyboard are accepted and processed but NONE from the mouse.
I emailed Stephane Guillard to ask him if he could look into this for OS4 but got no reply.

I thought I had cracked it when I read the docs about setting softsprite=yes in devs:monitors/radeon but this makes no difference.

I wondered if it was due to the changes in the new way that OS4 accepts inputs.

This is a high priority for me, I am seriously hampered by not having a working VNC. I reckon a native PPC version would be excellent. The sources for AmiVNC are included in the archive - maybe someone could have a go at porting it to OS4? ( I really don't have the time until my degree is finished and I seriously doubt I have the skills anyway.)

_________________
AmigaONE XE G4
____________________

@mr_homm

"On the same site, there is also a VNC server. It looks like it should work, but i can't get the OS4 version of Picasso96 to pick up the fake graphic board it uses"

I discounted this version of VNC server because the docs state it uses the mmu and I think I read somewhere that OS4_pre doesn't implement the mmu.

_________________
AmigaONE XE G4
____________________

@gadgetgaz

Hi,

I have uploaded the OS4 version of AmiVNC to os4depot.

This version also fixes the 'no mouse move' bug, it was a wrong message size to input.device, only in the case of mouse moves (was right for mouse clicks & keys).

Here I run it on my LAN with an old WinVNC client, and with a delay set to 10 on AmiVNC side, it is almost realtime OS4 display on the PC

Kind regards,
--
Stéphane Guillard

@sg2

Greaaaaat!! I need this program like the bread!!

_________________
http://www.amigasoft.net

@sg2

Fantastic news! I will try this as soon as possible. Thankyou!

_________________
AmigaONE XE G4
____________________

@sg2

It's a vnc server right? Couldn't get it to work. realvnc (win32) can't connect to it anyway.

/Björn

Just to clarify. When I start it nothing happens. The home page says that it should output something like:

AmiVNC 0.1.0 Mar 1st 2001 (VVA support)
(c) 1999-2001 stephane.guillard@steria.com
main.c / main : parameter values :
- listen port set to 5900
- endian set to little
- initial xfer limit set to FFFFFFFF
- color bitshifts : red 8, green 16, blue 24
main.c / main : Creating listener socket
main.c / main : Binding socket on port 5900
main.c / main : Listening set on port 5900
main.c / main : Waiting for client connection

But I get absolutely nothing. I can't ctrl+c it though. But other than that .. just .. nothing.

/Björn

@Orgin

You have to launch AiVNC with the '-v' argument if you want output to go to the shell, otherwise it goes to t:amivnc.log iirc.

Nothing happening is a good sign btw, AmiVNC is a server, you have to connect to it using a VNC client on another machine.

Myself, I connect to AmiVNC from various PC's using WinVNC 3.3.3 (I only use the client, which is 'VNCViewer', you don't need to install/run the other parts).

Kind regards,
--
Stéphane Guillard

@sg2

Yeah as I said reals VNC can't connect to it for some reason. This is the output I get when using -v :

main : accept()ed connection from *CENSOR* on socket 1
main : Negociating protocol version
main : Protocol supported by server : 3.3, by client : 3.3
main : Authentication
AmiVNC - main : Authenticate error (0)
AmiVNC session closed
main : Waiting for client connection

/Björn

@sg2

Just tried with winvnc, same result.

/Björn

@Orgin

Authentication failed : you did not set the password.

On the amiga side, please enter in a shell : 'amivnc -pabcd'

This will set the password to 'abcd'.

Then when your client will prompt for password, enter 'abcd' and it should connect.

Kind regards,
--
Stéphane Guillard

@sg2

I've set the password now then (I'll add instructions to the readme on os4depot). I get an image in winvnc but as soon as I try to do something:

5.Work:BH/BHData10/AmiVNC4-2.0.0> AmiVNC4 -v
AmiVNC OS4 2.0.0 Dec 22 2004
(c) 1999-2004 stephane.guillard@intest.info
main : parameter values :
- listen port set to 5900
- endian set to little
- initial xfer limit set to FFFFFFFF
- color bitshifts : red 8, green 16, blue 24
- log file set to stdout
- VVA BGR233 encoding : no
- user command on client login : none
- user command on client logout : none
main : Creating listener socket
main : Binding socket on port 5900
main : Listening set on port 5900
main : Waiting for client connection
main : accept()ed connection from *CENSOR* on socket 1
main : Negociating protocol version
main : Protocol supported by server : 3.3, by client : 3.5
main : Authentication
main : ClientInitialisation
main : SharedFlag = 0 (multiple clients : No)
main : Screen set to [Workbench Screen] (RTG)
main : RTG mode Pic96/12 @ 0x80000000, 1600x1200, 4 Bpp, size 7680000
main : prepared duplicate socket key 1167423252
vProcessIncomes : got duplicate socket key 1167423252
vProcessIncomes runs on socket 0

Crash log here:

crashlog

In reals vnc (using prot 3.3 on both sides) it opens up a garbled screen and closes it with a "rect to big" requester (on the win32 side).

/Björn

@sg2

I can now connect as well (thanks to your little note on setting the password) but I also get a garbled screen and the colours are all wrong (there's no dark green or pink on my workbench!).

Any ideas? Connecting with vnc3.3 on my fedora core 2 box.

GiGa

_________________
Owner of uA1-C with OS4.0

@sg2

My output is this:

AmiVNC4-2.0.0 Dec 22 2004
(c) 1999-2004 stephane.guillard@intest.info
main : parameter values :
- listen port set to 5900
- endian set to little
- initial xfer limit set to FFFFFFFF
- color bitshifts : red 8, green 16, blue 24
- log file set to stdout
- VVA BGR233 encoding : no
- user command on client login : none
- user command on client logout : none
main : Creating listener socket
main : Binding socket on port 5900
AmiVNC - main : bind() error (48)
AmiVNC session closed
AmiVNC halted

What's wrong here ? do I have to set up something in roadshow ?

Hi,

Same here, it doesn't work but it does a bit more: I can run it on the A1 and I can connect to it with RealVNCviewer 3.3.4.0. It opens the visualization window and displays "please wait" on it then it closes the window.
It says on the shell: "RTG mode Pïc96/7 @ 0x80000000, 1024x768, 2 Bpp, size 1572864"

@Fraggel
AmiVNC - main : bind() error (48)
AmiVNC session closed

I had this when I run it after having set the password. I rebooted and it worked fine (well, like said above).

Last edited by elwood on 26-Dec-2004 at 03:13 PM.

_________________
Philippe 'Elwood' Ferrucci
Sam460 1.10 Ghz
AmigaOS 4 betatester
Amiga Translator Organisation

@giga

Bind error means either that the TCP/IP stack is not launched, or that the server is already running.

You can check that your TCP-IP stack is up using the 'ping' command in a shell, try to ping the machine on which you intend to run the client, like 'ping 192.168.0.2' or whatever IP address (or machine name if you have a DNS).

You can check if the server is already running or not using the 'status' command in a shell, enter 'status full' and see if AmiVNC is already there in the list.

Now, just to be sure that your Windows client does not require a protocol variant or compression that AmiVNC does not support, please use this VNC client which is the one I use and which I know is working.

If that setup works, I'll see to patch AmiVNC to support clients that would not work.

Kind regards,
--
Stéphane Guillard

Last edited by sg2 on 26-Dec-2004 at 04:17 PM.