first commit - moved from local dev to git

tools/zview/doc/copying.gpl

@@ -0,0 +1,340 @@
+		    GNU GENERAL PUBLIC LICENSE
+		       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+     59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+			    Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+		    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+			    NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+		     END OF TERMS AND CONDITIONS
+
+	    How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License 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 for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program; if not, write to the Free Software
+    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) year  name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  <signature of Ty Coon>, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Library General
+Public License instead of this License.

tools/zview/doc/history.txt

@@ -0,0 +1,223 @@
+25 December 2005: BETA7a
+========================
+
+- A version of zview compatible with MagiC OS is provided in the "MagiC"
+folder.
+
+
+24 December 2005: BETA7
+=======================
+
+News:
+-----
+- PDF:
+	* Huge quality improvement in the PDF font rendering (Atari specific).
+	* Zoom function added.
+	* Code upgraded to xpdf 3.01pl1( 2005-dec-01).
+- Complete EXIF 2.21 support for JPEG image( now, you can see various
+  usefull informations like when the picture was taken, if the flash of your
+  camera was fired or not, the model of your cam, etc...).
+- Now, zView can extract the thumbnails embedded inside JPEG images created
+  with a digital photo-cam.
+  That means than the thumbnail creation is 20 times faster if the JPEG was
+  created with a camera.
+- News options added:
+	* Skip drive( it's faster to skip the check of the CD-ROM drive for example).
+	* Smooth Thumbnail: now, you can smooth the thumbnails with various method.
+	  That is very slow and only available on true color or near true color
+	  display but the result are perfect( specialy with the lanczos computation). 
+	* PDF font antialiasing ON/OFF.
+	* Fit the PDF to the window.
+- Utilisation of an embedded font to have the same look on any computers.
+- Animated interlaced Gif and animated Gif with transparency now supported.
+- More zoom levels for the pictures( 25, 50, 100, 150 and 200%, previoulsy: 
+  50, 100, and 200%).
+- Some function's shortcuts added to the toolbars.
+
+
+Bugs fixes:
+-----------
+- Many fixes in the PDF code( PDF rotated, problems with some fonts, etc..).
+- Missing horizontal SLIDER computation in the PDF and image window.
+- Little memory leak corrected in the multi-timer function.
+- A memory block was not freed in the file_rename function.
+- Some redraw fixed ( PDF bookmark, etc...).
+- Others littles bugs fixed.
+
+
+Know bug:
+---------
+- On aranym, with the DSP cookie installed, some stranges problems append
+  when we write a JPG.
+
+  
+
+5 August 2005: BETA6
+====================
+
+News:
+-----
+- For compatibility with the PDF code, zview is now under GPL licence.
+- Animation support added.
+  The first format benefitting of that is the animated GIF( SPACE key for 
+  pause/resume).
+- PDF read support( You will need a lot of memory to read a PDF).
+- Reservoir Dogs Godpaint write and read support.
+- Zoom available with the window's toolbar or the '+' and '-' keys.
+- Documentation and desktop icon added by Sacha Uhlig, many thanks to him !
+- French translation by Cyril Lefebvre, thanks to him !
+- Now, we can save from an interlaced picture.
+- The scrolling in the picture's window and the redraw function are a 
+  little bit faster.
+- Custom font added for the Exif Panel to see more lines.
+- 'VDI-Enhancer' from the Behne Bros provided in the "goodies" folder.
+  Install it if you use the standard Atari VDI without NVDI/fVDI/etc..
+- Others littles changes like Control+U to close the window instead of 
+  Control+W ( standard), menubar desactivation when we load a picture, 
+  'out of memory' warning in full screen code, etc...
+
+
+Bugs fixes:
+-----------
+- Remove unecessary redraws of the menu bar when we scroll the window and
+  in the browser window when this one is opened.
+- Now, when you enter in a directory and you go back again, the old 
+  directory remains selected. the code was there but it was wrong.
+- Static MDFB struct. were freed in 'winimg' and full screen code !  
+- The 1 plane pictures and icon were not correctly drawn in fullscreen mode
+  and in the browser's toolbar.
+- The progress bar was one pixel too wide and high.
+- Problem with 1 bits degas picture corrected.
+- Now, the background in full screen mode is always black.
+- In the Gif codec, a crash occured if the picture's text data was greater 
+  that 255 lines.
+- Uncorrect translation in the GUI ( octets -> bytes, etc...).
+
+
+Know bug:
+---------
+- On aranym, with the DSP cookie installed, some stranges problems append
+  when we write a JPG.
+- Various animated GIF are badly rendered.
+- With some rare PDF, the fonts are outlined.
+- The decoding of PDF with big pictures inside is very slow ( not really a 
+  bug but this code must be rewrote).
+
+
+
+20 february 2005: BETA5
+=======================
+
+News:
+-----
+- 68000, 68020 without FPU and 68020-60 version of the codecs and binaries 
+  available.
+- Full screen mode with automatic picture resize if this one is bigger that
+  the screen. ( F10 shortcut)
+- Another cool feature: when a window is iconified, zview show a thumbnail 
+  of the picture inside.
+- With the last Aranym from CVS, the JPG pictures are decoded natively with 
+  the host CPU !! ( to use this feature, "nfjpeg.prg" in your 'auto' folder
+  before MiNT). Many thanks to Patrice Mandin for his work on Aranym !
+- The DSP and the main JPG codecs are now merged in only one codec.
+  If the brainstorm's cookie is detected and you haven't a 68060, the JPG is
+  decoded with the DSP, else the CPU routine is used. 
+- Support of DEGAS compressed added ( PC1,PC2,PC3).
+- Others littles changes like recompilation of all the codecs with the last 
+  GCC, the possibility to move the about box with Xaaes, informations about 
+  the licence, etc...
+
+
+Bugs fixes:
+-----------
+- Many problems on others OS that MiNT are corrected, for exemple, the 
+  plugins were not loaded if this ones were in the global folder 
+  ( aka "LDGPATH/codecs") under TOS and MagiC, etc etc...
+- Problems with some degas images fixed.
+- With the DSP, JPG pictures not multiple of 16 were badly decoded. 
+- In planes < 8 bits, the toolbar's icons was not shown.
+- VDI's EDDI check at the start.
+- Zview saves the browser's coordinates when we quit the application.
+  Now, this coordinates are not saved if this window is iconified ( for 
+  prevent bad browser coordinate on next relaunch). 
+- Others littles bugs fixes like with the menu bar handling, error messages
+  not correct, etc etc...
+
+
+
+23 december 2004: BETA4
+=======================
+
+News:
+-----
+- The plugins are now in "codecs" directory, this one must be installed in  
+  "c:/gemsys/ldg/codecs" because some applications will use it.
+- Read & Write codecs for TIFF added. ( almost all variants supported !!!)
+- Read codecs for FAX added.
+- Read codecs for Eureka RAW data added.
+- Degas codecs read also Degas Elite uncompressed image now 
+  ( Thanks for the documentation Adam!).
+- The encoder and decoder are now in the same plugin.
+- Navigator frame scrolling optimised.
+- Some internal change in picture to screen convertion.
+
+
+Bugs fixes:
+-----------
+- Extra check for reverse pixel byte added to support 15, 16, 24 and 32 bits 
+  mode of some weired Hades VDI driver ( for Falcon NOVA card also).
+- Picture with 4 characters extention ( like "*.jpeg" or "*.tiff") are now 
+  handled correctly.
+
+
+
+25 november 2004: BETA3
+=======================
+
+News:
+-----
+- zView goes to LGPL.
+- TGA read plugin added( 15, 16, 24, 32 bits normal and compressed).
+- BMP read plugin added( 1, 4, 8, 24 bits non compressed).
+- JPG read plugin with DSP added. ( move JPG.LDG from '/dsp'
+  to '/plugin/decoder' and install jpgd.prg in your auto folder).
+- Option panel for the jpg encoder added... with this one, you can 
+  set the image quality wanted, progressive and grayscale mode.
+- The image viewer provides now a Info bar with basic information like 
+  resolution, color bits and image type.
+- Add delete function in the menu bar.
+- MEM.LDG from dominique Bereziat is now used for memory allocation 
+  ( more safe for MagiC system).
+- The dithering routine is now better for 8 and 4 bits resolution.
+- Handle of multi-pages Image format; first step for the fax and PDF 
+  reading.
+- Menu "history" activated.
+- the "jpe" image are now decoded with the JPG plugin.
+
+
+Bugs fixes:
+-----------
+- Some XGEM picture from old french application with non standard data caused
+  a crash under MagiC.. Now the line buffer is greater to avoid overflow.
+- Bugs fixe in the alpha code in PNG plugin.
+- The numpad key was not usable for rename a file.
+- redraw issue when the slider was used and a part of the window was outside 
+  the screen area.
+- The information dialog returned 0 colors for 24 bits img picture. 
+- Little bug fixe in rename function.
+- When you renamed a folder, the change was not done in the tree browser.
+- The use of a specific MiNT function ( Fxattr) made that the neochrome and 
+  degas picture wasn't displayed under plain TOS.
+- Fixe a little problem of allignement of the text in catalog tree when we 
+  change the font.
+- Fixe a bug that occurs when we deleted a folder in a "very depth" folder...
+  It was not deleted in the tree catalog.
+- Fixe a bug in the infobox, the '/0' null character was not put when the 
+  picture comes from fileselector, shame on me.
+
+
+
+28 october 2004: BETA2
+======================
+
+- First public release.

tools/zview/goodies/enhancer/docs/english/enhancer.txt

@@ -0,0 +1,20 @@
+VDI-Enhancer V1.00
+==================
+
+   VDI-Enhancer extends the ATARI VDI with new VDI functions for managing   
+   off-screen bitmaps and with the function vq_scrninfo().
+
+   In addition it replaces on Falcons in High-color mode (or True- color as 
+   it is called by ATARI :-) the non-working function v_get_pixel().
+
+Installation:
+=============
+   To install Enhancer, you have to copy it into your AUTO folder. If you   
+   use SPDOGDOS, Enhancer must be physically after SPDOGDOS.
+
+Note:
+=====
+   Enhancer shouldn't be used with NVDI because the provided functions 
+   already exists in NVDI 2.5 and older NVDI versions do not support 
+   monochrome bitmaps when working with color modes.
+

tools/zview/goodies/enhancer/docs/german/enhancer.txt

@@ -0,0 +1,89 @@
+VDI-Enhancer V1.00
+==================
+
+   Der Enhancer erweitert das ATARI-VDI um die neuen VDI-Funktionen zur 
+   Verwaltung von Off-Screen-Bitmaps und um die Funktion vq_scrninfo(). 
+
+   Au<41>erdem hat der Enhancer den angenehmen Effekt, die auf Falcons im 
+   High-Color-Modus (bzw. True-Color, wie ATARI es zu nennen pflegt :-), 
+   nicht funktionierende Funktion v_get_pixel() zu ersetzen.
+
+Installation:
+=============
+   Um den Enhancer zu installieren, m<>ssen Sie ihn nur in den AUTO-Ordner 
+   kopieren. Er mu<6D>, falls SPDOGDOS vorhanden ist, im AUTO-Ordner 
+   physikalisch dahinter liegen. 
+
+Hinweise:
+=========
+   Der Enhancer sollte nicht mit NVDI zusammen benutzt werden, da die von 
+   ihm bereitgestellten Funktionen in NVDI 2.5 schon existieren und in 
+   <20>lteren NVDI-Versionen keine monochromen Bitmaps im Farbbetrieb 
+   unterst<73>tzt werden.
+
+Beschreibung:
+=============
+   Der VDI-Enhancer erweitert in der jetzigen Form das ATARI-VDI oder dazu 
+   kompatible Bildschirmtreiber um die Funktionen v_opnbm() (OPEN BITMAP) 
+   und v_clsbm() (CLOSE BITMAP) zum Verwalten und Bearbeiten von 
+   Off-Screen-Bitmaps.  
+
+   Mittels dieser beiden Funktionen ist es m<>glich, Off-Screen-Bitmaps im 
+   ger<65>teabh<62>ngigen Format mit der Farbtiefe der jeweiligen Aufl<66>sung und 
+   beliebiger Breite und H<>he zu bearbeiten. Dadurch kann man VDI-Ausgaben 
+   auf einem Hintergrundschirm vornehmen und anschlie<69>end dessen Inhalt 
+   ohne Benutzung von vr_trnfm() auf den sichtbaren Bildschirm kopieren. 
+   Bei einigen Anwendungen f<>r Off-Screen-Bitmaps ist Farbe nicht 
+   notwendig, bzw. verbraucht unn<6E>tig viel Speicher. Daher kann man auch in 
+   Farbaufl<66>sungen mit v_opnbm() monochrome Bitmaps anlegen. 
+
+   Au<41>erdem bietet der Enhancer durch die Funktion vq_scrninfo() 
+   Informationen <20>ber das ger<65>teabh<62>ngige Bildschirmformat. Diese Funktion 
+   d<>rfte f<>r alle, die z.B. Farbbilder sichern, hilfreich sein.  
+
+Cookies und XBRA-Kennung:
+=========================
+   Der Enhancer installiert ebenso wie NVDI einen Cookie mit der Kennung 
+   'EdDI'. Das auf diese Kennung folgende Langwort ist die Adresse eines 
+   Funktionsdispatchers, der mit der Funktionsnummer in Register d0 
+   aufgerufen wird. Der Aufruf erfolgt nach den Pure C-Konventionen 
+   (Register d0-d2/a0-a1 und der Stack werden zur Parameter<65>bergabe 
+   benutzt). 
+   
+   Bisher existiert nur die Funktion 0, die als Funktionsresultat eine 
+   Versionsnummer zur<75>ckliefert, anhand er man auf die unterst<73>tzten 
+   Funktionen schlie<69>en kann. 
+
+   Ab Version 1.00 ($100 wird zur<75>ckgeliefert) sind die Funktionen 
+   v_opnbm(), v_clsbm() und vq_scrninfo() vorhanden. 
+
+Weitergabe des Enhancers und Copyright:
+=======================================
+
+   Die Weitergabe des VDI-Enhancers ist unter der Bedingung, da<64> dieser 
+   Text zusammen mit der Enhancer-Dokumentation mitgegeben wird, 
+   grunds<64>tzlich erlaubt. Der Vertrieb des Enhancers im Zusammenhang mit 
+   anderen Software-Produkten ist erlaubt, sofern dem Kunden dadurch keine 
+   zus<75>tzlichen Kosten entstehen und der empfohlene Verkaufspreis dieser 
+   Software 50 DM nicht <20>bersteigt. 
+
+   Auch dabei mu<6D> dieser Text mitgeliefert werden. Der Verkauf des 
+   VDI-Enhancers ist verboten. Er darf in PD-Sammlungen nur angeboten 
+   werden, wenn der Diskettenpreis unter 10 DM pro Diskette liegt. 
+
+   Ein Vertrieb <20>ber CHANNEL VIDEODAT oder <20>hnliche kommerzielle Systeme 
+   ist untersagt. 
+
+   ** Ausnahmen bed<65>rfen einer schriftlichen Genehmigung der Autoren! **
+     
+   Das Copyright verbleibt allein bei den Autoren, Sven & Wilfried Behne
+   E-Mail: Wilfried Behne @H
+   Fehlermeldungen und Verbesserungsvorschl<68>ge k<>nnen an diese Adresse 
+   geschickt werden.
+
+Ausschlu<EFBFBD> der Haftung:
+======================
+
+   Die Haftung f<>r unmittelbare und mittelbare Sch<63>den, Folgesch<63>den und 
+   Drittsch<63>den durch die Benutzung des VDI-Enhancers ist ausgeschlossen. 
+

tools/zview/goodies/enhancer/docs/german/neue_fkt.txt

@@ -0,0 +1,359 @@
+                        Neue Funktionen in NVDI 2.50
+                        ============================
+
+   Nachfolgend werden in dieser Datei die neuen Funktionen aufgef<65>hrt, die 
+   NVDI f<>r Bildschirmausgaben anbietet.
+
+1. Off-Screen Bitmaps
+=====================
+
+   F<>r viele Anwendungen ist es sehr n<>tzlich, wenn Zeichenfunktionen nicht 
+   direkt auf den Bildschirm, sondern auf einen nicht sichtbaren Bildschirm 
+   angewendet werden k<>nnen. Einen derartigen "versteckten" Bildschirm 
+   nennt man Off-Screen-Bitmap.
+   Zur Erzeugung von Off-Screen-Bitmaps dient die Funktion OPEN BITMAP.
+   Man kann ihr entweder die Gr<47><72>e eines Bitmap angeben, die Sie allozieren 
+   soll, oder ihr eine Bitmap <20>bergeben. Die Bitmap wird im gleichen Format 
+   wie die des Bildschirms verwaltet, wodurch schnelles Kopieren zwischen 
+   beiden m<>glich ist.
+   Die Funktion CLOSE BITMAP schlie<69>t eine mit OPEN BITMAP erzeugte Bitmap 
+   und  gibt gegebenenfalls deren Speicher zur<75>ck.
+
+
+      OPEN BITMAP (VDI 100, 1)
+
+      void  v_opnbm( WORD *work_in, MFDB *bitmap, WORD *handle, WORD *work_out )
+      {
+         pb[1] = work_in;
+         pb[3] = work_out;
+         pb[4] = work_out + 45;
+
+         contrl[0] = 100;
+         contrl[1] = 0;
+         contrl[3] = 20;
+         contrl[5] = 1;
+         *(MFDB *)&contrl[7] = bitmap;
+
+         vdi();
+
+         *handle = contrl[6];
+         pb[1] = intin;
+         pb[3] = intout;
+         pb[4] = ptsout;
+      }
+
+      Best<73>ckung der VDI-Arrays:
+
+       Feldelement      | Belegung
+      ------------------|-------------------------------------------
+      contrl[0]         | 100    Funktionsnummer f<>r v_opnbm()
+      contrl[1]         | 0      Anzahl der Eintr<74>ge in ptsin
+      contrl[2]         | 6      Anzahl der Eintr<74>ge in ptsout
+      contrl[3]         | 20     Anzahl der Eintr<74>ge in intin
+      contrl[4]         | 45     Anzahl der Eintr<74>ge in intout
+      contrl[5]         | 1      Unterfunktionsnummer f<>r v_opnbm()
+      contrl[6]         | handle
+      contrl[7..8]      | bitmap Zeiger auf einen MFDB der Bitmap
+                        |
+      intin[0..19]      | work_in[0..19]
+                        |
+      intout[0..44]     | work_out[0..44]
+                        |
+      ptsout[0..11]     | work_out[45..56]
+
+
+      handle:           graf_handle()
+
+      work_in[0..10]:   wie bei v_opnwk()/v_opnvwk() definiert
+      work_in[0]:       Getrez() + 2
+      work_in[11]:      Breite -1 (z.B. 1279)
+      work_in[12]:      H<>he -1 (z.B. 959)
+      work_in[13]:      Breite eines Pixels in Mikrometern
+      work_in[14]:      H<>he eines Pixels in Mikrometern
+      work_in[15..19]:  reserviert, sollte 0 enthalten
+
+      Achtung: Der Eintrag work_in[11] sollte bei Addition von 1 ohne Rest 
+               durch 16 teilbar sein. Andernfalls rundet der VDI-Treiber 
+               auf den n<>chsth<74>heren ohne Rest teilbaren Wert.
+
+      Hinweis: Wird f<>r Pixelbreite und -H<>he 0 angegeben, so werden die 
+               Werte des Bildschirms benutzt.
+
+      work_out[0..1]:   wie bei v_opnwk()/v_opnvwk() definiert
+      work_out[2]:      0
+      work_out[3..38]:  wie bei v_opnwk()/v_opnvwk() definiert
+      work_out[39]      0 (keine Hardware-Palette vorhanden, da Bitmap)
+      work_out[39..56]: wie beiv_opnwk()/v_opnvwk() definiert
+
+      bitmap:           Zeiger auf einen MFDB
+
+      Falls bitmap->fd_addr gleich NULL ist, so wird anhand der Gr<47><72>en- 
+      angaben in work_in Speicher f<>r die Bitmap angefordert (die Bitmap 
+      wird im Gegensatz zu v_opnvwk() gel<65>scht).
+
+      Um eine Bitmap im ger<65>tespezifischen Format zu <20>ffnen, mu<6D> 
+      bitmap->fd_nplanes eine Null oder die Ebenenanzahl des Schirms 
+      enthalten (work_out[4] bei vq_extnd()). Ist bitmap->fd_nplanes 1, 
+      wird eine monochrome Bitmap angelegt.
+
+      Die Eintr<74>ge des MFDB (fd_addr, fd_w, fd_h, fd_wdwidth, fd_stand, 
+      fd_nplanes) werden vom VDI-Treiber gesetzt und an die aufrufende 
+      Applikation zur<75>ckgegeben. Wenn nicht nicht gen<65>gend Speicher 
+      vorhanden ist, wird der Inhalt des MFDBs nicht ver<65>ndert; ein 
+      Null-Handle wird zur<75>ckgegeben.
+
+      Wenn bitmap->fd_addr ungleich NULL ist, wird dieser Eintrag als 
+      Zeiger auf eine Bitmap interpretiert. Wenn die Bitmap im 
+      Standardformat vorliegt, wird sie ins ger<65>tespezifische Format 
+      umgewandelt. Liegt sie schon im ger<65>tespezifischen Format vor, so 
+      wird sie nicht umgewandelt. Falls die Aufl<66>sung der Bitmap (d.h.  
+      die Anzahl der Farben und Planes) nicht unterst<73>tzt wird, gibt 
+      v_opnbm() ein Null-Handle zur<75>ck.
+
+
+      CLOSE BITMAP (VDI 101, 1)
+
+      void  v_clsbm( WORD handle )
+      {
+         contrl[0] = 101;
+         contrl[1] = 0;
+         contrl[3] = 0;
+         contrl[5] = 1;
+         contrl[6] = handle;
+         vdi();
+      }
+
+      Best<73>ckung der VDI-Arrays:
+
+       Feldelement      | Belegung
+      ------------------|-------------------------------------------
+      contrl[0]         | 101    Funktionsnummer f<>r v_clsbm()
+      contrl[1]         | 0      Anzahl der Eintr<74>ge in ptsin
+      contrl[2]         | 0      Anzahl der Eintr<74>ge in ptsout
+      contrl[3]         | 0      Anzahl der Eintr<74>ge in intin
+      contrl[4]         | 0      Anzahl der Eintr<74>ge in intout
+      contrl[5]         | 1      Unterfunktionsnummer f<>r v_clsbm()
+      contrl[6]         | handle
+
+      Die Funktion v_clsbm() schlie<69>t die mit handle bezeichnete Bitmap. 
+      Wenn der Speicher beim v_opnbm() vom VDI alloziert wurde, gibt sie 
+      diesen Speicher wieder frei.
+
+
+   Rasteroperationen bei Off-Screen-Bitmaps:
+   <20><><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD>
+   Rasteroperationen zwischen Bildschirm und Off-Screen-Bitmap sollten 
+   grunds<64>tzlich im ger<65>tespezifischen Format erfolgen.
+   Wenn als Ziel einer Rasteroperation eine Off-Screen-Bitmap mit ihrem 
+   MFDB angegeben wird und wenn das zu dieser Bitmap geh<65>rende Handle 
+   benutzt wird, so wird beim Blitten anhand der <20>ber vs_clip() auf dieser 
+   Workstation eingestellten Koordinaten geclippt. F<>r das Kopieren eines 
+   Rasters vom Bildschirm in eine Off-Screen-Bitmap sollte man also das 
+   VDI-Handle dieser Bitmap benutzen.
+   Ist die Bitmap dagegen Quelle und der Bildschirm Ziel, so sollte man das 
+   Handle der Bildschirm-Workstaion benutzen, da dann das Raster anhand der 
+   Bildschirm-Koordinaten abgeclippt wird.
+   Wenn man das von v_opnbm() zur<75>ckgelieferte Handle einer Bitmap benutzt 
+   und in fd_addr in einem MFDB 0 enth<74>lt, so werden die Daten der Bitmap 
+   statt dessen benutzt.
+
+   ESCAPES
+   -------
+   Die VDI-Escape-Funktionen (VT52) k<>nnen nicht auf einer Bitmap benutzt 
+   werden. Ihr Aufruf wid ignoriert.
+   
+   vs_color()/vq_color()
+   ---------------------
+   Wenn die Funktion vs_color() mit dem Handle einer Off-Screen-Bitmap 
+   aufgerufen wird, werden die Farben nur dann gesetzt, wenn es sich um 
+   High- oder True-Color handelt. Vq_color() ist ebenfalls nur in High- 
+   oder True-Color sinnvoll - andernfalls ist der Parameter valid -1.
+
+   vst_point()
+   -----------
+   Die Funktion vst_point() und alle anderen Funktionen, die Texth<74>hen in 
+   Punkten einstellen, reagieren bisher nur dann sinnvoll, wenn die Bitmap 
+   die Ausma<6D>e des Bildschirms hat. 
+
+   v_show_c()/v_hide_c()
+   ---------------------
+   Beide Funktionen werden ignoriert, falls sie mit dem Handle einer 
+   Off-Screen-Bitmap aufgerufen werden. Sie beziehen sich nur auf den 
+   Bildschirm und sollten nur vom AES aufgerufen werden.
+   
+2. vq_scrninfo()
+=================
+
+   Genauere Angaben <20>ber das Bildschirmformat liefert die Funktion INQUIRE 
+   SCREEN INFORMATION implementiert. Im workout-Array wird angeben, wie das 
+   ger<65>tespezifische Format aufgebaut ist. 
+   Diese Informationen sind in erster Linie interessant f<>r Programme, die
+   -  schnell Raster aufbauen (auch in TrueColor) und diese mit vro_cpyfm() 
+      auf den Schirm kopieren m<>chten.
+   -  Raster speichern (z.B. XIMGs).
+   -  Raster anzeigen.
+   
+      VQ_SCRNINFO( 102, 1 )
+
+      void  vq_scrninfo( WORD handle, WORD *work_out )
+      {
+         pb[3] = work_out;
+
+         intin[0] = 2;
+         contrl[0] = 102;
+         contrl[1] = 0;
+         contrl[3] = 1;
+         contrl[5] = 1;
+         contrl[6] = handle;
+         
+         vdi();
+
+         pb[3] = intout;
+      }
+
+      Best<73>ckung der VDI-Arrays:
+
+       Feldelement      | Belegung
+      ------------------|-------------------------------------------
+      contrl[0]         | 102    Funktionsnummer von vq_scrninfo()
+      contrl[1]         | 0      Anzahl der Eintr<74>ge in ptsin
+      contrl[2]         | 0      Anzahl der Eintr<74>ge in ptsout
+      contrl[3]         | 1      Anzahl der Eintr<74>ge in intin
+      contrl[4]         | 272    Anzahl der Eintr<74>ge in intout
+      contrl[5]         | 1      Unterfunktionsnummer von vq_scrninfo()
+      contrl[6]         | handle
+                        |
+      intin[0]          | 2      erweiterte Informationen ausgeben
+                        |
+      intout[0..272]    | work_out[0..272]
+      
+
+      intout[0]:  Formatangabe:
+                  0: Interleaved Planes, wortweise (ATARI Grafik)
+                  1: Standardformat (komplette Planes)
+                  2: Packed Pixels
+                 -1: unbekanntes Format; nicht direkt beschreibbar
+      intout[1]:  Verf<72>gbarkeit einer CLUT:
+                  0: keine CLUT (z.B. TTM 194)
+                  1: Hardware-CLUT
+                  2: Software-CLUT (HiColor oder TrueColor)
+      intout[2]:  Anzahl der Ebenen (Bits) pro Pixel
+      intout[3/4]:Farbanzahl oder 0L (mehr als 2*10^31 Farben)
+      intout[8]:  Anzahl der Bits f<>r die Rot-Intensit<69>t
+      intout[9]:  Anzahl der Bits f<>r die Gr<47>n-Intensit<69>t
+      intout[10]: Anzahl der Bits f<>r die Blau-Intensit<69>t
+      intout[11]: Anzahl der Bits f<>r den Alpha-Channel oder <20>hnliches
+      intout[12]: Anzahl der Bits f<>r Genlock
+      intout[13]: Anzahl der nicht benutzen Bits
+
+      Falls eine Hardware-CLUT (intout[1] == 1) vorhanden ist:
+      intout[16-271]: Pixelwert des zugeh<65>rigen VDI-Farbindexes
+
+      Falls HiColor, TrueColor oder <20>hnliches vorhanden ist:
+      intout[16..31]: Zuordnung von Bitnummer im Pixel zum Bit der Rotintensit<69>t
+      intout[32..47]: Zuordnung von Bitnummer im Pixel zum Bit der Gr<47>nintens.
+      intout[48..63]: Zuordnung von Bitnummer im Pixel zum Bit der Blauintensit<69>t
+      intout[64..79]: Zuordnung der Bitnummer f<>r Alpha-Channel
+      intout[80..95]: Zuordnung der Bitnummer f<>r Genlock
+      intout[96..127]: unbenutzte Bits
+      intout[128..271]: reserviert (0)
+      
+   Beispiele:
+   ----------
+
+      In 256 Farben auf dem Falcon w<>rden folgende Ausgaben erfolgen:
+
+      intout   | Wert   | Bedeutung
+      ---------|--------|-----------------------------------------------------
+         0     |   0    | Interleaved Planes, wortweise
+         1     |   1    | Hardware-CLUT vorhanden
+         2     |   8    | 8 Bit pro Pixel
+         3/4   | 256    | 256 verschiedene Farben gleichzeitig m<>glich
+         8     |   6    | 6 Bits f<>r die Rot-Intensit<69>t
+         9     |   6    | 6 Bits f<>r die Gr<47>n-Intensit<69>t
+        10     |   6    | 6 Bits f<>r die Blau-Intensit<69>t
+        11     |   0    | kein Bit f<>r Alpha-Channel
+        12     |   0    | kein Bit f<>r Genlock
+        13     |   0    | kein unbenutzes Bit
+               |        |
+               |        |
+        16     |   0    | Pixelwert f<>r VDI-Farbindex 0
+        17     | 255    | Pixelwert f<>r VDI-Farbindex 1
+        18     |   2    | Pixelwert f<>r VDI-Farbindex 2
+        ...    | ...    |
+       271     |  15    | Pixelwert f<>r VDI-Farbindex 255
+
+      In HiColor auf dem Falcon w<>rden folgende Ausgaben erfolgen:
+
+      intout   | Wert   | Bedeutung
+      ---------|--------|-----------------------------------------------------
+         0     |   2    | Packed Pixels
+         1     |   2    | HiColor bzw. TrueColor
+         2     |  16    | 16 Bit pro Pixel
+         3/4   | 32768  | 32768 verschiedene Farben gleichzeitig m<>glich
+         8     |   5    | 5 Bits f<>r die Rot-Intensit<69>t
+         9     |   5    | 5 Bits f<>r die Gr<47>n-Intensit<69>t
+        10     |   5    | 5 Bits f<>r die Blau-Intensit<69>t
+        11     |   0    | kein Bit f<>r Alpha-Channel
+        12     |   1    | ein Bit f<>r Genlock
+        13     |   0    | kein unbenutzes Bit
+               |        |
+               |        |
+        16     |  11    | Bit 0 der Rot-Intensit<69>t (niederwertigstes Bit)
+               |        | befindet sich in Bit 11 des Pixels
+        17     |  12    | Bit 1 befindet sich in Bit 12 des Pixels
+        18     |  13    | ...
+        19     |  14    | ...
+        20     |  15    | Bit 4 der Rot-Intensit<69>t (h<>chstwertigstes Bit)
+               |        | befindet sich in Bit 15 des Pixels
+        21..31 |  -1    | Bits werden nicht f<>r Rot-Intensit<69>t benutzt
+               |        |
+               |        |
+        32     |   6    | Bit 0 der Gr<47>n-Intensit<69>t (niederwertigstes Bit)
+               |        | befindet sich in Bit 6 des Pixels
+        33     |   7    | Bit 1 befindet sich in Bit 7 des Pixels
+        34     |   8    | ...
+        35     |   9    | ...
+        36     |  10    | Bit 4 der Gr<47>n-Intensit<69>t (h<>chstwertigstes Bit)
+               |        | befindet sich in Bit 10 des Pixels
+        37..37 |  -1    | Bits werden nicht f<>r Gr<47>n-Intensit<69>t benutzt
+               |        |
+               |        |
+        48     |   0    | Bit 0 der Blau-Intensit<69>t (niederwertigstes Bit)
+               |        | befindet sich in Bit 0 des Pixels
+        49     |   1    | Bit 1 befindet sich in Bit 1 des Pixels
+        50     |   2    | ...
+        51     |   3    | ...
+        52     |   4    | Bit 4 der Blau-Intensit<69>t (h<>chstwertigstes Bit)
+               |        | befindet sich in Bit 4 des Pixels
+        53..63 |  -1    | Bits werden nicht f<>r Blau-Intensit<69>t benutzt
+               |        |
+               |        |
+        64..79 |  -1    | kein Alpha-Channel
+               |        |
+               |        |
+        80     |   5    | Bit f<>r Genlock
+        81..95 |  -1    | nicht f<>r Genlock benutzt
+               |        |
+               |        |
+        96..127|  -1    | keine unbenutzten Bits
+               |        |
+               |        |
+
+3. Wie erkennt man, ob die neuen Funktionen vorhanden sind?
+===========================================================
+
+   NVDI installiert (ebenso wie der nur f<>rs ATARI-VDI gedachte Enhancer) 
+   einen Cookie mit der Kennung 'EdDI'. Das auf diese Kennung folgende  
+   Langwort ist die Adresse eines Funktionsdispatchers, der mit der 
+   Funktionsnummer in Register d0 aufgerufen wird. Der Aufruf erfolgt nach 
+   den Pure C-Konventionen (Register d0-d2/a0-a1 und der Stack werden zur 
+   Parameter<65>bergabe benutzt). 
+
+   Bisher existiert nur die Funktion 0, die als Funktionsresultat eine 
+   Versionsnummer zur<75>ckliefert, anhand er man auf die unterst<73>tzten 
+   Funktionen schlie<69>en kann. 
+
+   Ab Version 1.00 ($100 wird zur<75>ckgeliefert) sind die Funktionen 
+   v_opnbm(), v_clsbm() und vq_scrninfo() vorhanden. 
+

tools/zview/readme.1st

@@ -0,0 +1,8 @@
+MagiC users must use "zview.app" being located in the "MagiC" 
+folder !
+
+That's a version compiled with the old GCC 2.95.3 because it seems 
+that MagiC can't launch the C++ application compiled with GCC 3.x :/
+
+
+

tools/zview/zview.inf

@@ -0,0 +1,17 @@
+show_size=1
+show_hidden=0
+show_non_image=0
+browser_x=86
+browser_y=85
+browser_w=736
+browser_h=400
+sortingmode=0
+thumbnail_size=1
+browser_frame_width=200
+preview_frame_height=200
+show_read_progress_bar=1
+show_write_progress_bar=0
+skip_drive=BDU
+smooth_thumbnail=0
+pdf_fit_to_win=0
+pdf_aa=1