Here is a quick update. I will put this on the project status pages when they are up again.

Preliminary evaluation of the portability of NAS, the Network Audio System is now complete. The following items have been identified:

* Configuration is dependant on X11. Manual configuration is possible but will likely take some time.

* Depends in part on X11 but this seems to be fairly isolated. My *guess* is that this can be worked around with a small wrapper.

* Platform specific code and non ISO-C constructs are common and may require some extra work. Some functionality might be unavailable without too much work but the same seems to be true for win32 and OOo works there so this is likely not a problem.

* Actual audio code is relatively well isolated and when the api is understood, it would likely be easy to map to AHI. (NB: I do _not_ know how AHI works, so this is partly a guess)

Overall portability: 6 of 10. Suggested skills for porting: Unix, Sockets, C, AHI. Suggested first steps: Untangle build system and configure manually.

As for the testing of existing ports it goes forward but will take a bit of time as I am attempting to test more than minimum basic functionality. (And my day-job is taking quite a bit of time at the moment)

And finally, a question for Thomas or/and Hans-Jörg (I said I would take you up on the offer to answer questions about V50+ programming :)

1) Is it legal to call dos.library/FSync() on a filehandle obtained from dos.library/Open()?

2) Is intuition.library/AllocScreenBuffer() broken with regard to the SB_COPY_BITMAP flag?

3) How much should I trust the autodocs? I.e. are they completely up to date, 75% ok or 8.1% ok?

-Peter aka. Archprogrammer

Reality is for people who cannot face ScienceFiction. Only lefthanded people are in their right minds.