As they become available this area will contain extra support files for Directory Opus 5.5. These will include links to non-English language catalog files, ARexx scripts, new drop-in Opus modules and any program updates, notes and other hints and examples. As with Opus 5, these will also be released to Aminet.
21/10/96
16/10/96
14/10/96
5/10/96
30/9/96
29/9/96
23/9/96
22/9/96
21/9/96
Got a problem with installation or the use of Opus 5.5? Technical support is available by direct email to GPSoftware
When asking for technical support, please quote your Opus registration number and brief details of your Amiga setup plus a summary of the problem.
Found a solution to a known bug or problem? Got a really nifty setup which you wish to share with other Opus users? Perhaps you have written an indespensible ARexx script for Opus? Then tell us! You could win a free Opus 5 T-shirt if yours is the best utility, solution or suggestion for the month.
This is a mailing list for general discussion relating to general usage and comments for Opus 5. To subscribe to this list, send a message to listserv@lss.com.au containing : -
subscribe dopus5 <Your Real Name>
in the message body. You will be automatically sent a brief welcome message, with instructions on how to post to the list.
There is a mailing list for the discussion of programming issues relating to Opus and the Opus SDK. To subscribe to this list, send mail to listserv@lss.com.au with :
subscribe dopus5-dev <Your Name>
in the message body. You will be automatically sent a brief welcome message, with instructions on how to post to the list.
The is now available. This archive contains information for Amiga developers who wish to write their own custom modules for Opus 5.5. The archive contains AmigaGuide, autodocs and include files for the DOpus5.5 library plus instructions and examples of how to create modules in 'C' for use with Opus 5.5. Also included is the source to the Opus ViewFont program plus source for a new and nifty IconClock module and more.
From Jonathan Potter & GPSoftware, this is a replacement diskinfo.module for Directory Opus 5.5. It replaces the old text-based interface with a new graphical representation of free space. You can also relabel the disk from the requester.
To install, copy your old diskinfo.module in DOpus5:Modules to DOpus5:Storage/modules (in case you wish to re-install it later), then copy this new diskinfo.module to your DOpus5:Modules directory. You may need to reboot after copying the new module. We have also supplied the raw .cd file. If you are using a non-English language locale, you will also need to translate and compile a new catalog for your language and then remove or replace the old diskinfo.catalog.
21/10/96 now includes full AmigaGuide documentation, Installer script, source code.
compare.module by Leo 'Nudel' Davidson for Gods'Gift Utilities. A plug-in module for Directory Opus 5.5 to compare two files w/ progress guage. Can now also display HEX/ASCII dumps of the two files side-by-side with their differences highlighted. Now with installer script plus full AmigaGuide documentation.Written entirely in 'C', source archive available
hotlist.module by Leo 'Nudel' Davidson for Gods'Gift Utilities. A plug-in module for Directory Opus 5.5 to provide user-defined Hotlists of paths and files. Written entirely in 'C' -- *much* faster than the ARexx version.
Thanks to Leo 'Nudel' Davidson - NoOo.o.oOoODLE! email:
leo.davidson@keble.oxford.ac.uk
Amiga DOpus5 /X h WebPage v2.10
7-Apr-96 | http://users.ox.ac.uk/~kebl0364
An Opus ARexx script from Helmut Hummel which allows you to play mods files asynchronously with DeliTracker from DOpus5. All selected modules are loaded into the internal list of the DeliTracker and play the list forward or backwards asychronously from Opus.
These catalog files are provided by the efforts of 3rd party users and supporters of Directory Opus with permission and thanks from GPSoftware. They are provided free of charge 'as is' with strictly limited warranty. If you have a problem with any of these files, you may contact the respective authors directly or email me directly with details of the specific problem.