Stuff

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
===== How MYASS Works =====
{{:myass:myass.gif?nolink&200|}}

[[myass:index|Welcome to MYASS]] | [[myass:faq|F.A.Q.]] | [[myass:inside|]] | [[myass:plugins|]]

Getting **MYASS** Started

Getting **MYASS** going is easy! With an intuitive interface setup is simple, and should only take a few minutes for anyone, even if you have no previous experience with **MYASS** or any other piece of software.

Initially Inputting into **MYASS**

The thought of putting something into a system as complex as **MYASS** can seem devastating to start with. Don't be fooled though, getting into **MYASS** is easy, and fun (once you get comfortable and start to explore).

Pre-existing handlers allow you to begin quickly and easily, accessing and inputting into **MYASS** almost immediately. **MYASS** is fully customizable, and can be modified easily to reflect foreign character sets, or allow for personal profiles, users and group privileges. As well, **MYASS** has the all the administrative backdoor functions and features that integrators and developers love to use.

Fail safes inside the **MYASS** Kernel monitors data frequently to insure the proper distribution of every bit and byte inside **MYASS**, which requires proper traffic within the storage capacity of **MYASS** and your hardware capacity. This allows load balancing for managing and allocating system resources efficiently in case of power surges, lock-ups, or occasionally brown outs that can exist in unstable circumstances. This makes it easy to access and to be quickly removed from the system if necessary.

Primary Output

Once loaded up with data the G-string code is applied which confines **MYASS**, and triggers a query that collects all the important bits of information in the system. Then **MYASS** creates long but compact logs that automatically backup inside the system. Once the capacity of the system has reached its limits **MYASS** is safeguarded by beginning to notifying users of a possible random I/O malfunction. Logs can be exported from **MYASS** in succession, partial, complete, or discrete loads, never altering the original kernel.

Hardware Requirements

Although there are no minimum system requirements to run **MYASS**, it thrives in any environment that supports multifunction devices, and multi-port adapters. **MYASS** is platform independent, and has a small memory footprint, while taking up only a small portion of the perimeter of a hard disk. What is hard to believe is that **MYASS** has so much in store for you, and **MYASS** can take in more than you would ever think could go in there.