http://wiki.aranym.org/ 2012-05-18T07:45:02+02:00 http://wiki.aranym.org/ http://wiki.aranym.org/lib/tpl/default/images/favicon.ico text/html 2006-02-05T06:17:05+02:00 http://wiki.aranym.org/natfeats/about?rev=1139116625&do=diff Native Features is a powerful name for a technique and API with a simple goal: to allow the software running inside ARAnyM use certain features of the host platform. Various emulators used their own incompatible hacks but we wanted to set up something that could become a standard for other Atari emulators as well. Video, audio, network and other NatFeat based drivers should work on any NatFeat enhanced Atari emulator. text/html 2006-02-05T06:29:38+02:00 http://wiki.aranym.org/natfeats/best_practice?rev=1139117378&do=diff The entry point to any Native Features functionality from a user application is device driver entry that is accessible in your DEVDIR folder. Every such driver has to provide its own 'protocol' description which needs to be followed in order to be able to successfully use it. An example of such protocol can be the MultiTOS introduced Drag & Drop protocol as described in the Atari Compendium. text/html 2006-02-16T01:43:16+02:00 http://wiki.aranym.org/natfeats/example?rev=1140050596&do=diff There is a complete Native Features SDK ready to develop new NF's to be easily accessible according to the Native Features Best Practice document. The key is to provide device drivers for every functionality implemented using NF. The base usage code to use NFs is completely the same for both FreeMiNT .xdd and BetaDOS .bos driver (except for the #include statements and a single nf_ops initialization line). text/html 2006-05-21T23:47:53+02:00 http://wiki.aranym.org/natfeats/proposal?rev=1148248073&do=diff Original proposal document by --- Laurent Vogel 2001/12/08 This document describes a general technique to allow interaction between software running on a m68k processor inside an emulator, and native software. In this document, the emulator is some software running on a native platform, to run software in a 68k platform. This document specifies a general technique by which 68k software can interact with special native software to achieve special effects not allowed directly on the 68k platfor…