Aptivi - Manual
ProjectsWebsiteBlog
Nitrocid KS v0.1.0 - Rolling Manual
Nitrocid KS v0.1.0 - Rolling Manual
  • Welcome!
  • Version Release Notes
  • Installation and Maintenance
    • Installing the Kernel
      • Windows
      • macOS
      • Linux
      • Android
    • Upgrading the Kernel
      • Windows
      • macOS
      • Linux
      • Android
    • Dependency Information
  • Fundamentals
    • What is the Kernel?
    • What is Nitrocid KS?
    • Simulated Kernel Features
      • Extra Features
        • More Networking
          • FTP Client
          • SFTP Client
          • RSS Client
          • HTTP Client
          • Mail Client
        • Games and Amusements
          • Hangman
          • BackRace
          • Meteor
          • Russian Roulette
          • ShipDuet
          • Snaker
          • Solver
          • SpeedPress
          • Wordle
        • More Editors
          • JSON Editor
          • SQL Editor
        • Common Programs
          • Archive
          • Caffeine
          • Calendar
          • Calculator
          • Contacts
          • Dictionary
          • Git Shell
          • Music Player
          • Notes
          • SSH Connection
          • Timers
          • To-do List
          • Unit Converter
          • Weather
        • Docking
        • Language Studio
        • Theme Studio
      • Accounts
        • Groups
        • Permissions
      • Editors
        • Text Editor
        • Hex Editor
      • Shells
        • Commands List
        • Addon Commands List
      • Files and Folders
        • Hashing and Encryption
      • Networking
      • Languages
      • Screensavers
  • Advanced and Power Users
    • Building the Kernel
      • Building on Windows
      • Building on macOS
      • Building on Linux
      • Building on Android
    • Kernel Modifications
      • Building your Mod
      • Analyzing your Mod
        • Text - NKS0001
        • ConsoleBase - NKS0002
        • ConsoleBase - NKS0003
        • ConsoleBase - NKS0004
        • ConsoleBase - NKS0005
        • ConsoleBase - NKS0006
        • ConsoleBase - NKS0007
        • ConsoleBase - NKS0008
        • ConsoleBase - NKS0009
        • Files - NKS0010
        • Files - NKS0011
        • Files - NKS0012
        • Files - NKS0013
        • Files - NKS0014
        • Files - NKS0015
        • Files - NKS0016
        • Files - NKS0017
        • Files - NKS0018
        • Files - NKS0019
        • Files - NKS0020
        • Files - NKS0021
        • Files - NKS0022
        • Files - NKS0023
        • Kernel - NKS0024
        • Kernel - NKS0025
        • Kernel - NKS0026
        • Kernel - NKS0027
        • Kernel - NKS0031
        • Kernel - NKS0032
        • Kernel - NKS0033
        • Kernel - NKS0037
        • Kernel - NKS0038
        • Kernel - NKS0039
        • Kernel - NKS0040
        • Kernel - NKS0041
        • Kernel - NKS0042
        • Kernel - NKS0043
        • Kernel - NKS0052
        • Kernel - NKS0053
        • Languages - NKS0044
        • Languages - NKS0045
        • Languages - NKS0046
        • Network - NKS0051
        • Text - NKS0047
        • Text - NKS0048
        • Text - NKS0049
        • Text - NKS0050
        • Text - NKS0054
        • Text - NKS0055
      • Managing your Mod
        • Inter-Mod Communication
        • Inter-Addon Communication
    • Diagnostics
      • Debugging
        • Local Debugging
        • Remote Debugging
      • Testing
      • Other Diagnostics
    • Inner Workings
      • Kernel Settings
        • Mechanics of Settings App
        • Settings Format
        • Custom Settings
      • Shell Structure
        • Help System
        • Command Parsing
        • Command Information
        • Command Switch Management
        • Command Switch Information
        • Shell History
        • Shell Scripting
        • Shell Presets
        • Extra Shell Features
      • Multilingual Kernel
        • Custom Languages
      • Inner Essentials
        • Kernel Drivers
          • Console Drivers
          • Debug Logger Drivers
          • Encoding Drivers
          • Encryption Drivers
          • Filesystem Drivers
          • Hardware Prober Drivers
          • Input Drivers
          • Network Drivers
          • RNG Drivers
          • Regular Expression Drivers
          • Sorting Drivers
        • Kernel Placeholders
        • The Permissions
        • The Users
        • Kernel Threads
        • Kernel Arguments
        • Kernel Journaling
        • Remote Procedure
        • Nitrocid Filesystem
        • Screensaver Internals
        • Splash Internals
        • Kernel Platform
        • Theme Internals
        • Color Internals
        • Privacy Consents
        • System Notifications
        • MAL and MOTD
        • Progress Handlers
        • Assembly Signing
        • Assembly Reflection
        • Random Number Generation
        • Network Tools
        • Date and Time
        • Mod Manual Pages
      • Miscellaneous APIs
  • Project Dependencies
  • Report an issue
  • Source code
  • API Reference
