User Design-able Operative System Files

I Was Making A User Designable/Data Protection Operative System, I Am Tired Of Making It And I Do Not Even Know If It Is A Good Idea, So I Decided To Associate To Know If It Is A Good Idea And Finish It.

Join To Discuss The Main Ideas For Project.

(Enterprises Or People Who Want To Participate In This Project And Have Own Projects Can Join Them To This Project And Pay For Services With Their Participation Instead Of Money). 

By Joining To This Project, All Participants Are Acceding To The  SourceForge.net Terms Of Use And To These Ones: 

Do Not Join Just For Taking Any Of The Ideas And Leave.

Do Not Publish Or Comment Any Idea From This Project To Other People, Enterprises Or Wathever Is Not Part Of This Project. 

If You Join, We Shall Send Messages To Tell You About New Things To Do And You Must Contribute. If You Have An Own Project Registered In This Project, You Can Use The Things You Have Done And What Others Have Done In Your Own Project. 

What I Need Is: 

(This Will Be Discussed At Applications Design Process). 

						          Full Time Processes: 

Codes: People With Binary, Hexadecimal, Octagesimal, Unicode, Ascii, Etc. Knowledge.  

Java Or/And Other Programming Languages Programmers For Write Source Codes (Web/Network Programmers, Multi Media Programmers, Etc.

						Temporal:

Bios: Bootloaders And Bios Programmers, 

Graphics: Graphics Designers. 

Animation: Animation Designers. 

Passwords And Codes Generators Designers.

Patent:Give Temporal Free Service To People In Change Of A Patent, Copyrights, Trademarks, Etc.


						Services: 
						
E-Commerce: Bank Encrypted Accounts, User Encrypted Control (Transactions, Check Out, Etc.), Products Selling Accounts: Confirmed Details, Legal Proceedment, 

Apply Project Design To: 

Web Protection: Apply Project Structure To Web Sites, Chat, Network (E-Commerce And Stuff) , Etc..

Media Players/Managers: Apply Project Structure To Them.

Marketing: Enterprises Joined To The Project (Service), Can Get A Paid Publicity Service.

Make Thy Own Application: Pre-Made Software Components And Commands To Let Users Mix Them For Making Own Applications. 



The Idea Is To Create An Enterprise With Departments (Services Department, Web Department, Marketing Department, Make Your Own Application Department, Etc.


						This Is The Thematic: 

Mayan View Of The Universe.

Drive = X, Rivers, City With Houses, House Of The Lords, Levels: Blood = Analysis, Pus = Desinfection, Metnal = Deletion, 

Rivers: Blood = Essence Logs, Pus = Desinfection Logs, 

Houses: Access, 

Urls Structure = Rivers (For Despite),  9 Levels Of Xibalba, Maniqueens (False), 6 Houses(Access Tests For Each Kind Of…), House Of The Lords (O.S.), 
City And Gardens (Data Storage), 



						Project Description:

The Idea Is To Create A Bootloader To Run In Bios With The Code Of Whole Operative System (Portable Bin Or Another Type Of Bootloader File). 

When Bios Runs The Operative Syste (Bootloader), If It Is The First Time, A Setup Window Appears To Let Users Configure The Settings. If It Is A Rutinary Run, A Load Window Appears To Let Users Enter Login Password, Etc. Then, A Manager Window Appears To Let Users Handle The Operative System. 

Join The Project To Discuss The Main Idea Of The Project.

This Is The Main Idea, The Words And Concepts Between " " Are Things That I Do Not Know If Shall Be Possible. 

The Main Idea Of The Project Is To Create An Executable And "Portable" Operative System That Runs From Bios (Bootloader). All Drives, Urls (Directories) And Data (Files) Are Codes That Are Executed By O.S. (In Setup, Users Define Virtual Drives And Urls That Are Just References Inside The Program, While Data Is Stored "As Essential Binary, Hexadecimal, Octagecimal, Decimal, Ascii, Etc. Codes Inside Virtual/Referencial Extension Containers That Are Defined By Data Extensions Codes"). For Example, An Mp3 File Would Be Read As Binary, Hexadecimal, Or Any Code And Splited In Two: Its Extension (Mp3) And Its Content (Audio). Then, Its Content Would Be Stored Inside A Drive, A Directory, And A Mp3 Extension Container.  In Other Words: Make Extensions Codes, Save Only Main Code Of Data And Then, Add The Extension Codes When Data/Files Are Used.

There Would Be Identifier/Access Codes For O.S. Load, Drives, Urls, Commands, Data And Related Software (Defined By User In Setup). 

User Name And Password = Profile Code + Random Code. 
Commands = Profile Code, Command Password And Command Derived Code + Random Codes. 
Programs =  Profile Code, Programs Main Password And Program Name Derived Code + Random Codes. 
Drive = Profile Code, Drive Main Password And Drive Name Derived Code + Random Codes.
URL = Profile Code, Drive Code, URL Main Password And Directory Name Derived Code + Random Codes.
Data = Profile Code,Drive Code, URL Code,  Data Main Password And Data. Name Derived Code + Random Codes. 
Extension = Profile Code, Extension Main Password And ext. Name Derived Code + Random Codes. 

Profile Code.Command Code.Program/Application Code  =Action Code.

Data = Profile Code.Drive Code.Url Code.File/Data Code.Extension Code.

Ussage = Profile Code.Action Code.Drive Code.URL Code.File/Data Code.Extension Code.

Commands Codification Creates The User Defined Commands To Handle The Operative System. 

Programs/Applications Codification Creates The User Managed Registration Of Trusted Compatible Software That Are Allowed To Run Through The Operative System And Change Data.

Drives And Urls Codification Creates The Referencial Structure Of The Operative System.
Data/Files And Extensions Codification Defines Data As Source Codes Integrated To O.S. Source Code. 

I Thought In A Package Structure For Dividing The Source Code:

QdyrxLoad = Bios Setup(First Time),  Login And Load O.S. (Commands), QdyrxOs = Manager Tools, QdyrxMain =Drive, Urls, Data, Ext., Etc., QdyrxIntTools = Integrated Applications (Web, Text, Media, Etc.).