	Installation of the IMCNV Image Conversion Package
	--------------------------------------------------

The external version of the IRAF image conversion package, named IMCNV, is 
being distributed separately from the IRAF V2.11 distribution for users
on platforms that have not yet been upgraded to V2.11 or who require a
bug fix.  Precompiled binaries for certain popular systems or those that
may have compiler incompatability problems (e.g.  Silicon Graphics running
IRIX 5.2 or Solaris systems with V3 compilers) are also available, see
section 6 for installation instructions.  The method you use to copy the
file (or remotely access the tar file) is OS dependent and is not discussed
in this document.

If you have any questions, please contact the IRAF HOTLINE (602-323-4160) or
the author at 602-325-9387 (or fitz@noao.edu or 5355::fitz).


[1] The package is distributed as a compressed tar archive; IRAF is distributed
    with a tar reader.  The tar archive may be obtained by magnetic
    tape or anonymous ftp.  For magnetic tape go to step [2] and when
    reading the tar archive simply mount the tape and use the tape
    device name for the archive name in step [4].  To obtain the package
    via ftp (assuming a UNIX computer):

	% ftp 140.252.1.1
	login: anonymous
	password: [your last name]
	ftp> cd iraf.old
	ftp> get imcnv.readme
	ftp> binary
	ftp> get imcnv.tar.Z
	ftp> quit
	% ls -l *imcnv*
	-rw-r--r--  1 iraf         5024 Apr  1 15:40 imcnv.readme
        -rw-r--r--  1 fitz       658637 Nov  1 14:37 imcnv.tar.Z

	% uncompress imcnv.tar

    The readme.imcnv file contains these instructions.  Special arrangements 
    can be made for sites that don't have access to internet but could copy 
    the uncompressed archive over SPAN.

[2] Create a directory to contain the IMCNV external package files.  This
    directory should be outside the IRAF directory tree and must be owned
    by the IRAF account.  In the following examples, this root directory
    is named usr1:[imcnv] (VMS) or  /local/imcnv/ (UNIX).  Make the appropriate 
    file name substitutions for your site.

[3] Log in as IRAF and edit the extern.pkg file in the hlib directory to
    define the package to the CL.  From the IRAF account, outside the CL,
    you can move to this directory with the commands:

	$ set def irafhlib			# VMS example
	% cd $hlib				# UNIX example

    Define the environment variable imcnv to be the pathname to the imcnv 
    root directory.  The '$' character must be escaped in the VMS pathname;
    UNIX pathnames must be terminated with a '/'.  Edit extern.pkg to include:

	reset imcnv      = usr\$1:[imcnv]   	# VMS example
	reset imcnv      = /local/imcnv/	# UNIX example

	task  imcnv.pkg = imcnv$imcnv.cl

    Near the end of the hlib$extern.pkg file, update the definition of helpdb
    so it includes the imcnv help database, copying the syntax already used
    in the string.  Add this line before the line containing a closing quote:
        
                ,imcnv$lib/helpdb.mip\

[4] Log into the CL from the IRAF account and unpack the archive file.  Change
    directories to the IMCNV root directory created above and use 'rtar':

	cl> cd imcnv
	cl> softools
	so> rtar -xrf <archive>  where <archive> is the host name of the
				 archive file or the IRAF tape
				 device for tape distributions.

   On VMS systems, an error message will appear ("Copy 'bin.generic' to
   './bin fails") which can be ignored.  Also on VMS systems, the four
   bin.'mach' directories created by rtar under [newimred.bin] can be
   deleted.  UNIX sites should leave the symbolic link 'bin' in the IMCNV
   root directory pointing to 'bin.generic' but can delete any of the 
   bin.`mach' directories that won't be used.  The archive file can be
   deleted once the package has been successfully installed.

[5] When the archive has been unpacked, build the IMCNV package executable.  
    The compilation and linking of the IMCNV package is done using the 
    following command:

	cl> mkpkg -p imcnv update >& imcnv.spool &

    NOTE: Since the package is distributed in a 'gerneric' configuration
    you must configure the system for the desired architecture before issuing
    the above command.  SUN/IRAF sites must execute a pair of 'mkpkg' comm-
    ands for each supported architecture type.  The Unix environment variable
    IRAFARCH must be set as well before compiling.  For example:

	# Assuming IRAFARCH is set to sparc
	cl> mkpkg -p imcnv sparc
	cl> mkpkg -p imcnv update >& imcnv.sparc &

    The spool file(s) should be reviewed upon completion to make sure there
    were no errors.  

[6] An alternative to compiling from sources is to simply install the
    binaries that may also be retrieved from the archive in the same dir-
    ectory.  To do this uncompress and untar the downloaded file in the
    appropriate bin directory.  For example, to install the SunOS sparc
    binaries:

	cl> cd imcnv$bin.sparc
	cl> softools
	so> !uncompress /<path>/imcnv-bin.sparc.Z   # uncompress tar file
	so> rtar -xrf /<path>/imcnv-bin.sparc	    # unpack binaries


------------------------
CHANGES IN THIS RELEASE:
------------------------

(5/30/95)
    - Added IMEXPR task to the package for platforms that aren't yet updated
      to V2.10.3.
    - Merged bug fixes to evvexpr routines made during last release.


(2/14/95)
    - Mostly minor bugs fixes not worth mentioning in particular.
    - Enhancements:
	- support for ImageMagick MIFF format in EXPORT.  Primarily this 
	  allows images to be written in a format that can be used with 
	  the ANIMATE task in ImageMagick for making movies.
	- support for VICAR as a new EXPORT format.
	- full binary distribution for a number of Unix platforms.

