You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when using NVDI, setting all SCREEN.SYS entries in ASSIGN.SYS without 'p' (i.e. 01 SCREEN.SYS) makes XaAES fail with an v_openvwk error (and reboot) (actually this bombs also in plain TOS so not really a bug)
when using NVDI and SuperVidel's ASSIGN.SYS (i.e. all entries look like 01 SVCREEN.SYS) I'm getting memory violation when launching any GEM app (QED for instance) if and only ifvideo = xx is specified (for instance "video = 27" but also any SV resolution); without "video = xx" everything works fine
it seems that XaAES can't start without "video = " set to some (reasonable) value. At least on my Falcon booting in 640x480@2 colours I'm getting video init errors and reboot. Strangely, it works if NVRAM boot resolution is set to 640x480@256 colours. (see also XaAES terminates with NVDI in default/current resolution #159)
The text was updated successfully, but these errors were encountered:
After a very painful investigation I've collected following issues / unexplained behaviour related to XaAES video settings:
for some reason XaAES refuses to launch in RGBwhen using NVDI, setting all SCREEN.SYS entries in ASSIGN.SYS without 'p' (i.e. 01 SCREEN.SYS) makes XaAES fail with an(actually this bombs also in plain TOS so not really a bug)v_openvwk
error (and reboot)video = xx
is specified (for instance "video = 27" but also any SV resolution); without "video = xx" everything works fineit seems that XaAES can't start without "video = " set to some (reasonable) value. At least on my Falcon booting in 640x480@2 colours I'm getting video init errors and reboot. Strangely, it works if NVRAM boot resolution is set to 640x480@256 colours. (see also XaAES terminates with NVDI in default/current resolution #159)The text was updated successfully, but these errors were encountered: