Windows Xp Screensaver 10 Hours
Julian Gladyshev
If you have problems with your PC locking or going to sleep, caffeine will keep it awake. It works by simulating a key-press once every 59 seconds, so your machine thinks you're still working at the keyboard, so won't lock the screen or activate the screensaver.
Caffeine works by simulating an F15 key up event every 59 seconds. Of all the key presses available, F15 is probably the least intrusive (I've never seen a PC keyboard with that key!), and least likely to interfere with your work.
Double-clicking the program icon empties the coffee pot, which is what the icon represents, and temporarily disables the program. Double-clicking it again refills the pot, and will keep your machine awake.
If Windows Media Player is still installed, you can play a video on loop and minimize it (the sample "Wildlife" videos work fine for this). By default, as long as a video is playing, the screen won't lock.
Every six seconds, this quickly toggles numlock on the keyboard, causing Windows to believe that someone is interacting with the keyboard, preventing screen lock. This runs on vanilla windows, you don't need development or scripting tools to use it, just make a text file with .vbs as the extension and double-click it (or place it in your startup items).
You can create an AutoIt script to either continually press an unused key (e.g. make it toggle the num lock, scroll lock), sleep for a minute or so, and repeat. Alternatively, if you use the keyboard a lot, you could make it move the mouse by a pixel or so in any direction.
This script moves mouse cursor by one pixel in the up-left direction and after that returns it back, then sleeps for 9 minutes (540000 milliseconds). When script is running, you can see AutoIt icon in the tray. You can stop it right-clicking this icon and choosing the corresponding option.
To make a script, install AutoIt, right-click in any folder and choose New > AutoIt v3 Script, name it, right-click this new script, choose Edit, paste the code provided above and save. You can even compile it to .exe (again, from context menu) to start, for example, from Windows Scheduler.
UPDATE:Maybe there was some change from the administrator, but this doesn't work for me anymore Now I have to use an autohotkey-script from NBirnel: - this work perfect, because it moves the mouse (without distracting any work)
There is an android app called "Timeout Blocker" that vibrates at an interval and you can put your mouse on it. It says not to use it at work though. =com.isomerprogramming.application.timeoutblocker&hl=en
I am looking for a way to find out why sometimes screensaver is not activated on our Windows 10 1809 VDI (virtual machines). So the question is how Windows is calculating idle time which is taked for starting screensaver? We have a GPO configured to start screensaver after 15min of idle time (User Configuration - Administrative templates - Control Panel - Personalization - Screen saver timeout). It happens (especially when machines have longer uptime) then screen saver is not activated. I found out this nice script -the-session-idle-06350f77
but tested it with active skype call which last more than 15 minutes and during this time I was not touching mouse or keyboard. Script was counting to 15 mins but screensaver was not activated. Why? How skype is preventing it?
This machine was not activating screen saver before 12:00 (mine time is UTC +1) - then I restarted it and now it is working. So I am looking for a clue why it was not activating screen saver before 12:00 Details from report:
Although your mouse and keyboard are idle, Windows knows not to start the screensaver as the application skype is running. Below article mentioned "If an application is running that has a computer-based training (CBT) window open, or has a non-Windows program, such as one run from the MS-DOS prompt, as the foreground application, Windows will not start the screensaver."
Thanks for great answers. I expect that this was some application running in the background which prevents screensaver activation. But how to find out such application ? Here is more info from MS about CBT and screen saver : -us/windows/win32/lwef/screen-saver-library Part of it:
However, Windows does not start the screen saver if any of the following conditions exist:
The windows 95 is known for introducing a couple of classic screensavers including: Maze, Pipes and starfield among others. It looks like DirectX is a collection of multimedia APIs but for this question is really only Direct3D sublibrary.
All of the classic 3D screensavers (3D Maze, 3D Pipes, 3D Flying Objects, 3D Text, and 3D Flower Box) used OpenGL instead of DirectX. This was a virtual necessity for two reasons: (1) the original version of Windows 95 didn't ship with any version of DirectX, and (2) the Direct3D API required hardware acceleration that most PCs of the time wouldn't have had. On the other hand, OpenGL could fall back to software rending if hardware acceleration wasn't available. (In fact, I'm not sure there was any hardware support for OpenGL on Windows 95 when it first came out.)
There were at least some third-party screensavers that used Direct3D, but they were very uncommon. It didn't help that the official Windows screensaver API made it difficult to write a screen saver using Direct3D.
Johnny Castaway narrowly predated a whole swath of innovation in digital companions. Virtual (or desktop) pets grew to have proper gameplay and encompass a lot more than a lonely shipwrecked guy, with the Petz games releasing in 1995, followed by Tamagotchi becoming a massive fad in 1996 and 1997. The web-based Neopets followed. Quasi-spyware Bonzi Buddy, Clippy the Microsoft Office assistant, and The Sims franchise all have roots in the world of virtual pets. Most of them were far more complex than Sierra's, so why was the simpler Johnny Castaway stuck in my head?
After finding my white whale, I discovered that Johnny Castaway was still surprisingly popular. I wanted to install this computing relic again to revisit it, but I figured a 16-bit screensaver released in 1992 had about as much chance of running on my modern 64-bit installation of Windows 10 as poor Johnny did of escaping his island. But fans have figured out a workaround, and Johnny Castaway has a preconfigured install that launches it inside DOSBox and lets you select it as a screensaver, even on 64-bit Windows. They rescued Johnny and then dumped him right back on the same island, but stranded in a more modern sea.
Johnny Castaway stuck with me because my mind was forced into creativity: I imagined a whole game, a whole world, around my shipwrecked pal. I must not be the only one, because the pioneering desktop companion is still alive, in that 64-bit port of the original screensaver, a disassembled version you can run in your browser, and even his very own Team Fortress 2 spray. Technology may have moved on, but Johnny's always right where he should be: on his island, trying to woo a mermaid onto shore for dinner.
Sarah is a contributor for PC Gamer, formerly of TechRadar Gaming. With five years of experience writing freelance for several publications, she's covered every genre imaginable and probably a few she made up. She has a passion for diversity and the way different genres can be sandboxes for creativity and emergent storytelling, and loves worldbuilding. With thousands of hours in League of Legends, Overwatch, Minecraft, and countless survival, strategy, roguelike, and RPG entries, she still finds time for offline hobbies like tabletop RPGs, wargaming, miniatures painting, and hockey."}), " -0-10/js/authorBio.js"); } else console.error('%c FTE ','background: #9306F9; color: #ffffff','no lazy slice hydration function available'); Sarah RichterSocial Links NavigationContributorSarah is a contributor for PC Gamer, formerly of TechRadar Gaming. With five years of experience writing freelance for several publications, she's covered every genre imaginable and probably a few she made up. She has a passion for diversity and the way different genres can be sandboxes for creativity and emergent storytelling, and loves worldbuilding. With thousands of hours in League of Legends, Overwatch, Minecraft, and countless survival, strategy, roguelike, and RPG entries, she still finds time for offline hobbies like tabletop RPGs, wargaming, miniatures painting, and hockey.
One other thing which I also did was starting a notepad and clicking into it. This made the script output the dots into the application rather than overload Windows input buffer (which would have caused the OS to start beeping.)
talk about using the wrong tool for the job, why is powershell even involved, just some excuse not to use a WSH script (I know its tagged a hack and you are a powershell guy, but still) The proper way to do this would be to use the windows api (You can call the native api with autoit, so using a key pressing hack there is even worse)
i tried the same but this is not preventing the screesaver from starting, so i landed on this page, but a keypress is also not good because it writes where the Focus is. Next I tried to consume the pressed key immedialtly but no chance ?
Which version of PowerShell are you using? 3.0, right? If so, see which architecture that is. Chances are that you are on x64 Windows and the assembly only exists for the architecture different from the one that you are using. Try the same code in regular PowerShell and PowerShell x86 and see whether one of these works.
Good update Dara. To be honest I think we got around it with an AutoIT script one of our affiliates came up with. I also stumbled upon this not too long ago as well. This ScrSlayer might help some folks if they find this article.
As soon as the provided time (-Until) is exceeded, the script loop stops and the computer will lock itself dependent on the policy affecting the screen lock/screensaver. If you provide the -Logoff switch (As per second command), the computer will log off for you.
c80f0f1006