which emulator is error free opposite the MSX computer in the original:

- open MSX or bluemsx?

mfg Peter

No one can be error free :-(

Use both emulators to test software, it's the best practice.

Indeed, both emulators do their best to be as accurate as possible (and they're most certainly the most accurate MSX emulators available), but they are not error free. Very little software is error free, but moreover, both emulators are still heavily developed on, so bugs will be introduced. This is quite normal, as we're all human beings, who make mistakes.
Other than that, there are some very nasty details that can not be emulated properly (chips without refresh e.g.) and there are some things that are simply unknown (some details of VDP speed e.g.), so they cannot (yet) be emulated correctly either. Another thing is that some details of the sound chips are not correct, which means music composed on the emulator could sound a bit different on real hardware. This is mostly notable for sound composers themselves...

You can use these emulators as a basis, but you should never rely 100% on them. They will work correctly for most programs, though. But still: always check on real hardware! (And if it differs, please do tell the authors of the emulator!)

thanks for that white.
bluemsx I could test to jezt well, but probably not gebug.
I open MSX also gladly times to test, wars however Rome not loaded the English description read, do not understand I however not who can it to me once well explain my English am unsatisfactorily and I have now with 59 years again begun to program.
translate do I this text with babelfish.

mfg peter

Quote:

translate do I this text with babelfish.

And it did a piss poor job, if you ask me

I know the rule of this forum is to post in English, but I'd really prefer if super_castle would post in German (that seems to be his language, looking at what Babelfish did)... I think most of us would be able to understand, if not I can make the translation.. I'm not stellar at German, but I can read it well enough....

@super_castle: Are you programming in basic or assembler? If you program in Basic, you can use bluemsx or openmsx and the result will work on real MSXes in 99.9% of all cases. You have to do something very weird (that probably only NYYRIKKI can do ) to make it look different on the emulators and a real MSX.
If you program assembler, there are a few things you can remember and you will also be almost sure it works on real MSXes:
1. The most common mistake/problem is to send data too quickly to the VDP. On emulators it will look good but not necessarily on a real MSX. On MSX1, you can only output one byte to the VDP every 28 CPU cycles. On MSX2, you can use otir or consecutive outi's and it will be ok.
2. If you're doing something advanced like screen splits, or other very timing sensitive things, there is a chance that the output will look slightly different between emus and real MSXes.

I use blueMSX when programming quite advanced demos and sometimes I need to fine tune timing to make it run properly on a real MSX, but when I do more regular stuff I don't have any problems developing using emulators (but since I write one of them I know what to watch out for)

Does babelfish output improve when for example translating German to Dutch, and then Dutch to English, or something like that?

I just can't resist...

Quote:

If you program in Basic, you can use bluemsx or openmsx and the result will work on real MSXes in 99.9% of all cases. You have to do something very weird (that probably only NYYRIKKI can do ) to make it look different on the emulators and a real MSX.

Now that you mentioned... My BASIC demo called "Sieni Pakottaa" does not actually run correctly on BlueMSX. It seems that the R800 emulation is a bit too quick and that causes wave effect to end before end of screen. Last time I checked the effect was even much worse on OpenMSX.

Link: http://www.msx.org/modules.php?op=modload&name=Downloads&file=index&req=visit&lid=481
(MSX tR & DOS2 only)

Quote:

I open MSX also gladly times to test, wars however Rome not loaded the English description read

Can you explain to me what you mean? Better write in German than in this translated English...

Nyke: can you please try on the openMSX 0.6.2 beta I posted the other day? I think we made quite some improvements a while ago. If you insist, I can also make an AVI movie for you that shows your demo.

"Nyke"! Now there's finally a sense making alternative that's easier to remember.. ^_^

Oh, I checked: the wave effect behaves the same in openMSX as in blueMSX: it stops about 10 lines too early...
Thanks for reporting this. I added an item in our bug tracker for this issue: http://sourceforge.net/tracker/index.php?func=detail&aid=1687188&group_id=38274&atid=421861

Its a very interesting bug, because 10 lines is like 3% faster which is very much. I'm not sure what the reason is for this big number but the TR timing is much more complicated than MSX2. A guess though is that its either some not so frequently used z80 instruction that has wrong timing and is executing a lot in this demo, or perhaps some VDP bus timing (although the latter is a bit less likely).

Ah, you are always so quick.

The part of the demo that is causing this problem goes something like this:

1 _TURBO ON
5 DEFINT A-Z
10 TIME=0:FOR I=0 TO 1:I=TIME:NEXT I
20 K=K+1:I=K
30 I=I+1
40 VDP(19)=M(I)
50 IF I-K<93 THEN 30
60 IF K<900 THEN 10

There is also another "feature" in this demo that I would like someone to verify...

On my real MSX tR it somehow seems that in the wave effect the color brightness on some lines is different than on neighbour horizontal lines. Is this caused by my monitor or is there some undocumented behavior in V9958?