CompuServe Thread

Programming modules hosted by Twin-X is very easy. For some, honest to goodness device drivers need to be written. For others, a device driver would be unwarranted and simple user written code would suf- fice. For example, for our multiple serial port modules (one module with 2 ports, another with 4 ports), we will be providing an AmigaDOS driver since all (well written) programs which use the existing de- vice expect to talk to the serial.device. Our 12, 14, and 16 bit Analog To Digital converters, however, will come with a simple subroutine library rather than a device driver. One reason for this is the trivial nature of the code to perform a sample (2 or 3 assembly language lines). It would be a waste to put this little substance in a whole device driver. Modules which we design and manufacture will come with ASDG quality software support. But, there are over three hundred modules already in production by companies outside the Amiga market. We expect mod- ules from these other companies to become support in one of several ways: 1. Someone comes along and writes the support themselves and puts it in the public domain. We will distribute this code as part of our Twin-X support service. 2. Someone comes along and writes the support themselves and makes the support a product (of their own). 3. Someone comes along and writes the support themselves and gives or licenses it to us. And we sell or give it away. 4. We decide on our own to write the support and sell or give it a- way. 5. Someone comes along and pays us to write the support or makes us an offer (to buy Twin-X IF we write the software) we can't re- fuse. One of the things we'd like to use our vendor conference here on CIS (listening Steve?) is to host a forum for Twin-X users to ex- change their code and information (as would we). There is sooo much that can be done with Twin-X, the mind boggles. By the way – this is the second time I typed all this stuff in since the first message was eaten by the system crash CIS experienced. Perry