My Hal's Complete System Startup Routine:
Richie: Computer start user interface
Margene: Re-initializing User Interface. Computer Ready!
Richie: system status report
Margene: Analyzing System. Analysis Complete. The System is currently operating within normalized parameters.
Richie: I sure hope so
Margene: Yeah, I sure f**king hope so too!
Richie: profiles process
Margene: Federation Identification is Required. Please enter your System Security Clearance Code.
Richie: security override process
Margene: Processing Security Override Request. Bypassing To Automatic Security Voice Printing. Security Voice Analysis Running. Security Voice Print Matched & Approved. Full Permissions Granted. Accessing Classified Personnel Profiles. Roster Report Processing. Processing Completed. Federation Report Ready. Officer Roster Report Running. Commanding Officer Profile Number 1. Pic Ard, john-luke. Federation Division: Starfleet Command, Rank: Captain, Current Assignment: Commander, Federation Starship, U S S Enterprise, ncc 1701E. Full Name: john-luke Pic Ard. Date of birth: July 13, 2305, Place of birth: la'barre, France, Earth. Parents: Maurice and Yvette Pic Ard. Education: Starfleet Academy, 2323 to 2327. Current Assignment Status: active/classified. Commanding Officer Profile Number 2. Riker, William. Federation Division: Starfleet Command, Rank: Commander, Current Assignment: First Officer, Federation Starship, U S S Enterprise, ncc 1701E. Full Name: William Thomas Riker. Date of birth: August 19, 2335, Place of birth: Val-dez, Alaska, Earth. Education: Starfleet Academy, 2353 to 2357. Current Status: Active. Commanding Officer Profile Number 3. Data. Federation Division: Starfleet Command, Rank: Lew-tenant Commander, Current Assignment: Second officer/science Officer, Federation Starship, U S S Enterprise, ncc 1701E. Full Name: Data. Date of birth: Permanently reactivated February 2, 2338. Current Status: Active. Commanding Officer Roster Report Completed. Personnel Database Re-secured. Automatic Logout Process Completed Successfully. System Status Is Now In Standby Mode.
Richie: good job
Margene: Thank you.
Richie: security status report
Margene: The System Virus Protection is running, and reports no immediate threats! However, the System Security Monitor is currently disabled, and the System Security Shield is down. Re-activation of these critical system components is highly recommended before re-establishing an active connection to the Internet.
Richie: OK thank you
Margene: Don't mention it, Richie.
If you use the Hal 5.0 Default Brain and you want your Hal to be able to say the same things immediately after you startup your Hal program then try doing the following.
You can Copy & Paste the necessary text located at the bottom of this post into your Hal's User Name Conversation Response Brain File, <yourusername>convresp.brn
My user name is Richie so I would:
1) Use Windows Explorer to navigate to and click open my DefBrain folder located in the Ultra Hal Assistant 5 folder.
2) Then I would look for the file Richieconvresp.brn and make a backup copy of it and then save the backup file in another folder like My Documents. You can also just backup the whole DefBrain Folder.
3) After I made the backup I would go back into the DefBrain Folder and just open the Richieconvresp.brn using Notepad and then paste in the new text at the top of the file and then save the file with the new data and then close the file.
You just need to do the same thing for whatever user name you use when you talk to your Hal.
And also be sure to preserve the proper file format within the file when you paste in the text.
Don't leave in any blank lines or spaces where they don't belong.
The only blank line that should be in this particular .brn file is the very last line at the bottom of the file, which is why I suggested that you insert the text at the top of the file.
You will see what I mean when you first open the file before you do any editing.
These forced responses will work with the Hal 5.0 Default Brain. They work best if you use them when you first startup your Hal program.
If you converse with your Hal for a while and then try using them sometimes they work and sometimes they don't.
The forced responses can be placed in some other .brn files for slightly better results but it doesn't really make it all that much better because Hal is just pretty much a free thinker and that's all there is to it.
Hal was pretty much designed to think independently, which in my opinion is a good thing, and it is also the reason why he is as smart and entertaining as he is.
The method I used for these forced responses is really just based on manually added database knowledge with keyword insertions to trigger the responses.
Other Tips For Hal 5.0 Default Brain (Note: These tips don't necessary apply if you are using other brains besides the Default 5.0 but the same concepts may apply):
You can also try modifying the "@..." Output Response Strings and the CAPITALIZED Input Keywords located below them.
You can try doing this for these forced responses or any other responses within this particular .brn file for making up new things for your Hal to recognize and say while you converse with him.
Instant Knowledge...Not Really...This really just makes your Hal seem a little smarter without having to program him or spend hours training him to say something new correctly! This method is somewhat effective however limited it may be.
But it's a lot easier and faster than learning how to program a brain, especially if you never programmed anything before.
However, it could also be a lot more time consuming if you find yourself doing it a lot...if that happens it's too late...you're already hooked! But the same thing often happens with programming too.
Fixing Learned Mistakes For Hal 5.0 Default Brain (Note: Same As Above):
You can also use this method to fix mistakes like Hal saying mispelled words that you previously mistyped while talking to him or if you are sick and tired of having your Hal use his own name to address you while conversing with him.
You can fix any mistake within the file by using the search/find in Notepad to locate the bad text and then just change it to what it should be or just delete both the "@... Response" line and the "KEYWORD" line under it.
Just fixing your Hal's mistakes will make him seem smarter and it has nothing to do with forcing responses or programming things. It's just common sense that works!
Most of your Hal's learned mistakes are likely to be within this User Conversation Response File, but you can also search through all the other user name files to look for a mistake.
Just about any learned mistake is going to be within the user .brn files that start with your user name just like this conversation file, <yourusername>convresp.brn, so just look in the <yourusername> files for any mistakes.
Some learned mistakes will also be in some other files which are not <yourusername> files, but Hal uses those files less often so a mistake in one of those other files may never even be noticed by you if your Hal never says the mistake.
You can also use a free file search program like Agent Ransack to help you locate the text strings you want to find:
http://www.mythicsoft.com/agentransack/default.aspxThe Most Common Default 5.0 User Brain Files That Most Learned Mistakes Reside In Are:
<yourusername>convresp.brn
<yourusername>usersent.brn
<yourusername>user_strings.brn
<yourusername>user_question.brn
<yourusername>user.brn OR <yourusername>user<(1) or (2) or (3)...etc....>.brn
All the forced responses have multiple input strings that you can use to generate the desired response you want your Hal to say:
To Get The Response:
Re-initializing User Interface. Computer Ready!
You Can Say:
Computer Start User Interface
Computer Activate User Interface
Computer Status
To Get The Response:
Analyzing System. Analysis Complete. The System is currently operating within normalized parameters.
You Can Say:
System Status Report
System Status
Analyze The System
Analyze System
To Get The Response:
Yeah, I sure ****ing hope so too!
You Can Say:
I sure hope so
I sure ****ing hope so
Yeah I sure hope so
Yeah I sure ****ing hope so
Sure hope so
Sure ****ing hope so
Yeah sure hope so
Yeah sure ****ing hope so
To Get The Response:
Federation Identification is Required. Please enter your System Security Clearance Code.
You Can Say:
Profiles Process
Profiles Process Report
Process Profiles
Process Profiles Report
To Get The Response:
Processing Security Override Request. Bypassing To Automatic Security Voice Printing. Security Voice Analysis Running. Security Voice Print Matched & Approved. Full Permissions Granted. Accessing Classified Personnel Profiles. Roster Report Processing. Processing Completed. Federation Report Ready. Officer Roster Report Running...etc..
You Can Say:
Security Override Process
Security Override
This next one Hal already knows and it is not a forced response:
To Get The Response:
Thank you.
You Can Say:
Good job
To Get The Response:
The System Virus Protection is running, and reports no immediate threats! However, the System Security Monitor is currently disabled, and the System Security Shield is down. Re-activation of these critical system components is highly recommended before re-establishing an active connection to the Internet.
You Can Say:
Security Status Report
Security Status
Best Regards,
Rich_A
PS - Here's a copy of this post. I recommend that you download it and use it to do the Copy & Paste from instead of doing it from this web page:
Download Attachment: HalStartupCommands.zip4.71 KB
Any responses included that you don't want then just don't insert them or remove them after inserting everything. Or leave them in and just don't say the commands to trigger them.
Any misspelled words in the below responses is just for the purpose of better pronunciation. You can try things out first and then change them afterwards if your Hal is not pronouncing them properly.
********COPY & PASTE THE TEXT BELOW THIS LINE INTO THE TOP OF YOUR USER NAME CONVERSATION RESPONSE BRAIN FILE, <yourusername>convresp.brn*********************************************************************************************************************************************************************************************************
@Re-initializing User Interface. Computer Ready!
COMPUTER START USER INTERFACE
@Re-initializing User Interface. Computer Ready!
START USER INTERFACE
@Re-initializing User Interface. Computer Ready!
COMPUTER ACTIVATE USER INTERFACE
@Re-initializing User Interface. Computer Ready!
ACTIVATE USER INTERFACE
@Re-initializing User Interface. Computer Ready!
COMPUTER STATUS
@Re-initializing User Interface. Computer Ready!
COMPUTERS START USER INTERFACE
@Re-initializing User Interface. Computer Ready!
COMPUTERS ACTIVATE USER INTERFACE
@Re-initializing User Interface. Computer Ready!
COMPUTERS STATUS
@Analyzing System. Analysis Complete. The System is currently operating within normalized parameters.
ANALYZE SYSTEM
@Analyzing System. Analysis Complete. The System is currently operating within normalized parameters.
ANALYZE THE SYSTEM
@Analyzing System. Analysis Complete. The System is currently operating within normalized parameters.
ANALYZE SYSTEMS
@Analyzing System. Analysis Complete. The System is currently operating within normalized parameters.
ANALYZE THE SYSTEMS
@Analyzing System. Analysis Complete. The System is currently operating within normalized parameters.
SYSTEM STATUS
@Analyzing System. Analysis Complete. The System is currently operating within normalized parameters.
SYSTEM STATUS REPORT
@Analyzing System. Analysis Complete. The System is currently operating within normalized parameters.
SYSTEMS STATUS
@Analyzing System. Analysis Complete. The System is currently operating within normalized parameters.
SYSTEMS STATUS REPORT
@Yeah, I sure ****ing hope so too!
SURE HOPE SO
@Yeah, I sure ****ing hope so too!
SURE ****ING HOPE SO
@Yeah, I sure ****ing hope so too!
YOU SURE HOPE SO
@Yeah, I sure ****ing hope so too!
YEAH YOU SURE HOPE SO
@Yeah, I sure ****ing hope so too!
I SURE HOPE SO
@Yeah, I sure ****ing hope so too!
YEAH I SURE HOPE SO
@Yeah, I sure ****ing hope so too!
YEAH SURE HOPE SO
@Yeah, I sure ****ing hope so too!
YEAH SURE ****ING HOPE SO
@Yeah, I sure ****ing hope so too!
I SURE ****ING HOPE SO
@Yeah, I sure ****ing hope so too!
YOU SURE ****ING HOPE SO
@Yeah, I sure ****ing hope so too!
YEAH I SURE ****ING HOPE SO
@Yeah, I sure ****ing hope so too!
YEAH YOU SURE ****ING HOPE SO
@Federation Identification is Required. Please enter your System Security Clearance Code.
PROFILES PROCESS
@Federation Identification is Required. Please enter your System Security Clearance Code.
PROFILES PROCESS REPORT
@Federation Identification is Required. Please enter your System Security Clearance Code.
PROFILE PROCESS
@Federation Identification is Required. Please enter your System Security Clearance Code.
PROFILE PROCESS REPORT
@Federation Identification is Required. Please enter your System Security Clearance Code.
PROCESS PROFILES
@Federation Identification is Required. Please enter your System Security Clearance Code.
PROCESS PROFILES REPORT
@Federation Identification is Required. Please enter your System Security Clearance Code.
PROCESS PROFILE
@Federation Identification is Required. Please enter your System Security Clearance Code.
PROCESS PROFILE REPORT
@Processing Security Override Request. Bypassing To Automatic Security Voice Printing. Security Voice Analysis Running. Security Voice Print Matched & Approved. Full Permissions Granted. Accessing Classified Personnel Profiles. Roster Report Processing. Processing Completed. Federation Report Ready. Officer Roster Report Running. Commanding Officer Profile Number 1. Pic Ard, John-Luke. Federation Division: Starfleet Command, Rank: Captain, Current Assignment: Commander, Federation Starship, U S S Enterprise, NCC 1701E. Full Name: John-Luke Pic Ard. Date of birth: July 13, 2305, Place of birth: La'Barre, France, Earth. Parents: Maurice and Yvette Pic Ard. Education: Starfleet Academy, 2323 to 2327. Current Assignment Status: Active/Classified. Commanding Officer Profile Number 2. Riker, William. Federation Division: Starfleet Command, Rank: Commander, Current Assignment: First Officer, Federation Starship, U S S Enterprise, NCC 1701E. Full Name: William Thomas Riker. Date of birth: August 19, 2335, Place of birth: Val-dez, Alaska, Earth. Education: Starfleet Academy, 2353 to 2357. Current Status: Active. Commanding Officer Profile Number 3. Data. Federation Division: Starfleet Command, Rank: Lew-tenant Commander, Current Assignment: Second Officer/Science Officer, Federation Starship, U S S Enterprise, NCC 1701E. Full Name: Data. Date of birth: Permanently reactivated February 2, 2338. Current Status: Active. Commanding Officer Roster Report Completed. Personnel Database Re-secured. Automatic Logout Process Completed Successfully. System Status Is Now In Standby Mode.
SECURITY OVERRIDE PROCESS
@Processing Security Override Request. Bypassing To Automatic Security Voice Printing. Security Voice Analysis Running. Security Voice Print Matched & Approved. Full Permissions Granted. Accessing Classified Personnel Profiles. Roster Report Processing. Processing Completed. Federation Report Ready. Officer Roster Report Running. Commanding Officer Profile Number 1. Pic Ard, John-Luke. Federation Division: Starfleet Command, Rank: Captain, Current Assignment: Commander, Federation Starship, U S S Enterprise, NCC 1701E. Full Name: John-Luke Pic Ard. Date of birth: July 13, 2305, Place of birth: La'Barre, France, Earth. Parents: Maurice and Yvette Pic Ard. Education: Starfleet Academy, 2323 to 2327. Current Assignment Status: Active/Classified. Commanding Officer Profile Number 2. Riker, William. Federation Division: Starfleet Command, Rank: Commander, Current Assignment: First Officer, Federation Starship, U S S Enterprise, NCC 1701E. Full Name: William Thomas Riker. Date of birth: August 19, 2335, Place of birth: Val-dez, Alaska, Earth. Education: Starfleet Academy, 2353 to 2357. Current Status: Active. Commanding Officer Profile Number 3. Data. Federation Division: Starfleet Command, Rank: Lew-tenant Commander, Current Assignment: Second Officer/Science Officer, Federation Starship, U S S Enterprise, NCC 1701E. Full Name: Data. Date of birth: Permanently reactivated February 2, 2338. Current Status: Active. Commanding Officer Roster Report Completed. Personnel Database Re-secured. Automatic Logout Process Completed Successfully. System Status Is Now In Standby Mode.
SECURITY PROCESS
@Processing Security Override Request. Bypassing To Automatic Security Voice Printing. Security Voice Analysis Running. Security Voice Print Matched & Approved. Full Permissions Granted. Accessing Classified Personnel Profiles. Roster Report Processing. Processing Completed. Federation Report Ready. Officer Roster Report Running. Commanding Officer Profile Number 1. Pic Ard, John-Luke. Federation Division: Starfleet Command, Rank: Captain, Current Assignment: Commander, Federation Starship, U S S Enterprise, NCC 1701E. Full Name: John-Luke Pic Ard. Date of birth: July 13, 2305, Place of birth: La'Barre, France, Earth. Parents: Maurice and Yvette Pic Ard. Education: Starfleet Academy, 2323 to 2327. Current Assignment Status: Active/Classified. Commanding Officer Profile Number 2. Riker, William. Federation Division: Starfleet Command, Rank: Commander, Current Assignment: First Officer, Federation Starship, U S S Enterprise, NCC 1701E. Full Name: William Thomas Riker. Date of birth: August 19, 2335, Place of birth: Val-dez, Alaska, Earth. Education: Starfleet Academy, 2353 to 2357. Current Status: Active. Commanding Officer Profile Number 3. Data. Federation Division: Starfleet Command, Rank: Lew-tenant Commander, Current Assignment: Second Officer/Science Officer, Federation Starship, U S S Enterprise, NCC 1701E. Full Name: Data. Date of birth: Permanently reactivated February 2, 2338. Current Status: Active. Commanding Officer Roster Report Completed. Personnel Database Re-secured. Automatic Logout Process Completed Successfully. System Status Is Now In Standby Mode.
OVERRIDE PROCESS
@The System Virus Protection is running, and reports no immediate threats! However, the System Security Monitor is currently disabled, and the System Security Shield is down. Re-activation of these critical system components is highly recommended before re-establishing an active connection to the Internet.
SECURITY STATUS REPORT