Yahoo Groups archive

Emax

Index last updated: 2026-04-28 23:23 UTC

Message

Re: [emax] Re: Question to Esynthesist..

2005-11-08 by Alex Pereda

Waiting until a stable release of the windows version is the way to go.




On Nov 8, 2005, at 1:59 PM, esynthesist wrote:

> About the issue to port EMAXLib to Linux and Mac:
>
> I will publish the C-code of the software and also a EMAX I/EMAX II
> specification document explaining the complete structure of the disk
> images, including the 8-bit compression algorithm.
> This however will be done only after the first official version has
> been released (version 1.01).
> I don't think it would be a good idea to do it now because I'm still
> working on it frequently. The code is still incomplete (alpha
> version) and ... also a little bit dirty. A lot of comments are
> missing, so the code is hard to read at the moment.
> I will first clean up the code, add the missing features, and also
> make it a more modular so that the functions have a granularity that
> can be used by GUIs.
>
> Both code and specification document will probably be published under
> the GNU GPL license.
> I don't know when this will happen - I'm taking a break now and I'm
> also waiting on more feedback & test results from the community :-).
> Probably 1Q2006.
>
> ///E-Synthesist
>
>
> --- In emax@yahoogroups.com, poeml@c... wrote:
>>
>> Hi E-Synthesist,
>>
>> On Tue, Oct 11, 2005 at 09:33:41PM -0000, esynthesist wrote:
>>> Yes, it's being programmed in ANSI C (well, I'm not sure about
> the
>>> ANSI stuff, but hey, who cares :-)
>>
>> :-)
>>
>>> So porting to Linux or whatever platform is definitely an option,
>>> though I'm using some tricky MS-DOS calls. But these can easily
> be
>>> replaced by MAX/LINUX system calls or maybe even by C-calls (I'm
> a
>>> bit lazy in checking all C-libraries :-)
>>
>> Actually, I'm not worried too much about those calls.
>> I once had the intention to port the DOS program EMX (written in C)
> to
>> Linux, and I found that all those DOS C calls were not needed in
> Linux
>> because all is managed transparently in the kernel when simply
>> reading/writing from/to /dev/fd0u800. In fact, I ended up with a
> simple
>> 20-lines shell script.
>>
>>> Porting requires of course the distribution of the source code.
> I'm
>>> still struggling on that one, you know: stuff like GNU and so on.
> I
>>> have no problem to publish the source code (in fact I like open
>>> source) but the way I should do it is not clear to me yet... I
> have
>>> to check the possibilities.
>>
>> If you have specific questions, maybe I can help. :)
>> First of all, make sure whether your code includes any foreign code
> (for
>> example, snippets that you copied from elsewhere) or if it is all
> owned
>> by you, because obviously you can only give away your own code :)
>>
>> Have you experience in working with CVS or subversion repositories?
> I
>> can offer to host the source code, and/or a web site for news and
> such.
>>
>> Peter
>> --  
>> the pink cardinal imitated the big cardinal
>>
>>
>> [Non-text portions of this message have been removed]
>>
>
>
>
>
>
>
>
> ------------------------ Yahoo! Groups Sponsor -------------------- 
> ~-->
> Get fast access to your favorite Yahoo! Groups. Make Yahoo! your  
> home page
> http://us.click.yahoo.com/dpRU5A/wUILAA/yQLSAA/QnLolB/TM
> -------------------------------------------------------------------- 
> ~->
>
> Emax and Emax II User's Group Website
>
> http://www.silveriafamily.com
> Yahoo! Groups Links
>
>
>
>
>
>

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.