>I then think that, when also keeping in mind what you wrote below, you
>shouldn't call it an MSX.
Why not? If it's compatible to the MSX standard, it's an MSX...
>An eventual new MSX should be made of a Z380, OPL4, a v9990 in combination
>w/v9958, some memory (about 4MB), etc... Especially the Z380 is important,
AFAIK, the z380 isn't produced anymore and barely available.
Not a good starting point...
>and the OPL4 and v9990 are also important new hardware,
And again, AFAIK, also both reaching the end of their lifecycle...
>with which you can do lots of things, although not 3D
>(which I don't think is a disadvantage).
Amen :-)
>> 2. it should have decent graphics capabilities and graphical user
>> interface (BeOS maybe?).
>
>You only say BeOS because you don't want to go Microsoft.
Noone wants M$
>But, I agree BeOS is a nice OS... Especially the 404 error message...
Ever tried to install a scanner on Win59? >-)
Nice blue screens ...
>> 3. there must be some kind of built-in programming environment and
>> graphics tools, to give oportunity for creativity.
Why should they be built-in? I think that most of the developers now
don't use BASIC, but use asm or C in the MSX-DOS(2) environment.
IMHO anything built-in is just waste of ROM/RAM space...
A new MSX will most certainly have some kind of disk access
(good old floppy, HD, ZIP, you name it). If the environement is
installed on this kind of media and can be loaded with a simple
command (say "BASIC" ;-)) you're all set.
>> But I doubt, if this programming environment could be 'old-style'
>> BASIC. Maybe some modification of Visual Basic (Microsoft, again...).
Why couldn't it be some kind of BASIC? Just leave out the line numbers,
introduce named subroutines and/or procedures, and make it run in
some cross-breed between a compiler and interpreter (like XBASIC(?),
but without the required _TURBO [ON|OFF] commands)).
Would be perfect...
>I don't know... How could such a system boot in Visual Basic to
>'inspire gameplayers for programming'...
I agree. Starting to develop any progam in VB is way too much of a
hassle.
Eric (who still doesn't think much of a new MSX)
****
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/)
****
