I love BrMSX. Too bad that it isn't supported any longer. Anyway, even today I'm using the patched version that does work in Windows XP. I know that RicBit is currently integrated in the BlueMSX team, but I love the oldschool emulators for DOS, such as BrMSX and NO$MSX.

ATM, I mainly use openMSX 'cause I've moved to Linux, but I do use both BlueMSX and openMSX when using Windoze. BlueMSX debugger is awesome and openMSX isn't easy at this level. I use both emus basically for MSX1 development. Several problems still happen, but both do an excellent job for average users, I guess.

From my MSX1 freak developer point of view, I'd like to highlight two details:

Pro openMSX: excellent WAV support
Pro BlueMSX: user friendly debugger

If one of those emulators had the two points that I mention, I'll stick to it faithfully and drop the other.

@pitpan: I think you'll get both features on both emulators sometime this year

well i tried openmsx yesterday and i didnt like it very much, although it is looking nice and has a lot to offer but basically bluemsx looks easyer to use so i think i stick to bluemsx. (and offcourse playeing a cloecovisiongame is very very retro, which i do like)

Quote:

DemonSeed, this is true I know. Before my linux era, I used NLMSX quite a lot (and that was too, because I was on a 600MHz system, too slow for BlueMSX/openMSX). But some of the basic things are not supported in that emulator (e.g. SCREEN 3).

openMSX runs on a 200MHz GP2X, so, it definately runs on a 600MHz system. Just don't demand the most fancy settings/effects.

In some words:
bluemsx is simple to use (easy) the debugger is very user friendly.
but
openMSX is a very sofisticated tool for example you can stop execution when a program do a out(0x98),a with a=10. That's is not possible (AFAIK) in bluemsx. Not to mention Disk manipulator, a true gem....

I honestly don't think openMSX is more sofisticated than blueMSX. overall they are quite equal when it comes to what you can do. the disk manipulator v9990 support and the contitional breakpoints are features that are unique to openMSX but blueMSX has quite a few unique features as well, like obsonet support, digitizer support, midi in, scsi cd audio and much more.

So I get a bit annoyed when people think that simplicity means less features. Overall I think blueMSX supports a bit more stuff than openMSX but overall its about the same.

Quote:

I honestly don't think openMSX is more sofisticated than blueMSX.

Umh, i've been misunderstood. More sofisticated means about the debugger and diskmanipulator features.
And obviusly, it's a my opinion. Of course this opinion is influenced by the fact that i'm more interested in openMSX features (the debugger flexibility is one), than on others like cd audio or digitizer support.

Quote:

So I get a bit annoyed when people think that simplicity means less features.

Again, i've been misunderstood. Ease of use does not imply simplicity (but now we must define what kind of simplicity), always.

As usual is a matter of opinions and backgrounds. For example:

Most peoples think also that the absence of an integrated gui it's a openMSX limit. I respect this opinion, even if for me is not a limit. I feel well even with a command line interface.

OpenMSX has moonsound 4-op support, does blueMSX?

blueMSX can make me coffee

GhostWriterP: blueMSX reused the openMSX code for MoonSound. (Yes, we borrow some code from each other every now and then!

Since both openMSX and blueMSX are open source emulator with GPL license it makes sharing code very easy. Most features doesn't require that much modifications to be ported from one emu to the other. There are quite a few features that were developed in one emu and ported to the other. Sometimes the other emu makes improvements that are brought back to the first emu. So feature wise the emus are quite comparable. Some features are harder to do in one emu than the other and thats one reason why there are some differences. Conditional breakpoints are for example easier to implement in openMSX, digitizing is easier in blueMSX.

Quote:

GhostWriterP: blueMSX reused the openMSX code for MoonSound.

The blueMSX 2.7.1 build 30196 I have produces crap playing 4-op fm tones. So do I have an old build?

GhostWriterP, can you be a bit more specific on what kind of crap (more precisely what apps are you running)? 2.7.1 is the latest version btw.

Actually I prefer bluemsx because its debugger is very user friendly (even if it lacks of conditional break-points).

Said that, IMHO bluemsx some very nasty "features":

1) the emulation speed is ruled by a small wheel: please DESTROY all the wheels in the GUI and replace them with sliders, they are absolutely unusable;
2) even if the problem seems reduced in the last version, bluemsx has some graphical problems with windows (eg. the interface, after a while you do not touch the emulator, passes trough windows on in front of it and the program tends to become instable).

I usually don't use the speed wheel. I remap 'toggle fullspeed' to F11 or some other easy to access key. I use the speedup very frequently and the wheel (or a slider) wouldn't work for me.

For the second issue, do you have the emulator running or stopped when these issues occur? I use a multi desktop application so I always have bluemsx as the only or almost only app in one desktop so I never experienced this issue.