Powered by GitBook
On this page
  • Setting the screensaver
  • Saving your screen
  • Locking your screen
  • Reloading your custom screensaver
Edit on GitHub
  1. Fundamentals
  2. Simulated Kernel Features

Screensavers

Screensavers and their usage

Last updated 7 months ago

The screensavers were touted to be a solution against screen burn-ins in cathode ray-tube (CRT) or plasma displays. They fill the screens with either the blank screen or moving image or parts across the entire screen. They also are placed as a security measure so that when screensavers exit, the user will be required to input the password to be able to use your computer again.

The first screensaver that blanked the screen after three minutes of inactivity on the original IBM PCs, scrnsave, was created on 1983 by John Socha. Since then, improvements were made to make modern screensavers than just blanking the screen, to the point that the screensavers earned 3D support in modern times.

The simulated kernel attempts to simulate this functionality in its complete state. You can even customize most built-in screensavers using the built-in settings application found in the kernel, though you have to pass the -saver switch to it.

Some of the screensavers bundled with the addons, such as ExcaliBeats and KSX 2, and some of your custom screensavers may contain fast-paced animations and flashing colors, which may cause seizures for the photosensitive.

Before attempting to set your kernel screensaver default to such screensaver, if you are allergic to such animations, you must seek professional medical specialists found in your local region for guidance.

If you don't want to be warned of this everytime you run such screensaver, you can turn this warning off by opening the kernel settings and turning on the Acknowledge the photosensitive seizure warning option from the Screensaver settings section.

Please note that the random screensaver will not emit this warning, despite having this option turned off.

Setting the screensaver

Extra screensavers are bundled as a screensaver pack addon.

To set the screensaver to your favorite screensaver, use the setsaver command. Since this command is an administrative command, you either need to use an administrator account or use an account that has been granted the administrative command permissions.

  1. Log-in to the system account, root, or any of the administrators or users that has at least the strict command running permissions

  2. Execute the setsaver command to set the default kernel screensaver

    • The full usage of the setsaver command is setsaver <(CustomSaverName)/saver>

  3. Lock or save your screen using savescreen or lockscreen.

Note that your account must have either the administrative permissions enabled or the strict command running permission granted to be able to use this command.

Saving your screen

To save your screen using your default screensaver or any other screensaver, you need to use the savescreen command to launch the screensaver.

Locking your screen

To lock your screen in the simulated kernel, you need to use the lockscreen command to launch the screensaver. Once you press any key, you need to enter your user password before you're able to access the shell again.

As of 0.1.0 Beta 3, you can enable or disable automatic screen locking by going to the kernel settings > Screensaver and enabling or disabling the Enable Screensaver Timeout setting.

If you have this option enabled, you can set the timeout in the format of DDD.HH:MM:SS.NNN, or HH:MM:SS in the simplest form.

Reloading your custom screensaver

To reload your custom screensaver, you need to reload the mod that registered your screensaver.

  1. Execute the modman reload <modName> command to re-register your custom screensaver (if the mod registers that screensaver upon starting up)

  2. Save your screen using savescreen [CustomSaver].

Note that your account must have either the administrative permissions enabled or the strict command running permission granted to be able to use this command.