From mint-bounce@lists.fishpool.fi Fri Oct 29 11:22:25 2004 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Message-ID: <41820C69.30100@utbm.fr> Date: Fri, 29 Oct 2004 11:24:57 +0200 From: Olivier Landemarre User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: mint@fishpool.com Subject: [MiNT] appl_getinfo extension Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: olivier.landemarre@utbm.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=-1.0 tagged_above=-50.5 required=3.8 tests=BAYES_00 X-Spam-Level: Hello At your know is there any extension in appl_getinfo() avaible to know if AES can support or not Interface extended ressource files?. If not I propose you to extend AES_SYTEM mode in ap_gout4 as a bit field with second bit for explain AES support interface ressource, so for this AES answer will be 3. Remark, I have no idea why you wan't have function to know AES activity under Mint, this absolutly not need, perhaps it should be better to add thread as Magic do (share code), one part could manage AES and the other continu to do it's work, even this second thread can do an mt_appl_init() if it need to have some interaction with AES (for example to do an mt_wind_update()). This my point of view. Olivier