Skip to content
This repository has been archived by the owner on May 1, 2024. It is now read-only.

Settings

Nicholas "Tiger" Gautier edited this page Apr 16, 2016 · 3 revisions

Bootless Star has a very configurable environment that modules can take full advantage of and utilize.

Table of Contents

Copy Settings

Bootless Star accepts only two major copy extCMD's, XCOPY and ROBOCOPY. There maybe times when modules will simply over-ride this setting.

  • XCOPY
    • Default
    • This extCMD focuses primarily on data and the hierarchy setup.
  • ROBOCOPY
    • This extCMD is a very robust version of XCOPY, but is mainly intended for large scale operations.
    • In order to use this extCMD, Bootless Star must have Administrative Rights. Without this permission, this extCMD will never execute any instructions.

Directory Setup

Because modules may need extCMD's or specialized software to perform their tasks, Bootless Star tries to simplify the user's life by trying to automatically detecting what is available on the host system and sharing that information with modules. Doing this, will allow the user to focus more on what tasks has to be performed as opposed to trying to set up each session. In addition, you do NOT need to have all of the programs or maybe none at all. Please check the module documentation as to what the module requires.

If incase a program was not detected automatically but infact is installed on the host system, the user can reconfigure the directories.

Terminal Sounds

When a notification or a critical message appears on the terminal, modules can alert the end-user. The notification is merely invoking the BEL character, which - on modern Windows systems, that would output a 'beep' noise to the default output audio.

  • Notify for all notifications
    • Default
  • Notify only for errors
  • Disable
    • No sound

Log settings

Bootless Star allows logging by merely taking the STDOUT and redirecting it to a simple log-file on the filesystem instead of the terminal buffer. However, during operations, this may cause issues with performance because of the needing I/O time with the secondary storage.

  • Disable logging
    • Default
  • Enable logging