home *** CD-ROM | disk | FTP | other *** search
- > ReadMe for ModeX 0.15
-
- ModeX provides new screen modes using only one module for any (well...)
- number of modes: you just add the mode data blocks to it. The module called
- ModeXraw is 'code only'; you can tuck your own mode definitions onto the end
- (see below for format). The module ModeX_CPD contains some ready-made modes
- suitable for the Sony CPD-1402E multisync monitor, but may work on others.
- See '*Help modes' for mode numbers.
-
- ModeX no longer contains VIDC-Enhancer specific code; use Owen Smith's
- VIDCClock module for the Atomwide Enhancer or similar software. A540/A500 etc
- obviously don't need such support modules, RISC OS 2.01 or later selects the
- right clock automatically.
-
-
- Using your own modes with ModeXraw
- ----------------------------------
-
- - mode definitions must be in 'new' A540 format, i.e. include the VIDC clock
- rate (in KHz). They work happily in Risc OS 2.00.
-
- - at least one mode must be provided
-
- - each three-part mode definition must start with a 4 byte information word:
- ?0 mode number
- ?1 monitor type to match (0 normal, 1 only for multisyncs)
- ?2 reserved (=0)
- ?3 reserved (=0)
-
- - the last word must be -1 (&FFFFFFFF) to act as an end marker. This word is
- included in ModeXraw; insert your modes between it and the 'DATA' keyword.
- (This means that the last 8 bytes of ModeX are always &FF: the first four
- mark the end of that mode, and the last four is the end-of-modes marker.
-
-
- How to get the mode data
- ------------------------
- Either by hand, using VLSI's docs for the VIDC. This is possible, but hard
- work! Acceptable only if want to slightly alter an existing mode.
-
- Alternatively, using a mode designer. There are several available, but you
- have to look out for two things:
-
- 1) They have to include the VIDC clock rate as described above
- 2) Most designer don't allow to save the pure data; they insist to save a
- complete module. The data can often be found at the end; this is true for
- the Atomwide VIDCPlus mode designer, which is (by now) public domain (and
- worth getting).
-
- Inserting the data is best done in a good editor; Edit is up to job, but
- Zap's word mode is ideal for this (actually Zap is ideal for almost
- everything). If you are in doubt how the finished module should look like
- take a look at the example ModeX_CPD file.
-
-
-
- If you didn't understand all this gibberish, do the following (assuming you
- have a multisync monitor): try the modes supplied in ModeX_CPD and if they
- don't work - well, why not delete all this useless stuff and increase your
- disc space?
-
-
- Please note that you can damage your monitor by using badly defined modes;
- good multisync monitors should protect themselves, though (if it catches
- fire: well, it couldn't have been a good monitor then, could it?)
-
- The software is offered "as is"; the author makes no warranty, express or
- implied, of its fitness for any particular purpose. In no circumstances
- will the author be liable for any damage, loss of profits, time, or data, or
- any indirect or consequential loss arising out of the use of this software
- or inability to use this software, even if the author has been advised of
- the possibility of such loss.
-
- (the last paragraph has been borrowed from Chris Dennis.)
-
- The code that reads the memory speed was lifted from Nick Smith's ArmSI
- application.
-
- FINAL NOTE: ModeX is freeware. This program is Copyright © 1992,1993
- Holger Klingspohr and may be distributed freely provided only a _small_
- (i.e., non-commercial) amount is charged for it and this copyright notice is
- retained. Thank you.
-
-
- Send letters/bug reports/money/presents to:
-
- email: <klingspohr@tu-harburg.dbp.de>
-
- Holger Klingspohr
- Ebelingstr. 1 / 6.3.2.e
- D-W 2100 Hamburg 90
- Germany
-
- Have fun!
-