I posted some on the VDP command execution speeds:
Indeed, current VDP commands speed should be nice to run SymbOS and such, but at the moment even software emulators are a better choice for development (from the point of exactness of timing).
The question is whether exact VDP timing and other backward compatibility issues should be solved (at least in MSX2-compatible mode) or the upward compatibility is enough (I mean that if any existing MSX/MSX2 program runs in OCM, that's enough).
or the upward compatibility is enough
I think upward compatibility is enough. So far MSX2, MSX2+, MSX-TR has been almost 100% backward compatible. Imo its unfortunate that the WSX and TR aren't timing compatible but thats not so important. It sounds like the OCM can't be 100% compatible with MSX2 so even in an MSX2 mode it will not behave as a real MSX2.
If the ocm would be 100% a normal msx2 in every way what would be the point of buying it.
well, it has a decent keyboard, built in up-scan-converter and is very lightweight
well, it has a decent keyboard, built in up-scan-converter and is very lightweight A decent keyboard? afaik, the OCM ships without keyboаrd
(and on that 'decent' keyboard you want to plug in, show me the [Graph], , [Select], [Kana] or [Any] keys )
all true. Better put: it has "flexible" keyboard options
all true. Better put: it has "flexible" keyboard options :Plike this? oO
oh, those things so incredibly suck!
oh, those things so incredibly suck!
I know a certain lady who does the same.. ahum. sorry.
they do? hmm, I never tried but atleast it LOOKS cool. Thaz worth something, ainnit?