WinUAE preventing screensaver

[trumpy81]

Since I started using WinUAE 3.6.0 and now WinUAE 3.6.1 it has prevented my Win 10 screensaver from starting up after I have closed WinUAE.

I have disabled the option in WinUAE Host > Miscellaneous > Disable screensaver, but that has no effect in restoring the screensaver after I have run WinUAE.

The only way I can get the screensaver to work again is to reboot windows.

I have checked the ScreenSaveActive registry entry and it is correctly set to 1.

Is there another setting I have missed or ... ??

I should also add, that my monitors do not turn off either, probably because the screensaver does not run.

Any help would be appreciated.

[Toni Wilen]

This does not sound like WinUAE directly causing it because it does not do any global changes and all local changes automatically disappear when program exits.

[Tomislav]

Do you need screensaver? Screensavers are made for CRT monitors. With modern monitors they are unnecessary. Except if you need to lock down your computer.

[-Acid-]

screensavers are still a thing!?

[trumpy81]

Originally Posted by Toni Wilen

This does not sound like WinUAE directly causing it because it does not do any global changes and all local changes automatically disappear when program exits.

I have checked repeatedly and I only have a problem with the screensaver and monitors not turning off after I have run WinUAE.

If I don't run WinUAE then I don't have any issue with the screensaver or monitors turning off.

If you have any ideas what the issue might be, I'm all ears

[Toni Wilen]

Does it happen if you only open GUI?
Does it happen if you run it only in window mode? In fullscreen mode?

DirectDraw/D3D9/D3D11 mode?

[trumpy81]

If I opened the WinUAE properties window at all the SS would stop running afterwards, it was occuring after I ran a VM also. I only run my VM's in windowed mode.

Window style = standard
Graphics API = Direct 3D 11
Graphics API Options = Hardware D3D11

I have Picasso 96 installed using the UAEgfx settings only. Screen size is currently set to 1600x900 32bit.

Of course, I just opened the WinUAE Properties window and let the computer sit with it open and it ran the screensaver and shut off the monitors as it should.

I then started a VM and ran it for a minute or two and then closed WinUAE. The screensaver did not run when expected, but the monitors turned off at the time the screensaver should have started running.

I think something weird is going on here. I have a feeling this may be related to my GFX card somehow or possibly Direct 3D.

I am running the following specs for my PC, if it matters:

Corsair Carbide 400R MidTower Case (modified for SATA access)
Intel Core i7 5930K Haswell-E 3.5GHz 8MB - Running @ 4.3GHz (Stable)
Corsair H80 Liquid CPU Cooler
Asus X99 Rampage V Extreme (BIOS v3801)
G Skill Ripjaws 4 F4-3000C15-4GRR @ 3000MHz x4 16GB Total
Samsung SM951 MZVPV512HDGL-00000 M.2 512GB SSD
Samsung 850 Pro Series 2.5" 256GB SSD
Samsung 830 Pro Series 2.5" 256GB SSD
6x Seagate ST4000VN000 4TB NAS 3.5" Hard Drives
2x Seagate ST6000VN0021 6TB NAS 3.5" Hard Drive
ASUS DRW-24D3ST CD/DVD Burner
Nvidia Geforce GTX 1060
2x Asus VE278Q 27" Monitors
Corsair Vengeance K70 Keyboard
Logitech G502 Mouse
Corsair RM1000 1000w Modular Power Supply
Microsoft Windows 10 Professional 64bit (UEFI Mode On)

[Foebane]

Originally Posted by Tomislav

Do you need screensaver? Screensavers are made for CRT monitors. With modern monitors they are unnecessary. Except if you need to lock down your computer.

Originally Posted by -Acid-

screensavers are still a thing!?

I was going to post the same thing, but I figured I would be seen as unhelpful.

Then again, I've seen screensavers that actually worsened the problem with CRT displays, like Disney ones which burn "© Disney" into the screen because they're always there, in direct violation of the principle of a screensaver. D'oh!