Eightyone freezes whenever my Pc goes into screensaver mode

[1024MAK]

Hi John, yes, that's what I was thinking.

I only had time to try it once earlier today. I'll experiment a bit more later...

Mark

[Exile]

I tried EO 1.41 on 3 separate computers:
1) Windows 10 with an Intel GPU,
2) Windows 11 with an Intel GPU and
3) Windows 10 with an NVidia GPU.

On (1) and (2) (i.e. the computers with intel GPUs) I could get an access violation error similar to the one I described yesterday - but only when DirectDraw was enabled. I could not get an access violation when GDI was selected.

I can reproduce the F / K issue on all computers. I wonder if that is because the control key is detected by EO as part of the control alt delete?

I did also manage to get an access violation error on the NVidia PC, whilst trying to save a program.

Overall, it does smell a bit like memory corruption is occurring.

[Crayon21]

any fix?

[1024MAK]

Okay, when I get the F cursor, yes, pressing a shift key does sort out the problem.

Just now, it's not always suffering from this symptom.

All tests were done with BASIC program I listed earlier, running.

Processor Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz, 2701 Mhz, 2 Core(s), 4 Logical Processor(s)

Being a laptop, it has built-in graphics:
Name Intel(R) HD Graphics 620
PNP Device ID PCI\VEN_8086&DEV_5916&SUBSYS_832A103C&REV_02\3&11583659&2&10
Adapter Type Intel(R) HD Graphics Family, Intel Corporation compatible
Adapter Description Intel(R) HD Graphics 620
Adapter RAM 1.00 GB (1,073,741,824 bytes)

The only other modern Windows system I run, is on my older laptop. Everything else is either Linux or a much older version of Windows.

Mark

[stroebeljc]

Thanks, Exile, for the DirectDraw clue. Now I am able to reproduce the lock screen issue.
Has anyone seen the exception error while in GDI mode?

[Exile]

Okay, when I get the F cursor, yes, pressing a shift key does sort out the problem.

I think EO takes a control key press as shift enter? Therefore I suspect the F cursor is sometimes being generated as a side effect of pressing control alt delete. It will depend on how much earlier control is pressed compared to alt and delete. One way to test this theory is to avoid pressing control, by going to the lock screen via "Windows Key" + L.

any fix?

Press F5 to see the display settings dialog. If the Renderer is set to DirectDraw, then set to GDI. If it is set to GDI already, then please let us know.

[stroebeljc]

The stuck key issue will be fixed in the next release.