Some comments back:

Quote:

openMSX ======= * Optional automatical speed up during disk or cassette action blueMSX have had it since the day we added more realistic timing to the floppies (since 2004). all MSX emus has fast loading so the feature should perhaps be called optional Slow disk and cas loading

AFAIK openMSX is the only emulator that has accurate emulation and still automatic loading speed up, without the MSX knowing, so without influencing the state of the MSX (so, no risk of glitches).

Quote:

* Optional automatical loading of cassettes in CAS format * I think fMSX and others support cas files as well. some MSX emulators including blueMSX supports a couple of different cas formats.

This is not about the CAS formats, but about the automatical loading.

Quote:

* XML files to specify the hardware to be emulated, so you actually emulate specific MSX machines I would say NLMSX was the first emulator that allowed real MSX machine configuration. blueMSX also has it and both NLMSX and blueMSX has text files describing the machines, although not in XML format, but thats not really a feature.

AFAIK openMSX was actually the first emulator to emulate realistic machines, not fantasy or generic machines only. Am I wrong?

Quote:

* Autodetection of emulated video sources Not sure if openMSX has this too. The meaning is if user first uses the V9938 and then runs an app that is using a different video chip, the emulator automatically switches and displays the output of the new video chip

Um, what is this? A convenience feature that changes the hardware of the emulated MSX on the fly?
openMSX doesn't have that.

Quote:

* Audio capture Some other MSX emu must have had this feature before blueMSX, like paraMSX or something, or?

Well, at least it's not unique.

Quote:

AFAIK openMSX is the only emulator that has accurate emulation and still automatic loading speed up, without the MSX knowing, so without influencing the state of the MSX (so, no risk of glitches).

blueMSX have had this since 2004 or so. When loading disk images, the emulation automatically start running at max speed and then goes back to normal. So I think this actually is a 1st feature of blueMSX.

Quote:

This is not about the CAS formats, but about the automatical loading.

Ah ok, like the automatic loading in VICE, where you just insert a cassette and it loads the game automatically?

Quote:

AFAIK openMSX was actually the first emulator to emulate realistic machines, not fantasy or generic machines only. Am I wrong?

I'd say NLMSX is the first because it was the first real attempt of doing user configurable machines. It didn't allow as many configuration options as blueMSX or openMSX, but openMSX doesn't do a complete configuration using scripts either. blueMSX and openMSX are about equal when it comes to user configurability using scripts or gui and openMSX was of course earlier than blueMSX in this sense. But I still think NLMSX is the pioneer here. In either case, machine configuration is not a unique feature of MSX emulators nowdays.

Quote:

Um, what is this? A convenience feature that changes the hardware of the emulated MSX on the fly? openMSX doesn't have that.

Yes a convenience feature that can be disabled. It doesn't change the hardware, only connects the monitor to the active video processor (V9938 or 80 column cards in blueMSX)

Quote:

Well, at least it's not unique.

It says 1st but I doubt it was the first MSX emulator that had it.

Quote:

Quote: AFAIK openMSX is the only emulator that has accurate emulation and still automatic loading speed up, without the MSX knowing, so without influencing the state of the MSX (so, no risk of glitches). blueMSX have had this since 2004 or so. When loading disk images, the emulation automatically start running at max speed and then goes back to normal. So I think this actually is a 1st feature of blueMSX.

Aha, OK Well, it's a very handy feature

Quote:

Ah ok, like the automatic loading in VICE, where you just insert a cassette and it loads the game automatically?

Yep, exactly like that.

Quote:

Quote: AFAIK openMSX was actually the first emulator to emulate realistic machines, not fantasy or generic machines only. Am I wrong? I'd say NLMSX is the first because it was the first real attempt of doing user configurable machines. It didn't allow as many configuration options as blueMSX or openMSX, but openMSX doesn't do a complete configuration using scripts either. blueMSX and openMSX are about equal when it comes to user configurability using scripts or gui and openMSX was of course earlier than blueMSX in this sense. But I still think NLMSX is the pioneer here. In either case, machine configuration is not a unique feature of MSX emulators nowdays.

Well, the fact that we tried to emulate real(istic) machines was what I meant. I guess that was actually new. This was started in 2002.

Quote:

Quote: Um, what is this? A convenience feature that changes the hardware of the emulated MSX on the fly? openMSX doesn't have that. Yes a convenience feature that can be disabled. It doesn't change the hardware, only connects the monitor to the active video processor (V9938 or 80 column cards in blueMSX)

Ah, OK. We didn't find a realiable way to make this work for GFX9000.

Quote:

Quote: Well, at least it's not unique. It says 1st but I doubt it was the first MSX emulator that had it.

[/quote]

Where is this first/unique stuff on the blueMSX feature list anyway? I can't find it.

Anyway, I'll correct some things.

Quote:

Where is this first/unique stuff on the blueMSX feature list anyway? I can't find it.

its in the .chm documentation. If you have a .chm reader, you can download the latest release (.zip version) from the bluemsx website.

manuel: the space (or return + a bunch of spaces) between the icon closing span tag and description opening span tag, try it.

hap, I can't test on IE7, so what should I try?
Sounds like a bug in IE btw.... anyway, thanks for reporting it.
EDIT: oh, I just remember that there was still some non-standards compliant thing in the features page. That might have to do with it as well.

Try removing the space between those spans, I can test if the problem's fixed afterwards. (works fine in Firefox btw, so yeah, most likely an IE7 bug)

The first time I saw machine configuration files was in RuMSX. That must have been before 2000, because I was still running Windows at that time. It had INI style files that described the slot map etc. It might have been fantasy machines instead of real MSX models though.

About "fullspeedwhenloading": I think the idea has been in the bug database for quite a while before it was actually implemented. So it seems blueMSX was first indeed.
By the way, the fast loading of fMSX doesn't count because that's just a dirty hack to avoid emulating the FDC and disk drive; it has instant loading as a side effect. This approach breaks several games, most prominently the Aleste Gaiden intro.

Anyway, openMSX and blueMSX have many of the same features, especially since we regularly use each other's code

hap, what's the use if I remove it, if you already removed it and showed that it helped? We'll first have to make sure we have valid XHTML there.

In these unique/1st rules, does MESS count as MSX emulator? If so, you might want to make a few additional changes.

Yeah, I downloaded the site, and made some manual changes. Removing the space seemed to fix it.
I'm not sure the problem I'm seeing happens for every XP/IE7 user though.

*edit* http://home.planet.nl/~haps/crap/openfeat.png

Quote:

In these unique/1st rules, does MESS count as MSX emulator?

Absolutely. You have give the info though because I haven't used mess much at all.

For one thing, it supports input recording/playback (aka event logging in blueMSX).

Some other smaller features too, like gamma/brightness correction, you'll have to check for those yourself, I'm not completely sure: http://www.mess.org/