@DATABASE vva.guide @WIDTH 80 ## $VER: vva.guide 0.9.6 (20-Sep-2000) @NODE MAIN "vva Documentation" @{b}vva - VNC Viewer Amiga@{ub} Version 0.9.6 (20-Sep-2000) Hello, this is the latest version of VVA derived from the initial version made by Joerg Dietrich. I made, now, quite a lot of modi- fications since release 0.1.3. Main changes are: - WB3.0 compatible - launchable from Workbench or CLI - RTG compatible (and taking advantage of it) - clipboard support - starting from V0.9.3, hi and true color support on Workbench - web site and email have changed, see below for latest informations on VVA: www: http://dspach.free.fr email: dspach@free.fr for latest information on VNC: www: http://www.uk.research.att.com/vnc/index.html Denis Spach @{"Requirements " LINK MyRequirements} @{"Usage " LINK MyUsage} @{"Hints " LINK MyHints} @{"History of my changes " LINK MyHistory} @{"Original documentation from Joerg" LINK OriginalDoc} @ENDNODE @NODE "MyRequirements" In order to use VVA you need the following minimum configuration - An Amiga capable to display at least 256 colors, AGA or gfx-card - CPU 68020 or better - AmigaOS 3.0 and up - A TCP/IP-stack, like Miami, AmiTCP (v3 and up), or Genesis - A running VNC-Server anywhere in your reachable network - reqtools.library In order to take advantage of more than 256 colors, a gfx-card is required with CyberGraphics or Picasso96 RTG software. @ENDNODE @NODE "MyUsage" @{u}CLI template@{uu} H=Host,P=Port/N,S=ScreenMode/N,Sh=Shared/S, VO=ViewOnly/S,R=Raw/S,C=CopyRect/S,Hx=Hextile/S, RRE=RRE/S,CR=CoRRE/S,P=PIP/S,RTG=RTGONLY/S,W=WINDOW/S, SP=SHAREDPENS/S,16=16BITS/S,32=32BITS/S,NB=NOBORDER/S, BD=BACKDROP/S for more explanations, see @{"Original documentation from Joerg" LINK OriginalDoc} @{"History of my changes " LINK MyHistory} see also tooltypes in icons provided in the archive @{u}Shortkeys@{uu} - Right-Amiga H Iconify - Right-Amiga Q Quit - Right-Amiga C paste to remote server (sends clipboard 0) - Right-Amiga-B Window/Screen to back - Right-Amiga-F Window/Screen to front - Right-Amiga-MouseBtn middle button emulation - Help NumLock toggle @ENDNODE @NODE "MyHints" VVA uses intensivelly graphics and network sub systems, so you have to take care of both. Experimenting on my stock A4000,68040,25MHz has given the following results best combination worst combination (5 times slower) - Picasso96 - Cybergraphics - AmiTCP or Genesis - Miami Since V0.9.5 16 and 32 bits remote depth are supported, use the 16BITS or 32BITS options for this. If RTGONLY option is also set, VVA will use the BestModeID function to find a correct screen mode. If not set, you will have to select the right screen mode in the screen requester. Since V0.9.4, you may now use the remote screen machine as your background image in your workbench (use NOBORDER with or without BACKDROP option). This can be helpful, if the remote screen dimensions fits your WB one's. The PIP feature is only available with specific graphic cards such as the PicassoIV. This has not been tested with Cybervision64/3D for now. If the PIP can not be open, a private screen is used instead. Furthermore PIP may only be used on a screen which is big enough to hold the whole remote screen plus the PIP window borders. For instance I use a 832x624 screen for a remote 800x600 screen. Note also that this also apply to the window mode. Some people reported strange behaviour when sending keys which do not range in the classic ASCII values 0x20-0x7e. Starting from version 0.9.5 this must be much better. AFAIK, only pure dead keys are not working properly, and the rest should be OK now. @ENDNODE @NODE "MyHistory" changes for V0.9.6 ------------------ - added some network buffering for less latency - documentation updates changes for V0.9.5 ------------------ - 16 bits depth on PIP had sometimes strange colors - some encoding changes for CTRL and ALT-SHIFT keys combinations (this should fix some reported problems with some Un*x servers) - 16 and 32 bits support for both Workbench and private screens, (using 16BITS or 32BITS options means VVA requests 16 or 32 bits depth graphics data from from the VNC server that can be display on a 15/16 or 24/32 bits Workbench or private screen) changes for V0.9.4 ------------------ - new 32BITS tooltype and CLI option for 32 bits support on Workbench - new 16BITS tooltype and CLI option for 16 bits support on WB and PIP - new NOBORDER tooltype and CLI option to remove window border on WB - new BACKDROP tooltype and CLI option for backdrop window on WB - fixed V0.9.2 bug which made some crash in certain conditions - new web site and email address changes for V0.9.3 ------------------ - interim version changes for V0.9.2 ------------------ - when using PIP with P96 on 8 bits screen, 16 bits PIP is now used - few speed improvements on 8 bits screens - paste to remote server shortkey (Right-Amiga-C, sends clipboard unit 0) - middle mouse button event send when clicking left mouse button with the Right-Amiga key down - window to back shortkey (Right-Amiga-B) - window to front shortkey (Right-Amiga-F) - keys formed using dead keys such as ôêâöë are handled (warning: some remote VNC servers or applications ignore them) - top keys on the numeric keyboard are handled changes for V0.9.1 ------------------ - paste from remote server REALLY works now ! (result in clipboard unit 0) changes for V0.9.0 ------------------ - new SHAREDPENS tooltype and CLI option (for window mode on 8 bits screens) - works now on 8/15/16/24/32 bits depth screen (no more palette probs)) - iconify shortkey (Right-Amiga H) - quit shortkey (Right-Amiga Q) - paste from remote server works (result in clipboard unit 0) - project icons to launch vva are supported - raised version number to 0.9.0 since 1.0 is pretty near changes for V0.2.1 ------------------ - Help key acts now as a NumLock key (status shown on PIP window) - when clicking outside PIP the mouse event is not send to server - CTRL-C disabled for PC remote cut'n'paste (still not working) - new RTGONLY tooltype and CLI option (force P96 screen modes) - new WINDOW tooltype and CLI option (force window display on public screen) - recompiled for 68020 changes for V0.2.0 since original version ----------------------------------------- - keyboard is now working - running on WB 3.0 is now working - PIP support when used with Picasso96 (PIP tooltype or PIP CLI option) - compiled for 68040 CPU's @ENDNODE @NODE "OriginalDoc" Version 0.1.3 (11-Jan-1999) @{"Introduction" LINK Introduction} @{"Requirements" LINK Requirements} @{"Installation" LINK Installation} @{"Usage" LINK Usage} @{"Limitations" LINK Limitations} @{"Future" LINK Future} @{"History" LINK History} @{"Copyright" LINK Copyright} @{"Distribution and Warranty" LINK Distribution} @{"Download" LINK Download} @{"Sourcecode" LINK Sourcecode} @{"Contact" LINK Contact} @ENDNODE @NODE "Introduction" @{b}Introduction@{ub} vva - VNC Viewer Amiga is a VNC-client for the Amiga. It can be used to connect your Amiga to a VNC-server. VNC - Virtual Network Computing is a simple way to redirect the screen of a far computer to your local desktop. For more information about VNC have a look at the VNC-homepage at @{b}http://www.orl.co.uk/vnc/index.html@{ub} To make it clear: you can display the contents of the screen of your Unix- or Windozebox on your Amiga. The other way would require a VNC Server Amiga, which still dosn't exists. But who knows :) @ENDNODE @NODE "Requirements" @{b}Requirements@{ub} Minimum: - An Amiga capable to display 256 colors, AGA or gfx-card (A nacked A1200 should be enough, but the faster, the better) - AmigaOS 3.0 or newer - A TCP/IP-stack, like Miami or AmiTCP/IP - reqtools.library, available at Aminet - A running VNC-Server anywhere in your reachable network Recommented: - A fast processor and network (no, a FPU or PowerPC dosn't speedup the thing) - A gfx-card, vva is very display-intensive - Some FastRAM for the chunky FrameBuffer (vva needs just 256 Bytes if it uses hextile-encoding but much more (upto ScreenWidth x ScreenHeight) with other encodings) - NewWPA8 from Aminet to speedup c2p on your AGA-machine upto 3 times (do @{b}not@{ub} use for gfx-card) - AmigaOS 3.1 for the fastest c2p (even 3.0 is to old!) As times go by, the V39-code is now nearly as fast as V40. @ENDNODE @NODE "Installation" @{b}Installation@{ub} Unpack the vva-archive to any destination you want. It dosn't need an installation. Make sure, that reqtools.library is in your LIBS: - drawer. Your TCP-Stack and the VNC-Server must be installed properly. @ENDNODE @NODE "Usage" @{b}Usage@{ub} Make sure that the VNC-Server is running and your network-connection is established. vva can be used either from shell or Workbench. It accepts the following arguments/tooltypes: HOST - hostname of the VNC-Server, e.g. HOST=warzenschwein or HOST=10.0.0.1 PORT - portnumber of the VNC-Server, e.g. PORT=6902 The portnumber is set by the VNC-Server. Now PORT=2 should work too. Very ugly bug. SCREENMODE - screenmode of the vva-Screen, e.g. SCREENMODE=167940 This must be a @{b}decimal@{ub} number. With the help of "mid" in the Tools-drawer you can find out this number for your prefered screenmode. SHARED - Set the Shared-flag, e.g. SHARED With the Shared-flag set you can have more then one VNC-Viewers per VNC-Server. Without it the VNC-Server closes the old connection if a new VNC-Viewer connects. VIEWONLY - Set the ViewOnly-flag, e.g. VIEWONLY With the ViewOnly-flag set no mouse- and keyboard-actions are transfered to the VNC-Server. RAW - Raw encoding, e.g. RAW COPYRECT - CopyRect encoding, e.g. COPYRECT HEXTILE - Hextile encoding, e.g. HEXTILE RRE - RRE encoding, e.g. RRE CORRE - CoRRE encoding, e.g. CORRE For a description of the encoding-types see the original VNC-documentation. vva uses as default Hextile- and CopyRect-encoding. Don't set the stacksize to small. The default 4096 bytes maybe enough but I suggest 10000 bytes as minimum. If none of the arguments/tooltypes are used, vva pops up some reqtools- requesters and asks for host and port, password and screenmode. vva opens it's own customscreen, Workbench-windows are currently not supported. If the screen is to small, vva uses Overscan. Pay attention, gfx-cards don't have Overscan. You have to provide vva with a screenmode that fits. Or you run the VNC-server with screensizes, you have a screenmode for. To interrupt vva, send it a CTRL-C from shell or use Commodities Exchange to @{b}Remove@{ub} the vva-Commodity. @ENDNODE @NODE "Limitations" @{b}Limitations@{ub} Only the BGR233-truecolor-mode is supported by now. This gives you 256 more or less ugly colors. Palette-mode wouldn't be the problem, but there is very little support for this from the VNC-Servers. 16- and 24bit truecolor is not supported. I don't have a gfx-card. The clipboard dosn't work, but I'm working on this. The Amiga-keyboard has some limitations (especially missing keys like F11 F12). But this is not my fault. The Amiga-keys are not mapped to the remote computer, because of the special meaning of some key-kombinations. Maybe you will get a M send, when you do LAmiga-M to switch screens. When you jump to another screen and come back to the vva-screen, you have to click on the screen, to aktivate it. This click is sent to the remote computer! Be carefull, where you click. The support for shell-arguments is a little buggy. Please start vva from the shell in the following form: vva: vva Host=warzenschwein Port=6902 Screenmode=167940 shared Use the '=' , don't use the shortcuts. This quirk will be fixed in the next release. @ENDNODE @NODE "Future" @{b}Future@{ub} A version for older Amigas is on the way. It reduces the ugly 256 colors to even uglier 16 colors. So it can be used with OCS- and ECS-Amigas. And it is much faster than the 256-color-one. I play arround with a black-and-white (or better gray-and-black) Workbench-version. Gray-and-black, because it uses only the first two colors (the first bitplane) of the Workbench-screen. I have contact to a programmer, who wants to do gfx-card- and Highcolor- / Truecolorsupport. First ideas of a Truecolor2grayscale-mode are tought. @ENDNODE @NODE "History" @{b}History@{ub} vva 0.1.3 (11-Jan-1998) fixed the Port-bug, faster c2p for WB3.0 special debug-version vva 0.1.2 (08-Dec-1998) first usable, comfortable version vva 0.1.1 (26-Oct-1998) bugfix for the black-squares-bug vva 0.1 (16-Oct-1998) initial version, it worked but wasn't very usable @ENDNODE @NODE "Copyright" @{b}Copyright@{ub} vva is in big parts Copyright (C) 1998, 1999 Joerg Dietrich A few parts of vva are Copyright (C) 1997, 1998 Olivetti & Oracle Research Laboratory, distributed under the @{"GNU General Public License" LINK COPYING/main} @ENDNODE @NODE "Distribution" @{b}Distribution and Warranty@{ub} This program is free software; you can redistribute it and/or modify it under the terms of the @{"GNU General Public License" LINK COPYING/main} as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the @{"GNU General Public License" LINK COPYING/main} for more details. You should have received a copy of the @{"GNU General Public License" LINK COPYING/main} along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA @ENDNODE @NODE "Download" @{b}Download@{ub} vva's homepage is http://www.fh-zwickau.de/~jod/vva/index.html There you can find the latest version of vva. Once when it is stable, I will upload it to the Aminet. @ENDNODE @NODE "Sourcecode" @{b}Sourcecode@{ub} The sourcecode is available on the vva-homepage. @ENDNODE @NODE "Contact" @{b}Contact@{ub} Send bugreports and suggestions to: joerg.dietrich@fh-zwickau.de @ENDNODE