@DATABASE "InfraRexx.guide" @AUTHOR "Leon Woestenberg" @(c) "Copyright İ 1994 by Leon Woestenberg" @$VER: InfraRexx.guide 1.3 (10.8.94) by Leon Woestenberg @NODE main "InfraRexx" @{b}InfraRexx 1.3 İ 1994 by Leon Woestenberg and Jeroen Steenblik Infrared Remote Control ARexx Interface@{ub} General Information @{" Legal notes " LINK copyrights} @{" History " LINK history} @{" Introduction " LINK introduction} @{" Known Bugs " LINK bugs} @{" Features " LINK features} The User Help Guides @{" The software " LINK software} @{" The hardware " LINK hardware} More About InfraRexx @{" About InfraRexx... " LINK about} Much more that you would like to know. @{" Reaching the authors... " LINK authors} For smashing bugreports and the like. @ENDNODE @NODE copyrights "InfraRexx Copyrights and Disclaimers" @PREV main @NEXT introduction @{b}InfraRexx Copyrights@{ub} InfraRexx - The @{" software " LINK software} archive Copyrights İ 1994 by Leon Woestenberg and Jeroen Steenblik. InfraRexx is freely distributable providing that the archive is kept intact. A nominal fee may be asked to cover distribution costs. This is known as freeware. InfraJoy - The @{" hardware " LINK hardware} design Copyrights İ 1994 by Jeroen Steenblik and Leon Woestenberg. The hardware design is freely distributable and may be used to build a copy of the InfraJoy interface hardware. A copy of the hardware itself may not be sold with a profit. Both InfraRexx and InfraJoy may not be sold, nor included with any commercial product without written permission of the @{" author(s) " LINK authors}. @{b}InfraRexx Disclaimers@{ub} The authors do not take responsibility for the InfraRexx @{" software " LINK software} or @{" hardware " LINK hardware} damaging your Amiga computer, infrared controlled devices or data stored on these machines. The authors can not guarantee that InfraRexx and/or InfraJoy work(s) correctly on your configuration. InfraRexx has been tested for a long period and works correctly in every aspect the authors could test. @ENDNODE @NODE introduction "InfraRexx Introduction" @PREV copyrights @NEXT features @{b}InfraRexx Introduction@{ub} InfraRexx is a @{" hardware " LINK hardware} and @{" software " LINK software} project that allows your Amiga to control external devices and vice versa, via infrared signals. ARexx commands sent to the @{" InfraRexx Daemon " LINK daemon} commodity, cause corresponding infrared commands to be sent to external devices. Vice versa, infrared signals recognized by the Daemon can control software via ARexx. The seperate @{" InfraRexx Editor " LINK editor} program is used to learn new infrared command codes, and to attach meaningful ARexx commands to them. A possible use of InfraRexx is the control of audio/video devices, such as television sets, video tape recorders or compact disc players, via multimedia software running on an Amiga. Another possibility is to control a module player running on your Amiga so that you can adjust volume and select music modules via a common infrared remote control unit as found with modern audio/video consumer electronics. @ENDNODE @NODE features "InfraRexx Features" @PREV introduction @NEXT history @{b}InfraRexx Features@{ub} · Uses (and therefore needs) Kickstart release 2.04 (or higher). · Easy and allround control of devices via @{" ARexx " LINK ARexx}. · Control your Amiga programs via a remote control unit and ARexx. · Small @{" commodity daemon " LINK daemon} to save memory. · Low system overhead during infrared monitoring (can even be disabled). · Lowcost @{" hardware " LINK hardware} with optional joystick throughput. · Font-sensitive and style-compliant graphic user interface. · Localization under Workbench release 2.1 (and higher) systems. · Newlook menus under AmigaOS release 3.0 (and higher) systems. · Uses the Amiga Installer Utility for maximum convenience. @ENDNODE @NODE history "InfraRexx History" @PREV features @NEXT bugs @{b}InfraRexx History@{ub} Release 1.0 (11-May-94) · Initial release onto Aminet. Release 1.1 (4-Jun-94) · Interim release for registered InfraJoy v2 hardware users. · InfraRexx Editor v1.1 (4-Jun-94) - Adapted transmitter code to control v2 hardware as well. - Now learns code bitstreams with long headers (up to 24 bit). - Removed incompliant copyright notice from the versionstring. · InfraRexx Daemon v1.1 (4-Jun-94) - Adapted transmitter code to control v2 hardware as well. - Removed incompliant copyright notice from the versionstring. Release 1.2 (15-Jul-94) · Released on Aminet and soon on a Fidonet support BBS. · New language catalogs v2 are no longer in subdirectory. · Includes nice building plans for the new InfraJoy v3 hardware. · InfraRexx Editor v1.2 (28-Jun-94) - Waitpointer (using 3.x functions if present) during busy time. - Removed harmless bug that could prevent a window from opening. - Removed a crashful bug, dangerous when sending with high repeat. - Changed interrupt names to clear up who is using the CIA timer. - Now needs v2 of the language catalog, no longer in subdirectory. - Specific transmit/receive code for each of the v1/v2/v3 hardware. · InfraRexx Daemon v1.2 (27-Jun-94) - Changed interrupt names to clear up who is using the CIA timer. - Now needs v2 of the language catalog, no longer in subdirectory. - Specific transmit/receiver code for each of the v1/v2/v3 hardware. Release 1.3 (19-Aug-94) · Released on Aminet, and Fidonet support BBS. Submitted to Fred Fish. · InfraRexx Editor v1.3 (10-Aug-94) - Removed bug that made learning only work once on certain machines. - Previously, fast multiple clicks on the edit button could cause the program to open multiple edit windows. - Checkboxes are scaled to the font height under AmigaOS 3.x. · InfraRexx Daemon v1.3 (17-Aug-94) - Removed bug that made sending only work once on certain machines. - Removed a test line of v1.2, that caused to send a code at startup. - If the locale library was present, an unterminated taglist was used. - String compare didn't check for equal lengths first. @ENDNODE @NODE bugs "InfraRexx Known Bugs" @PREV history @NEXT software @{b}Known Bugs@{ub} There are some harmless byte-read Enforcer hits from address $0, mostly accesses to empty strings. @ENDNODE @NODE software "InfraRexx Software" @PREV main @NEXT editor @{b}InfraRexx Software@{ub} The InfraRexx software mainly consists of two programs: · The @{" InfraRexx Editor " LINK editor} provides a graphic user interface to edit a codeset. New infrared codes can be learned, and ARexx commands can be attached to each of the codes. · The @{" InfraRexx Daemon " LINK daemon} is a small commodity that runs in the background. It waits for incoming @{" ARexx commands " LINK arexx} that are sent to its ARexx host port, and sends the infrared code attached to each of these commands. Optionally, it is possible to enable an infrared monitor, that waits for infrared signals and sends the attached ARexx command to the ARexx Master. Some codesets and example ARexx scripts are included to show the power of InfraRexx in conjuction with other programs. @ENDNODE @NODE editor "InfraRexx Editor" @PREV software @NEXT mainwindow @{b}The InfraRexx Editor@{ub} The editor is a program where you can build up an infrared codeset. In the main window, a description of the codeset and default values can be given. The infrared codes can be edited by the code editor subwindow, where code-specific entries can be selected. @{" The main window " LINK mainwindow} @{" The code edit window " LINK editwindow} Two options can be passed to the editor, using either command line arguments (from the Shell) or icon tooltypes (from the Workbench). The supported entries for both are: · FROM Defines a codeset file to load. · PUBSCREEN/K Sets the preferred public screen where the editor should open on. The editor normally opens on the default public screen. · HARDWARE/N Selects the InfraJoy hardware version that is used. @ENDNODE @NODE mainwindow "InfraRexx Editor Mainwindow" @PREV editor @NEXT editwindow @{b}InfraRexx Editor Mainwindow@{ub} In this window you can edit an infrared command codeset. A codeset is the collection of functions found on a common remote control unit. It is built up of some global settings (found in the mainwindow) and command-specific data (found in the @{" editwindow " LINK editwindow}). To set the global parameters, use the following gadgets... · Codeset description Here you can define the name and additional information of the current codeset. · Receive bitrate Use this slider to set the bitrate of the codeset. This value is very important because it indicates how fast the infrared signals should be sampled. Before learning any commands, be sure to set this value to the bitrate that is used by the remote control unit. · Learn bitrate ** This function is not yet implemented in 1.3. ** ** For 1.3, we tried to include as many as possible codesets ** ** with bitrates included, so please use these to learn new ** ** codes. ** · Monitor frequency This value indicates how many times per second the @{" daemon commodity " LINK dameon} should check for incoming infrared signals. The higher the value the more processor time the commodity will take, but the quicker the response is. If you want a quick reponse to a short button-press, set this value to about 100 times per second. · Infrared codes This is the listview where all the learned codes are shown. Select a code here to make it the currently edited code. Use these buttons to edit the list... - New Adds an empty code to the list, ready to be learned or edited. - Edit... Opens the @{" edit window " LINK editwindow} with the selected code. - Delete Deletes the selected code. - Sort Sorts the list alphabetically. - Top, Bottom, Up, Down Edit the position of the selected code in the list. The pulldown menus are used to store the current project, the codeset, to disk, or to quit the editor. · Project - Load... Opens a filerequester in order to load a codeset from disk. If there are still unsaved changes, you will be asked to proceed first. - Save Saves the current codeset project to disk using the current name. - Save as... Opens a filerequester in order to save the current codeset to disk. - About... Displays information about InfraRexx. - Quit... Quits the editor program. If there are still unsaved changes, you will be asked to proceed, save before quiting or cancel. @ENDNODE @NODE editwindow "InfraRexx Editor Editwindow" @PREV mainwindow @NEXT daemon @{b}InfraRexx Editor Editwindow@{ub} The editwindow is the place to be when editing the infrared commands you want to use via @{" ARexx " LINK arexx}. Here you interface the current infrared signal code and ARexx commands. Use these gadgets to do so: · Infrared Code Interfacing In this frame, the user side of the interface can be edited. - Infrared Code Name Enter a meaningful name of the current code here. For example, 'CD Player Shuffle' or 'Amplifier Select Tuner' (without quotes). - ARexx Transmit Command Enter a unique keyword here for transmitting the current code. For example (see above), 'CD_SHUFFLE' or 'AMP_SELECT_TUNER'. When sending this keyword via @{" ARexx " LINK arexx} to the @{" daemon " LINK daemon}, the infrared code will be sent, and for example, your CD Player will go into shuffle mode, or your amplifier selects the tuner as input. - ARexx Receive Command Enter an @{" ARexx " LINK arexx} command here that will be executed when receiving this code. In this way, you can control your Amiga programs via your infrared remote control unit. Use SINGLE QUOTES around multiple keyword arguments. For example, use your (CD Player) remote control unit to control the moduleplayer DeliTracker 2.x. Select the 'CD Next Track' code and add this ARexx Receive Command: 'ADDRESS DELITRACKER NEXTSONG'. When you press the 'next track' button on the remote, the next module of the list will be played. You can also type the name of an ARexx script here, without quotes. The script has to be in the REXX: directory and must have a suffix '.irx' in order to be executed. · Transmit bitrate Defines the bitrate for the current code only. In this way it is possible for a code to have a different bitrate then the codeset. Note that codes with a different bitrate can only be sent, and cannot be received by the @{" daemon " LINK daemon}. - Use Codeset bitrate Makes this code use the same bitrate as the codeset. - Bitrate slider If the previous gadget is not checked, you can define a different bitrate here for the current code. · Infrared Code Data The place where the infrared signal can be edited. - Data Locked Checking this gadget will keep you from accidently modifying the signal and becoming invalid. - Infrared Bitstream The actual infrared signal bitstream using 1's and 0's. You should not edit this gadget unless you know what you are doing. - Delay Between Codes This indicates the number of 0 bits that should be sent inbetween two succesive code bitstreams. Normally, this delay is around the same size as the bitstream itself. - Code Repetition The number of times the code should be repeated. Normally, 3 to 5 times should be sufficient to guarantee a clear response from the controlled device. · Code Learner This is the place where codes are learned directly from the remote control unit. This needs the receiver hardware being present. - Learn Start learning a new code. The following messages instruct you what to do... · Waiting for IR signal... Direct your remoyte control unit towards the receiver, at about 1 meter (3 feet) distance. Now send the code by pressing the function button you want to learn on your remote control unit. · Learning IR signal... An infrared signal has been received and is now being prosessed. · Bad signal, not learned. This signal was received bad, and was not learned. Please try again. If this occurs often, check the batteries in the remote control unit, or try different distances/angles. · Timeout, nothing learned. Five seconds expired before any infrared light was received. · If no mesage appears after learning, the code learned is shown into the bitstream gadget. If the code is nonsense (lot of 1's, or 0's) you have to learn the code again. If the code looks OK, try it out by sending it, and check if the appropriate device responds to the infrared signal. If not, learn again. - Send Transmit the current code with the current settings. This can be used to immediately check if a newly learned code is correct. Note that if InfraRexx Daemon is running, its monitoring function must be disabled. Otherwise, the editor will report that it cannot use the CIA timer for sending, as the Daemon program is using it. @ENDNODE @NODE daemon "InfraRexx Daemon" @PREV editwindow @NEXT arexx @{b}The InfraRexx Daemon@{ub} This commodity serves as the actual @{" ARexx-to-infrared interface " LINK arexx}. This daemon uses as few memory and processor time as possible. Therefore, no graphic user interface is available except for a requester window where you can control the infrared monitor or quit the daemon. InfraRed Monitoring The infrared monitor is an interrupt that checks for incoming infrared signals on a regular basis. The monitor can be disabled, if you don't need to watch for incoming infrared signals. In this way, the daemon doesn't use processor time (until it receives activation signals). Re-running the daemon while already running will quit the daemon. The daemon is configured using either command line arguments (from the Shell) or icon tooltypes (from the Workbench). The supported entries for both are: · CX_PRIORITY/N/K Sets the commodity priority. Default this is zero. · CX_POPKEY/K Defines the hotkey to popup the monitor requester. The default is 'control alt i'. · FROM/A The acquired codeset file where all the infrared data is stored. This file can be edited and saved using the @{" InfraRexx Editor " LINK editor}. · MONITOR/K Sets the initial state of the monitor. Either 'YES' for enabled or 'NO' for disabled. Default is YES. · PUBSCREEN/K Sets the preferred public screen where the monitor requester should popup. Normally, it pops up on the default public screen. · HARDWARE/N Selects the InfraJoy hardware version that is used. @ENDNODE @NODE arexx "InfraRexx ARexx Interface" @PREV daemon @NEXT hardware @{b}InfraRexx ARexx Interface@{ub} The @{" InfraRexx Daemon " LINK daemon} communicates with other programs via ARexx. The name of the ARexx hostport is 'INFRAREXX'. Programs supporting ARexx or ARexx scripts may send commands to this port to control external devices via infrared codes. There are three types of ARexx commands it supports: @{b}· Transmit commands@{ub} that can be edited via the @{" InfraRexx Editor " LINK editor}. Sending these commands to the daemon, will make the daemon transmit the corresponding infrared signal from the used codeset. @{b}· Receive commands@{ub} are send by the daemon if it recognizes an incoming infrared signal that is sent by an infrared remote control unit. These receive commands will be send to the ARexx Master, but can also be directed to other programs using the ARexx 'ADDRESS' command. You can also execute an ARexx script in this way . Just save a script in the REXX: directory with a '.irx' suffix, and this script will be executed when the receive command of a code equals this script name. Receive commands are edited from the @{" Codeset Editwindow " LINK editwindow} of the @{" InfraRexx Editor " LINK editor} program. @{b}· Control commands@{ub} which control the configuration of the daemon. The templates of the daemon control commands are: @{b}- QUIT@{ub} Quits the daemon. @{b}- SET MONITOR/K@{ub} Sets the configuration of the daemon: · MONITOR/K Enables or disables the monitor. Either 'YES' or 'NO'. @{b}- SEND BITRATE/N/K STREAM/A/K DELAY/N/K REPEAT/N/K@{ub} Send a raw infrared signal as specified by these parameters: · BITRATE/N/K The rate at which this signal must be send. If not specified, the default codeset rate will be used. · STREAM/A/K This is the actual signal, a bitstream built up of ones and zeros. · DELAY/N/K The delay (in number of bits) between the bitstreams. In this period, no infrared signal is sent. · REPEAT/N/K The number of times that the bitstream is sent. With this parameter you can control the time that normally a button would be pressed on your remote control unit. This can be used to control audio volume or tape cueing functions. For normal functions, however, a value of around 3 should be good enough to ensure clear transmission. @ENDNODE @NODE hardware "InfraRexx Hardware" @PREV software @NEXT about @{b}InfraRexx Hardware@{ub} The InfraRexx hardware, named InfraJoy, is a small circuitry that is plugged into the @{b}second@{ub} joystick port. You may use the hardware plans of this archive to build your own hardware. Note the @{" copyrights " LINK copyrights} when doing so. The hardware can also be @{" ordered " LINK order} by the @{" author(s) " LINK authors}. The hardware is based on a small print circuit board, with a size of about 5 x 2.5 cm (2 x 1 inch), that can optionally hold a transmitter and/or receiver. · The transmitter sends infrared signals as directed by the InfraRexx software. This can either be the @{" Daemon " LINK daemon } (when processing ARexx @{" transmit commands " LINK arexx 8}) or the @{" Editor " LINK editor} (using the @{" send " LINK editwindow 200} function). Note that if you have a transmitter-only version of the InfraJoy hardware, you are able to control devices via your Amiga. However, to control your Amiga using a common infrared remote control unit, you need a receiver as well (see below). This is also true if you want to learn new codes. · The receiver is based on a hybrid infrared detector, that will detect infrared codes sent by remote control units, and send these to the InfraRexx software. This can either be the @{" Daemon " LINK daemon} (when @{" monitoring " LINK daemon 8}) or the @{" Editor " LINK editor} (when @{" learning " LINK editwindow 74}). Note that if you have a receiver-only version of the InfraJoy hardware, you are able to control your Amiga via an infrared remote control unit. To be able to control devices via your Amiga, you need the transmitter as well (see above). Although the transmitter-only and receiver-only versions can be used without problems, the most powerful solution is a combination of both. @ENDNODE @NODE about "About InfraRexx..." @PREV hardware @NEXT begin @{b}About InfraRexx...@{ub} @{" The beginning of InfraRexx... " LINK begin} How it all started. @{" Credits " LINK credits} Are you in here too? Just have a look who is. @{" Development " LINK develop} What can you do to make it happen in the future? @{" Future " LINK future} A look ahead of what is still to come in this world. @{" Ordering the hardware " LINK order} How to order the InfraJoy hardware interface. @{" Paying the dimes " LINK payment} How to get your money at the right spot. @{" Registering " LINK register} How to become a registered user of InfraRexx, and why. @{" The Registration/Order Form " LINK form} Fill this in, print it, and post it now :) @{" Obtaining updates " LINK updates} How to get the hottest, most cool release version. @ENDNODE @NODE begin "The beginning of InfraRexx..." @PREV about @NEXT credits @{b}The beginning of InfraRexx...@{ub} InfraRexx is a result of an idea I had in mind for months. I wanted to control my audio set via the Amiga, so that I could implement music and sound effects to video presentations. However, during the time many more ideas came above, like: · a GUI to control audio devices (inspired by CDDA player JukeBox). · voice-recognized control for lamps, audio/video (using VCLI). · automatic CD recordings, using editing, peak search, fading etc. · a discjockey program (inspired by those giant radio channels). · a small infrared communications project to make Amiga's interact. · a way to control my Amiga programs via a remote control unit. · selecting a radio/tv news channel on specific times (using Recall). As I had no idea where to start, I decided to design a basic interface which implements to basic functions needed to make the link between infrared light signals and Amiga applications. This is where the InfraRexx project started. In fact it does none of the things mentioned above, but serves as an @{" ARexx " LINK arexx} host that offers a large amount of possibilities. The name 'InfraRexx' was made up from two wonderful things: 'Infrared' and 'ARexx'. 'InfraJoy' added some 'joy(stickport)' to it :) @ENDNODE @NODE credits "InfraRexx Credits" @PREV begin @NEXT develop @{b}InfraRexx Credits@{ub} Thanks go to the following persons (in some chaotic, random order): · Wouter van Oortmerssen for the E programming language and compiler. · Dietmar Eilert for the programmer's editor GoldED. · Stephan Wijman 'Beam me up Scotty' for using his Fidonet BBS, Deep Space Nine, for support. · All Amiga E Mailing List members. I learned of every line of E. · Those who included 2.04+ example sources with their software, especially Stefan Becker for ToolManager and Olaf `Olsen' Barthel for Term. · Lars Jonsson and Guenther Rehm for a quick 'bug removed?'-betatest. · All registered users and users that gave feedback, bug reports, ideas. · The Amiga hardware and software (ex-)engineers for this superb computer and operating system. · All Amiga dudes and dudettes. Keep the Amiga flame burning hot. @ENDNODE @NODE develop "InfraRexx Development..." @PREV credits @NEXT future @{b}InfraRexx Development...@{ub} The InfraRexx project depends heavily on the availability of infrared code information as used by the electronics manufacturers. Most of the manufacturers don't document the codes for public. Happily, Philips does, so the project could be tested with the specs in our hands. In future releases, I would like to offer more ready-to-use codesets. Therefore, I need the specs of the infrared codes used. Although codes can be learned by just experimenting, many things remain unclear. The most important spec is the so-called bitrate of the code. Also, I would like to see the @{" InfraRexx software " LINK software} being localized for different countries. As I don't speak all the worlds languages, I would like it if people want to localize the catalogs, and send them to me. Please read the @{" localization notes " LINK locale} if you are interested. Also, I would like to hear some feedback from InfraRexx users. Maybe you've got an exotic use or cool @{" ARexx " LINK arexx} script that you want to share with other users. If you think you can contribute to the @{" future " LINK future } of InfraRexx, just drop me a (electronic) @{" mail " LINK authors}. @ENDNODE @NODE future "InfraRexx Future..." @PREV develop @NEXT order @{b}InfraRexx Future...@{ub} I want InfraRexx to become the perfect infrared interface for the Amiga, which is system- and userfriendly and gives good performance. Things I have in mind for further improvement are: · more ready-to-use codesets and more supported brands. · a new client/server model, with Prefs editor, etc. · not only ARexx, but also Shell and HotKey events; new program name. · a more modular approach to the codeset and code implementations. · a device independant way of controlling audio/video devices, so that an application can transparently control any device. · increased infrared transmission range, really a hardware thing. · hardware for parallel port and maybe serial port or even power LED. · IFF codeset file definition, fast asynchronous loading and saving. · improved graphic user interface, aspect-ratio (hi/lowres) sensitive. · context sensitive AmigaGuide online help support. · maybe a Magic User Interface version. (MUI İ by Stefan Stuntz). · many more usage ideas and implementations. · everything YOU suggest... I hope to implement many of the above features in an complete rewrite of the programs, with a much more modular approach in an object oriented way. @ENDNODE @NODE locale "Localizing InfraRexx..." @PREV develop @{b}Localizing InfraRexx...@{ub} If you want to see the InfraRexx messages in your own language, why don't you translate the messages yourself? I would be very glad if people sent me their localizations so that they can be included in future releases of InfraRexx. You need some knowledge of the localization procedure, but the following guidelines help you along. @{b}Localization guidelines@{ub} The InfraRexx software uses the locale library and language catalogs to adapt to the user's locale preferences. Catalog description files (.cd), as well as empty catalog translations files (.ct) are included in the InfraRexx archive. Use these to create a locale catalog of your language, using a catalog compiler such as CatComp. A more easy way is to use CatEdit by Rafael D'Halleweyn, a complete catalog editor with a very good GUI for editing the catalog strings. Follow these simple guidelines to generate a correct translation: - know the features of the software. - fill in the header of the translation file. - translate EVERY sentence in the translation file. - NOT change the order of the catalog strings. - be sure that every sentence is CORRECTLY and CLEARLY translated. - pay attention to the spaces around GUI strings (frames, sliders etc.). - use a texteditor that does NOT wipe out the end-of-line spaces. - adapt your translation so that the windows fit on a 'NTSC Hires Nonlaced' screen of regular size (640x200) using the 'Topaz 8' font. - Add this line to the STRING_ABOUT message (translated of course). \n\n translation by where is the name of the language you translated to. and is the name of the translator, yes, you! If you think you made a nice translation, please send the translation file to one of the @{" authors " LINK authors}. Also state if you would like to translate future versions of the software, or not. @ENDNODE @NODE order "How to order InfraJoy..." @PREV future @NEXT register @{b}How to order InfraJoy...@{ub} InfraJoy is the @{" hardware " LINK hardware} part of InfraRexx and is needed by the @{" software " LINK software}. Full plans and instructions are included with this archive to build the hardware yourself. However, the hardware can also be ordered via the @{" authors " LINK authors} by filling in the @{" registration/order form " LINK form}. Connector throughput Please indicate on the order form if you need a throughput connector design. The joystick can then be plugged into the InfraJoy hardware. This will keep you from switching connector over and over. Note that you cannot use the hardware while using the joystick. The Scala MM 300 dongle has been tested with connector throughput, and worked correctly. Extension cable For Amiga 500 and 1200 models, the joystick connector is situated on the backside of the computer, reducing the receiver performance, as the Amiga often blocks the infrared light. For those purposes, an extension cable of about 1 metre (3-4 feet) is an extra option. Amiga Model Also state the Amiga model the hardware will be used with, so that the receiver can be placed according to the joystick port direction. Optimisation Since InfraJoy v2, we are now able to, more or less, optimise the hardware for the electronics brand you use. This gives you a somewhat better response on both the Amiga side as the external devices side. Note that this is just a fine-tune, and that other brands will work as well, although maybe somewhat less responsive. Notes · Allow two to six weeks before delivery of the InfraJoy hardware. · By buying the hardware, you become a @{" registered user " LINK register} for free. @PREV develop @NEXT register @ENDNODE @NODE register "How to register to InfraRexx..." @PREV order @NEXT payment @{b}How to register to InfraRexx...@{ub} First of all, InfraRexx is freeware. You may use it to its full extend without paying a single dime, and without missing one single option. If you think InfraRexx is good or if you think it should become better, you should register. Also, if you built the hardware yourself and it actually works :), please register the software. To register, fill in the @{" registration/order form " LINK form} and send it, along with the @{" payment " LINK payment}, to one of the @{" authors " LINK authors}. Registered users stay registered even if InfraRexx may become shareware in the future. The register fee is DFL 10.- (dutch guilders) or the equivalence of USD 10.- (US dollars) in any other currency. Note that if you @{" order the hardware " LINK order } you are registered for free. Note that registering doesn't offer extra features, it just helps the future of InfraRexx. @ENDNODE @NODE payment "How to pay for what you get..." @PREV register @NEXT form @{b}How to pay for what you get...@{ub} Please send the money directly in cash or on an EuroCheck to one of the @{" authors " LINK authors}, along with the @{" registration/order form " LINK form}. When sending cash money, send the USD (US dollar) prices (or the equivalence in your local currency). If you send an EuroCheck, use the DFL (dutch guilders) prices. From countries outside Europe we do not accept checks as there are high costs involved. Cash money in an envelope, invisible from the outside, is often the best way to get your money across. @ENDNODE @NODE form "InfraRexx Registration/Order Form" @PREV payment @NEXT updates Use these handy buttons to first @{" edit " SYSTEM "Run <>NIL: Ed OrderForm"} and then @{" print " SYSTEM "Run <>NIL: Type OrderForm >PRT:"} this orderform. You can also use the Project/Print menu item to print an empty form now. Then send the form, along with the @{" payment " LINK payment} to the @{" authors " LINK authors}. -------------------------------------------------------------------------- @{b}InfraRexx Registration/Order Form@{ub} @{b}User Information@{ub} Name: ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ Address: ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ Country: ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ Internet/Fidonet E-Mail: ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ ( ) Yes, please e-mail new InfraRexx releases as uuencoded mail. For those that don't have access to FTP or an up-to-date BBS. @{b}InfraRexx Registration@{ub} ( ) Yes, I want to register to InfraRexx. I have included the registration fee (DFL 10 or USD 10) with this form. ( ) I get free registration because I order the hardware. @{b}Ordering the InfraJoy hardware@{ub} ( ) Yes, I want to order (some of) the InfraJoy hardware interface. I want to order the... ( ) complete InfraJoy hardware. (DFL 29 or USD 24) ( ) transmitter only (receiver can be added). (DFL 19 or USD 16) ( ) receiver only (transmitter can be added). (DFL 24 or USD 21) ( ) print circuit board (for both) only. (DFL 13 or USD 12) ( ) components (for both) only. (DFL 25 or USD 21) ( ) transmitter components only (DFL 15 or USD 13) ( ) receiver components only (DFL 20 or USD 18) ( ) Yes, add @{"connector throughput" LINK order 8}. (DFL 2 or USD 1 EXTRA) ( ) Yes, add an @{"extension cable" LINK order 16}. (DFL 4 or USD 3 EXTRA) What is the @{"Amiga model" LINK order 23} the hardware is used with? ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ ( ) If possible, @{"optimise" LINK order 100} the hardware for this brand: ŻŻŻŻŻŻŻŻŻŻŻŻ I have read the copyrights and disclaimer notes and agree, place, date: sign: ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ -------------------------------------------------------------------------- PLEASE NOTE: (Read @{" Payment " LINK payment} and @{" Ordering the hardware " LINK order} for details) · Only cash money or EuroChecks are accepted. If you send... ...an EuroCheck, fill in DFL (dutch guilders) currency and prices. ...cash money, send the USD prices (or the equivalence in your currency). · Please allow two to six weeks for delivery of the InfraJoy hardware. @ENDNODE @NODE updates "Obtaining Updates..." @PREV updates @NEXT authors @{b}Obtaining Updates...@{ub} Internet users New InfraRexx releases will be uploaded to Aminet, a worldwide network of FTP sites for freely distributable Amiga software. It can be found in the 'util/rexx' subdirectory of the Aminet tree ('pub/aminet') under the name 'InfraRexxX.X.lha' (X.X representing the release version). At the same time, an announcement will be posted to the Usenet newsgroup called 'comp.sys.amiga.announce'. Fidonet or Amiganet users For those there is a support BBS called 'Deep Space Nine', where the latest release of InfraRexx is available. For filerequests use the magic name INFRAREXX. The Fidonet nodenumber is 2:2802/123, the Amiganet node- number is 39:150/101. Deep Space Nine supports speeds up to V.FastClass (28k8). If all goes well, the updates should be available on SAN (Sky Amiga Network) too within a few days from release. Modem users The support BBS 'Deep Space Nine' (see above) is also accessable for non-Fidonetters, and supports speeds up to V.FastClass (28k8). The number is +31-40-480556 in The Netherlands (also known as Holland). Registered snailmail users Registered users will receive updates via snailmail, if they can't reach new versions through computer networks or local BBS systems. Snailmail users will receive two updates by means of a mailed 3.5" floppy (FFS). Fred Fish Submissions Major releases will be submitted to the makers of the Fred Fish series. @ENDNODE @NODE authors "Reaching the authors..." @PREV updates @{b}Reaching the authors...@{ub} If you have any bugs, ideas or if you want to @{" register " LINK register} or @{" order the hardware " LINK order}, write to one (or both) of the following addresses: @{b}InfraRexx software programmer@{ub} Leon Woestenberg Langenhof 62 NL-5071 TP Udenhout The Netherlands Internet: leon@stack.urc.tue.nl @{b}InfraJoy hardware designer@{ub} Jeroen Steenblik Retiestraat 13 NL-5628 PC Eindhoven The Netherlands Internet: jeroens@stack.urc.tue.nl Fidonet: "Jeroen Steenblik" @ 2:2802/123.2 @ENDNODE