Screen opening woes in OS4.1FEu1 Classic

	Bottom Previous Topic Next Topic
Register To Post

« 1 (2)

broadblues

Re: Screen opening woes in OS4.1FEu1 Classic

Posted on: 2018/3/5 12:42 #21

Home away from home

@BSzili

Quote:

Yes, I have the Multiscan monitor in devs:monitors on OS3.1.

So if you choose a MultiScan mode for something (eg workbench) does it display correcttly? That would eliminate emulation bug.

If yes, then chack how your settings might vary between the emulations for 3.x snd OS4

Quote:

On OS4 I don't have the PAL monitor in there just PicassoIV, but the native PAL modes work fine, I'm only had issues with Multiscan one.

Because the multiscane / VGA modes are added in the kickstart they would be eariler in the database than if they were added after boot up via DevS:Monitors, this is the main reason they are getting chosen in preference to the native or RTG clut modes.

Quote:

I'll copy my 3.1 setup onto an RDB hardfile to see what it does on the same UAE config.

Ah, is your 3.1 setup on real hardware then?

Blender For OS4.x : Blues : Walker Broad

BSzili

Re: Screen opening woes in OS4.1FEu1 Classic

Posted on: 2018/3/5 13:14 #22

Quite a regular

@broadblues
The Multiscan mode is broken in the ScreenMode prefs test as well. I guess the only way to make sure it's not an emulator problem is to use the very same winuae config with OS3.1. I have it in WinUAE, it's just that it's not on proper RDB hardfile, so it only work with uaehf.device and not the emulated IDE controller.

edit: I tested it, and on the very same UAE config Multiscan works under OS3.1 but not under OS4.1FE.

Edited by BSzili on 2018/3/5 14:13:01

This is just like television, only you can see much further.

Register To Post	« 1 (2)
	Top Previous Topic Next Topic

Currently Active Users Viewing This Thread: 3 ( 0 members and 3 Anonymous Users )