Finally have a feature request for openMSX :) | MSX Resource Center (Pagina 4/5)

Ambassador (5672)

09-03-2013, 12:38

Manuel wrote:

JohnHassink: the OSD menu of course The one you open with the MENU key on your keyboard, usually left of your RIGHT CTRL key. This OSD menu contains a sub-menu called "hardware" where you can plug in and remove extensions.

Oh LOL, I'm so thick sometimes.
Thanks. I must say that in Catapult, it's more easy to view.

Van Manuel

Ascended (19466)

09-03-2013, 13:18

tvalenca: what kind of Macs do you use and which OS X version?

Van tvalenca

Paladin (747)

09-03-2013, 13:44

I mainly use a Mac Mini 3,1 Intel Core2Duo with OSX Lion, and a MacBook Pro Intel core2duo with Snow Leopard.

Van mars2000you

Enlighted (6482)

09-03-2013, 14:18

@tvalenca, you can maybe also try CocoaMSX :

http://code.google.com/p/cocoa-msx/

Van tvalenca

Paladin (747)

09-03-2013, 15:11

I tried once, but I could not find it's debugger..

Van mars2000you

Enlighted (6482)

09-03-2013, 15:41

CocoaMSX is a very new emulator for Mac (although it's based on blueMSX), I guess that a debugger will be added in a future version.

Van Manuel

Ascended (19466)

09-03-2013, 16:44

tvalenca: there is a GUI debugger, but I don't think anyone ever tried to compile it for Mac... Only for Windows and Linux.

What kind of crash do you get? Can you give some information?

Van tvalenca

Paladin (747)

09-03-2013, 16:56

Mars2000you: I hope that it happen soon!

Manuel: I'll post a detailed log when I get home!

Van wouter_

Hero (522)

09-03-2013, 18:16

bluemsx wrote:

I've checked TC8566AF FDC emulation of openMSX.
I think openMSX emulates TC8566AF FDC with combined method.

I've fixed this in revision 13192. Compared to blueMSX, openMSX will now also return the correct values when reading memory locations 0x7ffc-0x7fff on a turboR machine.
It's likely that none of these changes will make any difference for 'normal' emulation (I mean for anything except for a specific test program). But it's nice to get these details right.
@bluemsx: thanks for reporting this bug.

Van bluemsx

Resident (44)

10-03-2013, 10:15

wouter_ wrote:

bluemsx wrote:

I've checked TC8566AF FDC emulation of openMSX.
I think openMSX emulates TC8566AF FDC with combined method.

I've fixed this in revision 13192. Compared to blueMSX, openMSX will now also return the correct values when reading memory locations 0x7ffc-0x7fff on a turboR machine.
It's likely that none of these changes will make any difference for 'normal' emulation (I mean for anything except for a specific test program). But it's nice to get these details right.
@bluemsx: thanks for reporting this bug.

Thanks.
According to FS-A1FX/WX/WSX/ST/GT, PHC-70FD/70FD2, memory I/O (7FFC-7FFF) is shown as "FC FC FF 3F".
This is also mirrored to (BFFC-BFFF)
If openMSX doesn't want to this memory mapped I/O value "FC FF FC 3F" from 7FFC-7FFF and BFFC-BFFF,
all of disk basic kernel and MSXDOS 2.3x kernel must be redumped!

Which is the best solution?

If you dump Slot 3-2 with SAVEROM.COM on real MSX2+/MSXturboR machine, you can see the "FC FC FF 3F" via "7FFC-7FFF" and "BFFC-BFFF (mirrored)"

on Bluemsx emulator, I re-dumped all of MSX2+/MSXturboR disk kernal ROMs based on TC8856 with memory mapped I/O value "FC FF FC 3F".

If you impement to add Memory Mapped I/O "FC FF FC 3F", there is no need to replace rom.
But if not possible or wanted, rom must be replaced.