I'm wondering how many people already tampered with openMSX configuration files to create 'the ideal xml profile'.

I for one made a NMS8250 with 256KB RAM, SCC+, MSX-Music, and Muziekmodule in order to do the emu comparison tests

Maybe we should make something of a collection of those files and post them here, or elsewhere on this site. Until the software has it's own good interface.

Hmm... iirc, one of the openMSX testers that frequents #msx (his nickname is openmsx btw ) sent me a zip file with a lot of different configuration files, each emulating a specific MSX... Maybe he can be convinced to publish those files?

I think these files will in time be released on the OpenMSX page. I didn't fiddle around with the config yet to get the ideal MSX, but that's because very serious plans for a launcher are made. There is a topic posted in the Development section. It'll probably be moved to this section btw.

Just be a bit more patient
The XML format for openMSX is about to change (for the better) and eventually (and ideally) openMSX will come with config files for all MSX machines ever made.
The biggest problem with distribution right now is ROMs.

You can also look at my site ... on my openMSX page, I've tried to make .xml files that correspond to the by default configurations of NLMSX.

The direct link to this page is :

http://www.marsupone.com/msx/openmsx.htm

You can then download a zipped file with 8 .xml files (4 configurations without empty SCC+ cartridge, 4 configurations with empty SCC+ cartridge). The MSX 2, 2+ and Turbo-R configurations include MSX-AUDIO and MSX-MUSIC. I didn't include support for mouse of joystick, because I think it must stay optional. All these configurations correspond to Japanese MSX machines with more RAM and other add-ons.

I think that before to make configurations that correspond to specific machines, it's better to have "general" configurations, as in NLMSX.

How about universal configurations, that can be used in more than just one emulator?

Configurations in openMSX are XML and they generally do not contain any emulator specific settings, so should be interpretable by any other emu.

Snout wrote:

Quote:

How about universal configurations, that can be used in more than just one emulator?

GuyveR800 wrote:

Quote:

Configurations in openMSX are XML and they generally do not contain any emulator specific settings, so should be interpretable by any other emu.

It shouldn't be that hard to make a conversion tool for that.

Quote:

I think these files will in time be released on the OpenMSX page. I didn't fiddle around with the config yet to get the ideal MSX, but that's because very serious plans for a launcher are made. There is a topic posted in the Development section. It'll probably be moved to this section btw.

In fact, most of these config files are in openMSX CVS now, so don't worry about that. The snapshots also includes them and then next release will also have those config files included. Of course you can create your own fantasy MSX also. Note that these config files will be actively maintained by the openMSX developers.

As GuyveR800 already said: the config file format will change drastically in the near future. The XML will be a lot simpler then. Also, at the moment we have made a split off in the config files: configuration of the emulator itself is now completely separated from the configuration of the MSX machine. This way, it should be possible to easily exchange configuration files. In the end, we hope to be able to have a config file included in the MSX hardware list.

Since the machine configs are in XML, they are very easy to convert to any other format (e.g. MSX hardwarelist database entries...)

Don't forget: please send the openMSX developers as much feedback as you can! Preferably by filing a bug report or feature request on openmsx.sf.net in the tracker system. If you're logged in we can respond to you. Don't forget to check if your bug is already a known problem by browsing the bugs that are already there.
Thanks!

Quote:

There is a topic posted in the Development section. It'll probably be moved to this section btw.

I've moved the topic to the emulation section since it isn't MSX development, but actually for emulation purposes.