Wanted: feedback from Mac OS X users

Page 3/18
1 | 2 | | 4 | 5 | 6 | 7 | 8

By anonymous

incognito ergo sum (116)

anonymous's picture

05-11-2013, 14:22

mth wrote:
sd_snatcher wrote:

- There's still no way to produce the MSX [INSERT] key on the Apple keyboards without numpad, which are shipped as the standard for the majority of Macs today.

We need a key though to assign INSERT to. Maybe the §/± key? Although that key inserts the right symbols in openMSX, I doubt many people will need to type § or ± in MSX programs.

As you can see on:

Belgian/Flemish keyboards for instance don't have such a key. (Well, § is available as Shift+6, but I don't see ± at all)
Same goes for English and French. Using 'special' characters such as §/± for it is rather risky imho. Can't it be bound to a normal letter combination like CMD+i instead?

By Manuel

Ascended (18162)

Manuel's picture

05-11-2013, 15:15

mth wrote:
sd_snatcher wrote:

- save_msx_screen should save its files inside the ~/.openMSX/screenshots folder. On 0.8.1 it saved inside ~/.openMSX. In 0.9.1-619-ge97f702 it results in error: couldn’t open “kv22.SC5”: permission denied.

It works fine when I test it: it saves the screenshot as ".openMSX/screenshots/Zanac-Ex 0001.png".

Any idea where that ".SC5" comes from? openMSX screenshots are always PNG files.

mth, he didn't use the screenshot command here, but from a script the command save_msx_screen. That command saves the screen in MSX format.

By mth

Champion (500)

mth's picture

05-11-2013, 15:41

FiXato wrote:

Using 'special' characters such as §/± for it is rather risky imho. Can't it be bound to a normal letter combination like CMD+i instead?

Since there doesn't seem to be a free non-combo key, that's probably the only way.

By mth

Champion (500)

mth's picture

05-11-2013, 15:47

Manuel wrote:

mth, he didn't use the screenshot command here, but from a script the command save_msx_screen. That command saves the screen in MSX format.

I didn't know that command exists Smile Indeed he wrote that.

It seems the save_msx_screen command saves in the current working directory, so I think this is a generic bug, not an OS X specific one. But it is undesired, since the working directory might not be easy to find or not even writable (as was the case for sd_snatcher).

By Manuel

Ascended (18162)

Manuel's picture

05-11-2013, 22:00

OK, save_msx_screen command fixed in git. It saves to the screenshots folder now.

sd_snatcher: can you try the file associations again? It may have to do with a first run or something.
Also, I'm still very interested in feedback from KV2 on real machines.

By sd_snatcher

Prophet (3473)

sd_snatcher's picture

06-11-2013, 00:43

Ok, just did a quick test.

1) Right-click on ALESTE.ROM->open with->openMSX: no luck
2) Right-click on ALESTE22.DSK->open with->openMSX: no luck

About the KV2 tape test, plz wait a bit more. I already went downtown and bought the necessary components. But building the cable will require quite more free time (and concentration) than I have available right now.

Another quick test revealed another problem: Turbo Z80 MSX models are now broken. Both Panasonic MSX2+ models and the CIEL ExpertTurbo get corrupted images when their turbo modes are enabled.

- For the ExpertTurbo, the V9958 WAIT signal emulation seems to be missing
- For the Panasonic MSX2+ machines probably there's some sort of I/O slowdown provided by the chipset that isn't being emulated.

Also, I notice that the Built-in On-Screen-Display menu can load FDD images, ROMs and tapes, but cannot load HDD images.

By Manuel

Ascended (18162)

Manuel's picture

06-11-2013, 09:33

About the Turbo stuff: how can this be tested? When did it still work? (Note that we did not remove any wait stuff or I/O slowdown... so it may have been sheer luck that it worked before... If you tell me how to test this myself, I'll try to find out when it broke.)

The OSD menu offers a selection of the most used/important functionality. We didn't consider changing harddisk images being amongst that... that's why it's not in. Of course you can still use the IDE extension with the default harddisk image (via the hardware menu).

By wouter_

Champion (467)

wouter_'s picture

06-11-2013, 11:52

Manuel wrote:

About the Turbo stuff: how can this be tested? When did it still work? (Note that we did not remove any wait stuff or I/O slowdown...

This is likely because we now emulate the behavior of too fast VDP I/O. When the Z80 is running at 3.5MHz this rarely occurs. But apparently when the Z80 runs much faster it's more common.

Probably the real Turbo-Z80 machines have some extra circuit that inserts wait states (or temporary switches back to a lower clock freq?) when accessing the VDP (just like on a turboR machine the R800 is automatically slowed down when accessing the VDP too fast). That extra circuit is not yet emulated.

@sd_snatcher: Do you have (detailed) info on such delay circuits? Are there circuit diagrams available of the 'Turbo-Z80' machines?

By sd_snatcher

Prophet (3473)

sd_snatcher's picture

06-11-2013, 12:27

Manuel,

To test it, create a disk containing MSX-DOS1, Fudeba Turbo Changer, and GAMEBOOT.COM (the same used for Turbo-R)

After booting MSX-DOS, type:

A:> TURBO ON

To enable the turbo, and:

A:> GAMEBOOT

To boot any disk game you want to test. After it asks for the game disk to be inserted, just swap the disks using the openMSX console.

If you can't find GAMEBOOT.COM, the alternative is to just type:

A:> BASIC

CALL SYSTEM

By sd_snatcher

Prophet (3473)

sd_snatcher's picture

06-11-2013, 12:52

@wouter_

Yes, this indeed seems related to the new VDP I/O engine.

In the CIEL Expert turbo, it's implemented in a simple and straightforward way: The V9958's /WAIT pin is connected to the Z80 /WAIT pin. This means that the VDP itself manages the correct I/O timing for VRAM operations by generating any necessary waitstates. This way all I/O can be done at 7Mhz without trouble.

In the Panasonic MSX2+ machines, there's a custom chipset that controls the CPU speed. I don't have any other details than to say that this chip seems to do it based in the VBLANK/HBLANK areas, because this chip receives such signals from the VDP. There's a scan of this page from the WSX service manual around in the Net.

EDIT:

The WSX service manual scanned page can be found at the MSXpro website.

Page 3/18
1 | 2 | | 4 | 5 | 6 | 7 | 8