No RS232 or Obsonet support

You used my garbled e-mail which I use to prevent spam. As is hinted: REMOVE the CAPS from the address and it should work.

Anyway, using the Setup Guide that comes with openMSX (and the other config files), it should be pretty easy to create a config file for any MSX with standard hardware.

Could someone with a real Yamaha AX350II please contact me?

About RS232 and Obsonet: indeed, we haven't done anything about those two things. If you want that to change: please help us. File feature requests, provide information and test cases, talk to us, tell us *exactly* what it is you want, etc. We work completely open, so it should be no surprise that it isn't there.

Eh, openMSX has RS232 support and it has had it for quite some time...

mth: he means this.

Anyway, no problems/bugs at all?? Come on! I don't believe that!

Quote:

Eh, openMSX has RS232 support and it has had it for quite some time...

It supports the rom, but dont work like an rs232, so is useless.

Quote:

mth: he means this.

Exact.

Other possibilities

-support Laserdisk (pioneer px7)
-support (future) symbos rs232 --> tcp

In the obsonet side, we have the bluemsx support, but only under windows.

Is planned obsonet support for symbos too.

Are there any plans to support Yamaha KYBT2 networking (YM8032 chip) ?
It can be very useful for diskless Yamaha YIS503IIIR owners with tnt23's msx-link.

Quote:

Anyway, no problems/bugs at all?? Come on! I don't believe that!

I am testing the new release with my frontend, and the MSX emulation is working flawlessy so far...

The only minor glitches I had are caused by some bad GFX on the title screen of Zanac A.I. when emulated under a MSX1 machine... well, have a look:



...but I am still not sure if the tested ROM is a bad dump, so...


EDIT: Under C-Bios v0.21 for MSX2 the Title screen is displayed properly, while it's still corrupt when I select to run it under C-Bios v0.21 for MSX1 or Philips NMS 8250.

I've seen that garbled logo before. Forgot where

Quote:

Are there any plans to support Yamaha KYBT2 networking (YM8032 chip) ? It can be very useful for diskless Yamaha YIS503IIIR owners with tnt23's msx-link.

No plans, but if we get information (preferably attached to a feature request item in our tracker), it is possible we implement it. But we need software to test it with!



The Zanac thing is a known problem, it exists in our bug tracker since ages. It seems to be caused by some very tricky timing problem, IIRC.

Laserdisk is also an existing feature request.

I was more asking about what *bugs* you found than what features you are missing. I want to know if 0.6.2 is worth to release or if it contains (critical) problems.

Thanks for your feedback, though! Your feature requests are also appreciated, but it was not the reason why I started this thread. You can submit them any time to our feature request tracker on sf.net; please do so if you want to make sure we don't forget about it.

By the way, Cax, please contact by e-mail if you know details about the Yamaha YIS503IIIR; I have an experimental config file for it for openMSX and I'd like you to test it a bit.

I'll post some details here, please comment if something is correct or something is wrong. Both are interesting to hear!

- MSX2
- no memory mapper readback limitation (as in turboR e.g.)
- cassette port
- slot 0-0: basic/bios with SHA1SUM 0f851ee7a1cf79819f61cc89e9948ee72a413802
- slot 1 and 2 are the external slots
- slot 3 is expanded
- slot 3-1 contains the sub ROM (I have no data about mirroring, this requires a 64k slot dump)
- slot 3-1 also contains a CP/M ROM. (How can it be tested?)
- slot 3-2 contains a 128kB memory mapper
- 128kB VRAM on a V9938
- YM2149 PSG
- RTC
- printer port


I also have some comments about the 805, which is similar, but has the following differences:
- slot 3-0: Painter with sha1sum 7fd2a28c4fdaeb140f3c8c8fb90271b1472c97b9
- slot 3-1: diskROM instead of CP/M ROM, WD2793 FDC

So, the sub ROM and BASIC/BIOS ROMs seem to be the same.

Is this correct?

Any info is welcome...!

Quote:

The Zanac thing is a known problem, it exists in our bug tracker since ages. It seems to be caused by some very tricky timing problem, IIRC.

I thought it was something other than timing. blueMSX had the same or similar bug earlier but I can't remember what I did to fix it. I thought it got fixed in openMSX at the same time but looks like I'm wrong. I'll try to remember what I did.

@cax. I'm also interested in the YM8032 chip so if you have any information, I'd be happy to look at it.

@manuel: obsonet is fully supported (at least the ethernet version) in blueMSX, so you can get the code there.