Screen resolution setting.

I dug out an I3 Probook and rpcemu runs much better on there once compiled. (0.9.1). Than it it did under Virtual Box. (Due to terrible Mouse performance in Virtual Box)

Equally, the native OSX version had awful mouse problems despite a very modern Mac Book Pro.

The screen resolution of this laptop is 1366 × 768.

If I click full screen in settings, the menu bar sticks to the top of the screen and I can’t see the Riscos tool bar.
800 X 600 is OK.

I seem to remember that there is a file somewhere in !Boot that I can store precise screen res settings so that I can max out my screen use. I can’t find the file.

I am on RO3.7 and everything seems to work OK.

I seem to remember that there is a file somewhere in !Boot that I can store precise screen res settings

!Boot.Resources.Configure.Monitors.<monitor-name>

The format of an entry should be pretty easy to determine. Each mode needs a mode name if you want it to appear on the menu (so you would be creating a mode named “1366 × 768”). As you’re using an emulator you don’t need put proper values in the pixel_rate, h_timings or v_timings entries (but the entries do need to exist).

I suggest you create a new file containing your settings and put it in the “Monitors” directory. A suitable monitor title would be “RPCEmu” and you only need to mention the modes you will actually be using (but you should keep the “640 × 480” and “800 × 600” modes just in case).

But beware: due to some limitations in RISC OS, you’ll need to use 1360×768 and not 1366×768.

you don’t need put proper values in the pixel_rate, h_timings or v_timings entries

However I found that setting ‘Sync_pol:3’ as a final value* was essential to avoid ‘this mode is unsuitable’ error messages. The easiest procedure IMHO is to copy an existing similar mode (which is known to work) from the Configure.Monitors./current mode file/, edit the x and y values and the sync_pol values as required, name it and paste it back into the current mode file. On rebooting the new mode should be visible amongst the resolution options in Configure-Screen-/current mode file/.

[*no idea why – this is purely the result of empirical testing on my system]

You can drag a mode file onto the display manager to temporarily test it, without needing to reboot.

I found that setting ‘Sync_pol:3’ as a final value* was essential

Correction: it’s not (I was mistaken). I’ve since successfully set up a Sync_Pol:0 MDF, so it looks as if this parameter is not critical after all.