home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ARM Club 3
/
TheARMClub_PDCD3.iso
/
hensa
/
utilities
/
vmecontrol_2
/
!VMEctrl
/
!Help
< prev
next >
Wrap
Text File
|
1995-11-23
|
6KB
|
116 lines
!VMEctrl 1.01 / VMEcontrol module 1.22
~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~
First off, to use this you'll need
* A VIDC enhancer that uses IO1 (eg. Atomwide, Risc Developments, etc)
as its 'enable' control. (also works with Andreas Barth's DIY
enhancer).
Support for other enhancers will be added if there's any call for it
* An 'old' machine; ie. one that had to have a VIDC enhancer fitted
(the 'newer' machines have it built in)
* the VMEcontrol module (version 1.22 or later). You should find a
copy of it inside the !VMEctrl directory. Feel free to *copy* it to
somewhere else, but it *must* remain in this directory [the app.
uses it as the 'stub' for customised modules]
NB: No checks are made for hardware/OS version... If you don't know what you've
got, "*fx 0" from the command line/in a taskwindow will tell you the OS
version. You can try it with your VIDC enhancer and if it works, good. If not,
let me know and I'll try to sort it out.
When I say VIDC enhancer, I mean a third party add-on, not the clock switcher
built into the newer machines. (Just to clear that bit up)
[ see the file 'ModuleDocs' inside the !VMEctrl directory for information about
the module (commands, swis, etc) ]
!VMEctrl is a WIMP frontend for the VMEcontrol module (inside the !VMEctrl
directory) that controls a VIDC enhancer add-on (see the ModuleDocs file for
more information of the module). Basically the front-end allows you to
(re)configure the module to suit your preferences, and then save either a file
that the VMEcontrol module can read back in ('*loadmap <filename>' or use
RMLOAD VMEcontrol <filename>') or a new VMEcontrol module that has your choices
built in (so you can just RMLoad it. You can still use it with the saved files
tho', so this method is probably the better of the two).
Usage
~~~~~
Double-click the !VMEctrl icon in a filer window to run the application ... oh,
you know how it works, skip the waffle ... Clicking on the iconbar icon with
select will open the main window. Adjust will give you a little bit of info on
how to contact me (to say hello, bug reports... etc) and Menu will give a very
exiting [oops, I mean exciting... I hope] menu. Very.
The main window
~~~~~~~~~~~~~~~
This window has two main sections, 'Configuration' and 'Current'. Suprisingly,
the 'current' section refers to the current screen mode. See, it even says what
mode that happens to be! Beneath the tantalising mode number there are two
'option' icons, 'enabled' & 'configured'. These refer (respectively) to whether
the VME is currently enabled, and whether it is configured to be enabled for
this mode ['enabled' will only ever be different to 'configured' is you've
deliberately en/disabled the VME since the last mode change]. You can click on
these icons to turn the VME on/off, or set the configuration status for the
current mode. [note, unlike the '*mode <n> On|Off' command provided by the
VMEcontrol module for configuration, changing the configuration for the current
mode will have *no* immediate effect (the VME's state will only be affected on
the next mode change)]
The 'configuration' section allows you to set the configure the VMEcontrol
module for any screen mode, not just the current one. Use the arrow up/down
icons to move through the *possible* modes [NB: possible is extremely unlikely
to be the same as *available*, just because there are 127 screen modes
*possible* doesn't mean that they exist]. You can also type a mode number into
the mode number writable icon [press Return after entering the number]. No mode
changes take place.
Below the 'mode selection' icons is a single 'option' icon that allows you to
see/set the VME configuration for the displayed screen mode.
Below the 'enabled' option icon is a 'pop-up menu' icon that will open the
'save' box should you click on it. The save box is also available from the menu.
Saving Files/Modules
~~~~~~~~~~~~~~~~~~~~
The save box can be accessed from the menu (off the Save=> entry), or by
clicking on the 'save config' popup icon in the main window.
The save box contains the normal icons, plus a 'module' option icon. This
allows you to specify whether you want !VMEctrl to save a configuration file
(just the save as *SaveMap does), or generate a module that has your
configuartion built in. Use of the save box shouldn't really need to be
explained, so...
Notes
~~~~~
Once the application has been 'seen' by the filer (or Filer_Boot'ed), double
clicking on a 'VMEmap' (configuration file) will, assuming that the VMEcontrol
module is loaded, load that file (using *loadmap) whether !VMEctrl is running
or not.
The !VMEctrl application is a very simple front-end for the VMEcontrol module.
It doesn't provide any extra features (well, it does... the creation of a new
module is an 'extra feature' I suppose) and simply acts as a GUI to the SWIs
(or *commands) that control the module. There are only two reasons why !VMEctrl
should even exist: (1) To generate 'preconfigured' modules, and (2) because
some of you (you know who you are) don't like command line stuff. Of course,
you could configure the module from the CLI, and then use !VMEctrl to save your
custom module...
The source code for the module is provided in the 'Source' directory inside he
application. Also, the uncrunched !RunImage is there.
Disclaimer
~~~~~~~~~~
Use of this software is completely at your own risk. The author can accept no
responsibility for any damage/loss arising from the use, or inability to use
this software. No warranty, express or implied, applies to this software.
This is not PD: the Copyright in this software belongs at all times to the
author. However, permission is granted for unrestricted distribution
prodividing that *no* charge is made for the distribution [a charge may be made
for handling/media] and that the whole of the software is supplied intact and
unaltered. Permission is also granted for unrestricted use and alteration of
the software [but if you fix a bug / add anything nice, let me know so I can
patch the 'master' version].
Bug reports / comments / etc to:
Angelos tou Thanatou c/o 23 Baronsway, Whitkirk, Leeds, LS15 7AW, England.
(until Sept-ish '96: n0ae3@newton.ncl.ac.uk)