Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XaAES 'video = xx' issues #41

Open
mikrosk opened this issue May 24, 2017 · 1 comment
Open

XaAES 'video = xx' issues #41

mikrosk opened this issue May 24, 2017 · 1 comment

Comments

@mikrosk
Copy link
Member

mikrosk commented May 24, 2017

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 RGB
  • 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 if video = 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)
@mikrosk
Copy link
Member Author

mikrosk commented Mar 30, 2019

Added fourth issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant