Using a Nec chipset for the project we will keep away all the issues related with the VIA chips in SF, and these USB cards are quite cheap indeed.

In the other hand FireWire is far better IMO than USB, and yes, once the driver is made, there are only a few classes to be made, since there are far less device available for Firewire, so IMO its easier to get it running and support it.
And of course all the pegasos have the very same chipset for it on mobbo, and this way only one configuration have to be supported.

FireWire will do the job for me too.

Maybe will have to contact Guido or Chris Hodges, in order to know if they would be intereset in such a bounty.

Guido, Chris! We want you for the navy!

If any of you have followed recent news about Epistula (a MSN Client that was going to be developed for OS4, OS3 and the author wanted to support MOS too) it may be a good idea to create a bounty for a MSN client with full support of custom emoticons, file transfer, talking with various users in the same window, and maybe winks (these files are just flash animations so it may be possible to use these files using a flash player).

Maybe the gadu gadu author may be interested too?

[ Edited by Crumb on 2005/8/10 17:12 ]

If you think it is a good idea then open a bounty ! You just have to fill this form and find someone who is interested enough to put the $30 necessary to open a new bounty.

Speaking of which, a new bounty is open for discussion and hopefully I'll have the donation button up tonight..

ezPM

@Targhan

Two questions related to ezPM

First is a legal one:
Would it be legal if such a software would contact
a webserver and download MOSSYS-Components to repair
inconsistencies found ?
Guess only the Mos-Team can offer such service ...

Second question is technical (since the server will probably run
linux): Is there a tool that can extract the same version string using
linux from a MOS/68k-library/tool as the morphos "version
full"-command delivers ?

Technical first:
The server would really only contain a text file for comparison purposes, and would not be required to get a version string from any files.

Legal:
No MorphOS-Team files would be hosted; in fact, should such a tool find that your version of MorphOS has lost a PPC library or has an old version--it would simply inform you to insert your MorphOS CD. If a library (mcc etc) has an official MorphOS-Team version and a known stable external third party release, the user would be informed of such.

In the case that there is an official online update from the MorphOS team, then the user would simply be notified of the fact--and would simply be reminded that they must be registered with MorphOS-Team.net to recieve those updates.

The main purpose is to control those third party system files and to make sure that the user hasn't over-written their MorphOS specific files.

Furthermore, this tool would *not* be for MorphOS System beta-testers.

Quote:

Well in the case of betatesters he would notice that installed files are newer than distributed ones and not overwrite them.