> >have the guarantee of a full compatibility between different
> projects and a
> It's a good idea to standardize the new MSX efforts, it will
Iim sure that Phoenix is something needed for the MSX system, and with
Phoenix all the programmers will be in contact with hardware developers
to work together.
> > But I wonder, how will the Phoenix standard be decided?
>
> As I said Phoenix depends on Internet, there is no discussion about this,
>therefore Phoenix must be decided in Internet, I will contact with Tristan
>and Funet will have a Phoenix directory, Padial will publish schemas and
>complete information about the finished projects.
> The Phoenix web is another important part.
But what about the developers which don't have internet-access??? I know
Hans van Oranje has, and others might be able to access the internet via
school or the library, but I don't think they all have internet-access.
> > like. Some people want full compatibility with nowadays MSX,
> > other people
> > want a machine that will run Linux, some are willing to pay
>
> The real users want a evolution, full compatibility with old MSX but new
>possibilities, this means a real hardware revolution, maybe Z380 could be
>the key for a new MSX future, for the moment Padial have sold 35 Z380
>boards without finishing it, so it is important to give a real support
>for new hardware developments.
>
> > An alternative to consensus would be voting, in that case
> > who gets to vote? Anyone who subscribes to a Phoenix mailinglist?
>
> This is not neccesary, how many hardware developers are in the world??,
>maybe with the hand fingers is enough to count them, there are many
>programmers, but the programmers depends on the hardware developers, so
>the main characters of Phoenix are the hardware developers:
>
> Padial, Ademir, Culla, ESE, Henrik...
I don't agree with that. Software-developers must also have a "vinger in de
pap", because they are the ones who are going to use it, and they can tell
which things are useful, which not, and they can give very useful
suggestions or tips, for example on a feature which makes a certain board a
little more expensive, but at the same time is of a great help to
programmers (for example an external interrupt or so).
> We need to stablish a real relationship between them, in that time Phoenix
>will be running, but before that we must give them an Internet support.
no comments
> > Another question: what are the starting assumptions for Phoenix?
>
> Well, this is certainly complicated, I think Phoenix must assumpt the
>system hardware developments like Z380, new musics board, new VDP boards...
> Nowaday we have no problems because there is only a new music board and a
>new VDP board (I think): Moonsound and GFX9000, but it could be a real
>problem if somebody makes a new OPL4 incompatible with Moonsound, Phoenix
>has the responsability in this kind of problems.
Ah, this is very good. In a lot of projects the OPL4 of v9990 is not listed
or is listed but in an incompatible way... I'm very glad with this...
relieved.
By the way, there was some guy (dunno where) developing an OPL3 board!!!
Aargh! Let us make it MoonSound-compatible and convince this guy to use
OPL4!!! (which can still be achieved).
Oh, by the way, I think a new MSX must have a decent timer of which the
speed can be set and which can generate an interrupt. This is definately
useful, in example for JoyNet.
>> you write MSX, do you mean "something that is 99% compatible
> > with MSX2" or
> > do you mean "something that carries the spirit of MSX" or
> > something else?
>
> We know that MSX is a generational standard, theorically MSX-TR is
compatible
>with MSX-1, MSX-2 and MSX-2+, MSX 2 with MSX-1...possible new MSX computers
>have to be compatible with MSX TR, 2+, 2 and 1 obviosly.
Ok, that is perfect.
> > >developers and programmers for getting a common agreement.
> > I have experience in web and software.
> > mailinglist), but maybe it's easier to use existing services,
> > Phoenix directory on funet.
>
> The Phoenix directory in funet is a good idea, but it is neccesary to
>create a new mailing list, this ML has a big number of unuseful messages
>for developers, the new MSX mailing list is oriented only for MSX
>developers, so emulators, opinions about games or tips are strictly
>prohibited.
This mailinglist is, I have to say, quite emulator-less...
Compare it with news://comp.sys.msx which has a lot of emulator-talk.
> If you have a good knownledge of WEB programming, contact with my POP3
>adress: [EMAIL PROTECTED], I will coordinate the creation of a WEB
>programming group, now we need about 10 Mb or more of web space in a
>free server, it is important to have an own DNS.
I can program HTML and a little java(script), and I'm learning CGI. So I
might be able to help.
About free webspace: I know how you can disable the advertisements in
Geocities, so you can get 11MB of free space without ads. And if you use a
nice URL redirector like cjb.net, you can get 11MB of webspace with an URL
like http://phoenix.cjb.net
If needed, CGIs can be hosted on another server, I know one which allows
them.
Nice, isn't it?
~Grauw "Phoenix is a great idea"
PS. I think you should make a "phoenix seal of quality", just like Nintendo
has...
--
>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<
email me: [EMAIL PROTECTED] or ICQ: 10196372
visit the Datax homepage at http://datax.cjb.net/
MSX fair Bussum / MSX Marathon homepage: http://msxfair.cjb.net/
>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<
****
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put
in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the
quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
****
