Please help testing upcoming openMSX release!

Page 22/57
15 | 16 | 17 | 18 | 19 | 20 | 21 | | 23 | 24 | 25 | 26 | 27

By Manuel

Ascended (17941)

Manuel's picture

16-05-2020, 21:54

Great, thanks!

By donluca

Expert (75)

donluca's picture

16-05-2020, 22:39

Grauw wrote:

Fn+Up and Fn+Down are Page-Up/Down and Fn+Left/Right are Home/End, and they work in openMSX. The other terminal key combinations are indeed also the same, only copy/paste uses CMD.

Isn't CMD+Left Home and CMD+Right End? I always use those to to get to the start or end of the line.
Fn+Left and Fn+Right seem to be the same as Fn+Up and Fn+Down at least here on my Mac Pro with bluetooth Magic Keyboard and Italian layout...

By Grauw

Ascended (9904)

Grauw's picture

16-05-2020, 23:14

So Fn-Left and Right go to the start of the document (like a webpage or pdf). Which also is the function of Home / End as well on Windows. On macOS this is also the case in the terminal history.

However on Windows when a text field has focus, home / end goes to the start / end of the current line. On macOS, this is not the case. There, Cmd-Left/Right has this function.

By Manuel

Ascended (17941)

Manuel's picture

16-05-2020, 23:49

donluca: Which compiler version are you using exactly?

By donluca

Expert (75)

donluca's picture

17-05-2020, 00:24

luca@Cougar ~> cc --version
Apple LLVM version 10.0.0 (clang-1000.11.45.5)
Target: x86_64-apple-darwin17.7.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

By Grauw

Ascended (9904)

Grauw's picture

17-05-2020, 03:06

For me that’s

Apple clang version 11.0.3 (clang-1103.0.32.59)
Target: x86_64-apple-darwin19.4.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

Btw you can also get dev builds from GitHub, and these ones don’t have the caps-lock issue for me.

By Manuel

Ascended (17941)

Manuel's picture

17-05-2020, 11:05

Grauw wrote:
sdsnatcher73 wrote:
Sylvester wrote:

I can confirm the caps blinking bug with the latest build, I also have the same problem on my macbook.

I have it as well, for some time now actually.

Ok, I tried the openMSX build from openmsx.dev, and there I can also reproduce the issue.

I recommend upgrading XCode on the build machines. I’m building with XCode 11.4.1 without issues.

Grauw, in your last post you seem to claim the opposite?? Oh wait GitHub is not openMSX.dev.

By Louthrax

Prophet (2405)

Louthrax's picture

17-05-2020, 11:17

Hi Manuel,

Nothing critical at all, but I noticed that when I start openMSX, I always have randoms checks for various ROMs:

Making dependencies...
Injecting files in ssms.dsk...
Launching ssms.dsk...
..\..\bin\openmsx\openmsx -machine Philips_NMS_8245_4MB -ext slotexpander -ext ram4mb -ext ram4mb -ext ram2mb -ext ram2mb -ext nextoride  -script ..\openmsx.ini -hda "C:\Projects\mdk\projects\ssms\ssms.dsk"
progress: Searching for file with sha1sum cc57c1dcd7249ea9f8e2547244592e7d97308ed0...
Indexing filepool C:/Projects/mdk/bin/openmsx/share/systemroms: [148]: /machines/frael/bruc100_2_firmware1.2.rom
progress: Searching for file with sha1sum cc57c1dcd7249ea9f8e2547244592e7d97308ed0...
Indexing filepool C:/Projects/mdk/bin/openmsx/share/systemroms: [292]: /machines/panasonic/FS-A1WX_IC16.bin
progress: Searching for file with sha1sum d97c9b4e936d999954ac89173d0d69bc7fc88d7b...
Indexing filepool C:/Projects/mdk/bin/openmsx/share/systemroms: [523]: /misc/Keyboard Master Voice ROM (1984) (Konami) (J).rom

The weird thing is that those checks are looking quite random (not always the same ROMs, sometimes only 1, sometimes several...).

I already have this line added in my openmsx.ini file:

set auto_enable_reverse off

which works to disable the hash computation of the HD images I'm using.

I'm using openMSX 0.15.0 (32 bits) on Windows 7.

By Grauw

Ascended (9904)

Grauw's picture

17-05-2020, 12:48

Do you use an antivirus program?

By Manuel

Ascended (17941)

Manuel's picture

17-05-2020, 13:30

Louthrax: this happens if you have a sha1sum in your machine configuration that is not found in the /share/.filecache file. openMSX will then start looking for the file ("indexing") in the file pools that are configured. It reports progress on this indexing once per second or so, showing the current file it was indexing, and how many files it has indexed so far (the number between square brackets).

So, important in this case is the ROMs with sha1sum cc57c1dcd7249ea9f8e2547244592e7d97308ed0 (NMS 8245 EPROM dump) and sha1sum d97c9b4e936d999954ac89173d0d69bc7fc88d7b (unknown to me) . Apparently they were not in the filecache?

For the former case, the standard 8245 has this ROM as first of 4 alternatives. Perhaps you have one of the later mentioned alternatives installed. I think currently openMSX will first try to find the first one (including indexing) and then a later one. Perhaps we should change this behaviour.

To avoid this for now, install the full system ROM set Smile

Page 22/57
15 | 16 | 17 | 18 | 19 | 20 | 21 | | 23 | 24 | 25 | 26 | 27