If you have upgraded from Imagecopy 3.5 or 4.0 you can preserve your existing preferences by saving them into an INF file (select Global-Save INF File) and loading this into the new version (with Load INF File). Select Global-Save Defaults to make these the default preferences.
If you have not upgraded from a previous version you can take the following steps to configure Imagecopy for your system:
[NB IMPORTANT Do not save preferences onto your master disk, since this will prevent future upgrade patches from working correctly.]
Imagecopy 4.1 takes advantage of system enhancements provided by third-party desktops and multitasking OSes.
Imagecopy supports the VA_START protocol, so that if you are running it from a desktop which supports this protocol (Ease, Gemini, MagXDesk, Neodesk 4, Thing etc.) you can load files into an active version of Imagecopy by double-clicking on them or dragging them onto an Imagecopy icon. If you have a single-tasking version of TOS this will only work if you are running Imagecopy as an accessory (otherwise you don't have access to the desktop when Imagecopy is running).
[NB Under Neodesk 4.003 and greater there is an option in Miscellaneous Settings which prevents multiple instances of a program being loaded when you double-click on a file or drag it onto a program icon. Neodesk should also be selected as the AV server (using the same option)]
Imagecopy supports the 'Drag and Drop' protocol in MultiTOS-compatible systems (MultiTOS, MagiC 4 and greater). This allows images to be loaded by dragging them onto an Imagecopy window. Dragging images onto a catalogue or page window causes them to be added to the catalogue or page. Dragging them onto another window causes the images to be viewed, unless the [Shift] key is held down, in which case you have a choice of viewing, printing, or converting the images. Dragging a folder onto an Imagecopy window (or program icon) causes all the images in that folder to be processed.
[NB Some systems that do not support drag and drop (e.g. Neodesk/Geneva) use the VA_START protocol to allow files to be dragged onto program windows. On these systems, dragging image files onto a catalogue or page window causes the images to be opened in a separate window instead of being added to the catalogue or page (the VA_START protocol does not indicate which window the file was dragged onto).]