FB.rexx is a AREXX program made to work in conjunction with
VistaPro2.0's F3 function key macro DoFB.F3, ASDG's Art
Department Professional, and the Mimetics FrameBuffer.  FB.rexx
will boot ADPro (if it is not already running in the background),
load the 24 bit plane picture into ADPro and instruct ADPro to
"save" the picture to the FrameBuffer for display or recording
with any NTSC video device.  After the image is displayed, ADPro
will shut down to free up the FAST RAM for use with VistaPro2.0
or for other multitasking jobs. 

Using ADPro to display the 24 bit image is simpler and more
versatile than Mimetics own FrameBuffer software.  If you wish
to send images to ADPro for further manipulation, you may delete
the line 'ADPRO_EXIT'in FB.rexx which shuts ADPro down. ADPro
will continue to run with VistaPro2.0 in the background.  An
Amiga 2000 with nine megabytes of RAM is advisable to support
both VistaPro2.0 and ADPro.

The procedure is simple. After rendering your image with Vista-
Pro2.0, press the F3 function key. You will be presented with
a requester asking you where to save the 24 bit IFF file. After
the picture is saved, the image will be displayed and you will
then be returned to VistaPro2.0 for further work.

There are a few conditions and items necessary to make FB.rexx
work properly.  You MUST OWN AREXX, VistaPro2.0, ADPro, and a
Mimetics FrameBuffer. Place WAITPORT in your C: directory.
WAITPORT works similar to AREXX's WAITFORPORT.  It is necessary
because WAITFORPORT has a major bug in it.   Place DoFB.F3 in
either your S: directory or in the same directory as 
VistaPro2.0.  FB.rexx should go in your REXX: directory so
AREXX knows where to find it.  Either include an ASSIGN ADPro:
WhereYouKeepADPro: in your startup sequence or assign ADPro
before running VistaPro2.0.

Since the F3 function key runs an Amiga DOS script and that the
EXECUTE command is necessary for Amiga DOS scripts to function,
you must either start VistaPro2.0 from a Shell or CLI (making
sure your stack is set to 50000 or higher), or you may run
VistaPro2.0 from an icon using IconX.  I have included a script
file called VistaPro2.0I and a Project Icon. To enable you to run
VistaPro2.0 from an Icon using IconX.  Place both of these in the
same directory as VistaPro2.0.  By having both the standard
VistaPro2.0 Tool Icon and the VistaPro2.0I.info Icon with the
VistaPro2.0I script file side by side in the same directory, you
may easily choose how you want VistaPro2.0 to load simply by
clicking the appropriate Icon.  If you do not wish to add an
ASSIGN ADPro: line to your startup-sequence, you may add an
assign command to the VistaPro2.0I script file.  This will
automatically assign ADPro when you load VistaPro2.0.  The line
ASSIGN ADPro: WhereYouKeepADPro: added before the line
"VistaPro2.0" will work nicely.

FB.rexx may be easily changed to be used with other frame
buffers.  The type of SAVER in ADPro determines where the image
will be sent.  An excellent application would be to automatically
save 24 bit images in the JPEG compressed file format. This would
cram the images into a small space.  ADPro Operators and devices
could be added to FB.rexx for additional dithering or sizing of
the image.  You may even link VistaPro2.0, ADPRo, and other
programs using FB.rexx. AREXX opens many possibilities.

I asked Bill Sorensen to write FB.rexx because I wanted to use my
FrameBuffer as a quick 24 bit image preview device to check parts
of scripted animations before rendering.  This will save time by
giving me a better idea of what my final work will look like and
help me catch costly mistakes.  I hope it works well for you. Joe
Laleman, February 1992. 235 Island Avenue, East Moline, IL 61244
(309) 755-6178. Contact me if you need any help.