Eightyone freezes whenever my Pc goes into screensaver mode

[Crayon21]

how do I fix this? It won't respond to anything and I often have to redo type ins due to having to reset. any help? I'm running windows 10 build: 19045
latest install: KB5053606

[Moggy]

Unless you're running a desktop/tower PC along with a cathode tube TV/monitor, screensavers are unnecessary so the simple answer is to disable the screensaver.

[1024MAK]

I haven’t used a "screen saver" on a modern PC since, err, ever! Yes, I had a screen saver on my Pentium system that ran Windows Windows 95.

On my newest laptop, which is running Windows 10 (version 10.0.19045 build 19045) there is no problem with it going into and out of standby or hibernation.

Mark

[stroebeljc]

Which screensaver?

[Crayon21]

Which screensaver?

when I leave it idle, it goes to my password screen and shuts off the monitor

[Exile]

I can reproduce this very easily on Windows 10.

With EO 1.4.1 I created a simple program

Code: Select all

10 PRINT "*";
20 GOTO 10

When the code was running I pressed control-alt-delete and selected the lock screen (aka password screen). I then entered my password to exit the lock screen. When my desktop was redrawn EO had crashed - the attached screen shot shows the error dialog box.

Sometimes after clicking "OK" a few times the dialog went away. At that point EO displayed the following:

The fact that the program ran until the screen was full makes me think that the crash occurs when the PC leaves the lock screen, rather than when the PC enters the lock screen

I got a similar crash when I tried with EO 1.40.

[stroebeljc]

I am unable to reproduce the issue on my Windows 10 PC with the KB5053606 update. Has this issue always been present on Windows 10, or has it only occurred since the latest Windows update?

[1024MAK]

The version of EightOne that I am using is 1.38

This is running on Windows 10 (version 10.0.19045 build 19045) 22H2 KB5053606.

I have noticed that if I run this program:

Code: Select all

  10 FOR A=1 TO (21*32)
  20 PRINT "*";
  30 NEXT A
  40 CLS 
  50 GOTO 10

Then go to the lock screen as described by Exile, then when I unlocked, EightOne continued running.

After breaking into the program by pressing Space, pressing Return (New Line) just alternates between a K cursor and a F cursor. Unless I use a letter key or press Space again, then Return (New Line) works as normal.

I'll try using EightOne 1.41 later.

Mark

[1024MAK]

I'll try using EightOne 1.41 later.

I get similar results with EightOne 1.41 except the keyboard behaviour is worse. After getting the cursor changing as I describe above, pressing space gets me £ symbols instead...

Mark

[stroebeljc]

I get similar results with EightOne 1.41 except the keyboard behaviour is worse. After getting the cursor changing as I describe above, pressing space gets me £ symbols instead...

It's acting like the shift key is pressed. Does pressing one of the shift keys before any other key fix the problem?