
Originally
posted by
Jim Sachs:
Ad_Enuff - for some reason, your system is not recognizing the .scr filetype, and adding the proper program argument (-s in this case). When you double-click on the file, Windows is supposed to interpret it as "[filepath]MA3Beta.scr -s". You say that this is a work computer - is it possible that someone has disabled the screenaver capability on it?

I have tried using the *.scr -s and the screensaver works as it should.
Take away the -s and it stops working. Changing the extention to EXE works as well.
Again due to my Works GD build being rather shabby anyway, I'm unsure if its the build or a genuine bug within the screensaver itself.
Just to confirm, the screensaver on my Home machine (Vista 64Bit) works flawlessly.
AMD Ryzen 5 2600X, 3600.0 MHz, 16Gb DDR4 RAM, NVIDIA GeForce GTX 1050 Ti, 4Gb RAM, Windows 10 PRO 64Bit