Welcome to Hal Windows Central...

 

Hal Windows Brain & Command List Introduction:
There is a Hal Windows Brain designed to be used with a Hal 5 and another Hal Windows Brain
designed to be used with a Hal 6. Make sure you use the right one for your version of Hal.
If you are running a duel Hal5/Hal6 configuration (multiple version installation) then you
can use both Hal Windows Brains at the same time while running both versions of Ultra Hal
on a single computer. Both Hal Windows Brains are designed to handle and account for multiple
instances of an Ultra Hal program running on one computer. If you only have a Hal 6 installed
you can still also use a compatible old Hal 5 brain with it provided that you have an old Hal 5
database designed to be used with it. So the Hal Windows Hal 5 brain will work with Hal 6, but
only if you have an old v5 database for it. And finally, if you only have a Hal 5 installed then
everything should also work fairly well because most Hal Windows software was originally designed
and developed with an old Hal 5 program. For desktop system automation an Ultra Hal with Hal
Windows installed will absolutely outdo and outperform any other version of Ultra Hal without
a Hal Windows installation no matter how many other plug-ins or customized things the other Hal
has. A Hal Windows Ultra Hal will always win in overall capability no matter what! Why? There are
many reasons why, but if I had to pick just one it probably would be the fact that any version of
Hal with an additional Hal Windows GUI will enable a Hal user to fully control both their Hal and
their operating system without even having to manually type at all, virtually everything can be
point and click driven, including issuing text commands or complete sentences for chat. Show me
some other Hal plug-in or Hal compatible software package that does that for free or paid.
Hal Windows is the only one that I know of, which is part of the reason why my Hal, Amanda
Interactive, and I decided to make the Hal Windows OS Interface. There is simply nothing
else like it!

 

These demo brain versions are also designed to be used with most any kind of Hal knowledge
database so they are pre-defined to be used with the Zabaware default database. But it is
recommended that you create your own copy of a new or pre-existing knowledge database and
then use that newly created database instead. Creating a new database to be used with a
new brain script is a simple common practice that many Hal users already know how to do
so if you need help with doing that you can just post for help and someone will assist
you with the process.

A full version of a Hal Windows Brain would also include the Amanda Interactive assertive
adult female database but that database is not included with these free demo brain scripts.

 

Command List Overview:
This version of the Hal Windows Brain allows a Hal user to input and repeat Hal Windows commands over and over again without Hal mentioning anything about the user repeating himself or Hal repeating himself or that the commands are short phrases, etc. The usual unnecessary and sometimes annoying Hal responses are automatically filtered out, but the filter process is applied to only Hal Windows commands and nothing else.

 

Some Hal windows commands and functions that use window titles as parameters normally require
that the window title input be case sensitive but that is no longer the case. Much of the recently
updated code requires less case sensitive user input for many of the upgraded functions. However,
the following examples will assume full case sensitivity for learning purposes. Most all win type
(win<funcname>) functions do accept any valid sub-string of a window title. That means something
like the word "Notepad" would be an acceptable parameter for a window with the word "Notepad"
contained anywhere within the window title, such as "hal6.uhp - Notepad". In this example other
valid parameters would be "hal", "pad", "Note", "otep", etc. If multiple instances of the same
exact window exists, such as two "Untitled - Notepad" windows, then the most recently active window is the one that the function will use. If you have two similar windows, such as "hal5.uhp - Notepad" and "hal6.uhp - Notepad", then a user simply needs to use a sub-string that uniquely distinguishes it from any other similar window. In this example "hal5" or "hal6" or just "5" or just "6" would be enough to uniquely identify the window that a user wants to use with the function. So the Hal Windows command "winclose 6" would close the "hal6.uhp - Notepad" window without having any effect on the "hal5.uhp - Notepad" window. Another thing also recommended is that a user inputs more than just one character to specify a window title to ensure that a false positive window title match does not occur, so the "hal6" parameter from the above example would be the better one to use instead of just "6". The examples just given are just examples. I say that because if you really tried to close an editor window that had edit changes contained within it then the window won't completely close until a user responds to the "Save Changes" dialog box. However, there are some Hal Windows functions that are capable of automatically responding to window dialog choices or even completely overriding and bypassing window dialog boxes without having to select a choice. Those kind of functions are very powerful and should be used wisely. Completely bypassing a "Save Changes" dialog box would usually have the same effect as actually answering "No" to the "Save Changes" and then all the edit changes would be lost. So it's the user's full responsibility to be aware of whatever it is they are doing.

 

In an effort to make everything as easy and fuss-free as possible, most all Hal Windows commands
and functions that do not use window titles are usually NOT case sensitive. But now most functions
that accept window titles as parameters are also NOT case sensitive. The newly added window close commands, "close" and "close all", are window based functions that are also NOT case sensitive. This means that these two commands can accept a window title parameter as a substring that is NOT case sensitive which is the easiest way to do things for a Hal Windows user. So the command "close recycle bin" would work for the window title "Recycle Bin", even though the actual title has two uppercase letters in it. But my favorite and most powerful window close function is the
new "close everything" command. The new "close everything" command will try to close all open
windows and programs except for Ultra Hal and Hal Windows GUI's. So now Ultra Hal is capable of
closing many windows in one shot with just a single Hal Windows command. This kind of function
is also very powerful and should be used wisely as well. Other multi-window commands available
are "minimize all" (alias: "min all") and "restore all", which both do exactly what they say.

Due to some recent upgrades all winfunc type of commands are also NO longer case sensitive.
That basically means that a user does not have to worry about capitalizing letters in a command
parameter. The user now has the choice of entering parameters of window title names with or without case sensitivity. But the easiest way to type in a window title parameter is in all lower case. Any valid sub-string of a window title in any kind of case should almost always work. It doesn't get
any easier than that. If a parameter does not work when it's typed in with no case sensitivity
then a user can just re-issue the same command with case sensitivity and that will always
usually work right. So the command "winclose recycle bin" would work for the window title "Recycle Bin", even though the actual title has two uppercase letters in it. The other following examples would also work, "winclose recycle", "winclose bin", "winclose rEcYclE bI", "winclose rECyC", you get the idea. It's very convenient because typing in text in all lower case is usually the easiest thing to
do. It's also better for use with speech recognition because most speech rec software will
usually automatically input the text of a voice command in all lower case. And even if
speech rec changed the case to something unusual like "wINcLOSe rEcYCLe bIN", things
would still most likely work right.

 

You can read more about the winfunc type of commands within the "Command List/Hal Output" section of these instructions. There are many other cooler winfunc commands besides just closing windows as shown in the previous examples. Hal can do many other new things like hide, show, minimize or restore or change the transparency level or set the topmost attribute on or off of any window. He can even change the transparency level of your system's taskbar or hide the system clock or disable the system "Start" button or change an MS Agent character to not be always on top and even change an Agent to be semi-transparent too...etc...etc...etc! There's over 350 Hal Windows Brain commands so there's a lot of new things to play around with!

 

Most all Hal Windows commands and functions are designed to enable the Hal program to do exactly what a Hal user requests with no restrictions and no questions asked. So if you tell Hal to do something then he is going to almost always do it regardless of most any kind of pre-existing
conditions. But I did include some safeguards for preventing certain bad things or mistakes from
happening. The safeguards have a fairly high level of logical checks and balances to ensure that
Hal doesn't try to do something that doesn't make sense to him. A simple example would be a user
telling Hal to perform a window close operation on a window that doesn't exist. Hal will respond
by telling the user that the window was not detected and window titles are also case sensitive.
So if the window really doesn't exist then Hal was right and a window close operation will not be
performed. Now on the other hand, if the window does exist but the user just typed the window title
in wrong then a user would just simply have to re-issue the same window close command again with the proper window title name and format. There are many other built-in internal logical checks
like this, but not all of them are going to always prevent Hal from doing something for you even
though it doesn't make sense to him or he just knows that it's not a good thing to do, like telling
Hal to terminate his own HalAsst.exe process. This version of the Hal Windows Brain let's a user do things like telling Hal to terminate his own process, but in other more advanced versions Hal will
decide and make the final decision on whether or not to actually do something like terminating his
own program process. Unfortunately having many more safeguards also often means more restrictions and I rather have my Hal be able to do absolutely anything I want him to do, so that's the way most things are within this version of the Hal Windows Brain. And by the way, don't tell Hal to terminate his own process because that was just another example. If you did tell him that then he would perform an improper program shutdown which is not good to do. You will see the other Hal windows commands available that could be used for closing Hal's window or properly shutting down his program or even shutting down your entire computer. The main point is that this brain version does not have the additional safeguards that would enable Hal to disobey a shutdown command if the request is for his own program. And the reason why this brain version is like that is because most people don't want their Hal to disobey any kind of user command regardless of what it may be.

Most all Hal Windows commands will usually automatically return control back to the main Hal
window or a Hal Windows GUI, depending on which one is currently in use before a function is
performed. This means that if a certain function requires making one or more other windows
active then Hal will usually automatically make his own window or a GUI window active again
after the function completes its task. Having Hal automatically return control back to his
own window or a GUI window is a way of controlling the desktop environment without having to
constantly point and click on other windows or clicking on the main Hal program window to make
it active again. There are also many commands that allow Hal to manipulate different types of
windows without even having to make the window active or the window may briefly become active
but you won't even notice it because everything happens so fast. Since things are designed in
this optimized way it has the potential to make a Hal program much more capable of proficiently
assisting a Hal user in the every day use of their computer.

 

One other thing worth mentioning is that there are many Hal Windows functions that do not automatically return control back to Hal because they are not supposed to do that if the function requires another window to stay active after the function completes its task. A simple example would be issuing the command "activate start menu" and then Hal performs a virtual click on the system start button to display the actual system start menu. Now it doesn't make sense to return control back to Hal once the system start menu is displayed so the system start menu stays active instead. Another thing that I should also mention is that many virtual clicking functions are performed by utilizing standard Microsoft Windows Hotkeys (aka. Windows keyboard shortcuts) so if you modified or changed your system's standard hotkeys then some Hal Windows functions will not work properly. If a malfunction occurs due to an invalid hotkey assignment there are a few things that you could try to do to correct the problem. Either restore your system's hotkey back to its default setting or modify the existing code within the Hal Windows Brain script to work with a different hotkey assignment. If your system's default hotkey assignments is not the same as the default hotkey assignments of a standard Windows XP system then it may be required that you modify some of the brain script code in order to make things work right. I can assist you with fixing things but you have to know what your own system's hotkey assignments are in order to modify things properly. If you have some sort of software program installed on your computer that permanently changed or corrupted your system's default hotkey assignments then you will have to figure out and fix that kind of problem yourself. If you have trouble fixing system related problems and need more help you can try contacting me but free assistance for things like corrupt system components is very limited and I would probably just tell you to reinstall some or all of your operating system components or try researching the problem on the Internet.

 

The following are some of the Windows keyboard shortcuts that Hal Windows utilizes. And you don't have to memorize anything because your Hal will already know all the key combinations that he will
need to do in order to perform a requested Hal Windows function. The necessary key combinations are already coded into the Hal Windows Brain.

 

Natural keyboard shortcuts

You can use the following keyboard shortcuts with a Microsoft Natural Keyboard or any other
compatible keyboard that includes the Windows logo key (winkey) and the Application key (appkey).

Press    To

winkey    Display or hide the Start menu.
winkey + BREAK   Display the System Properties dialog box.
winkey + D   Show the desktop.
winkey + M   Minimize all windows.
winkey + Shift + M  Restores minimized windows.
winkey + E   Open My Computer.
winkey + F   Search for a file or folder.
CTRL + winkey + F  Search for computers.
winkey + F1   Display Windows Help.
winkey + L   Lock your computer if you are connected to a network domain, or switch users if you are not connected to a network domain.
winkey + R   Open the Run dialog box.
appkey    Display the shortcut menu for the selected item.
winkey + U   Open Utility Manager.

End of Natural keyboard shortcuts

 

You can also consult your system's own Help and Support documentation to confirm that the above
keyboard shortcut list is the same for your computer as it is for mine and most other people's.

All versions of the Hal Windows Brain are plug-ins that work with an Ultra Hal program.
However, the actual Hal Windows OS Interface is not an Ultra Hal plug-in. The full version
of the Hal Windows OS Interface is a very large A.I. system control software program that is
about 200 MB in total size. So Hal Windows is fairly big which is part of the reason why it
doesn't even need an Ultra Hal program to be able to do the thousands of things that it is
designed to do. And in reality the Ultra Hal and Haptek applications are actually considered
as plug-ins that work with Hal Windows software. So a Hal Windows Brain is not even required
to be used in order for the Hal Windows software to work with Ultra Hal. Hal Windows GUI's are
able to do thousands of things with an Ultra Hal program which includes, but is not limited to,
fully controlling a Haptek character with point and click controls or text commands or drag and
drop operations. All the Haptek related things that Hal Windows GUI's are able to do will work
with any kind of window or software application and not just Ultra Hal. So Hal Windows fully
controls any type of Haptek character whether Ultra Hal is running or not. Hal Windows is also
capable of performing many Hal Windows Brain Commands even if Hal is not running because Hal
Windows utilizes its own Auxiliary Offline Brain, and the My Halinator GUI also has it's own
built-in set of internal hard coded commands that perform the same type of functions as a Hal
Windows brain does. So many Hal Windows commands can be performed in three different ways:
1) Hal Windows Brain Script or On-The-Fly UHP plug-in
2) Auxiliary Offline Brain VBS plug-in
3) GUI internal hard coded text commands or point & click command list/menu items/button controls

 

More About Haptek In Hal:
Absolutely any kind of Haptek animation or long running or infinite looping Haptek script can be
ran and fully controlled inside of the Hal program without even using Hal Windows or any other kind
of plug-in for that matter. A standard default Hal program can do any kind of Haptek thing you want
it to do despite whatever anyone has ever said to the contrary. Most everybody is dead wrong when
they say you can't do so and so because of so and so. Don't listen to them! Try this instead, change all your Haptek mood files inside of the Hal "Characters" folder from the default "Script" type to
"Command" type instead, and then you will be able to play any long running or infinite looping Haptek script (defined as "Script" type) forever inside of Hal and it will never stop or fail from Hal
program interference, and all Hal moods will still also continue to work properly. I've been doing
it for over five years now. So in a nutshell, you don't have to modify a Hal brain except for adding
in the necessary code to execute Haptek instructions. Some people often try to force Hal to successfully perform an animation by  making unnecessary brain script code modifications. Changing an internal Hal clock or timer is a perfect example of an unnecessary and sometimes really dumb thing to do just to run a Haptek animation. You usually do not need to do something like modifying a Hal clock or timer in order to do most anything you would want to do that is Haptek related, unless of course you are trying to do some sort of automated function based on a time of day or timeout period. The main thing about running Haptek animations inside of Hal or anything else is "Script" type versus "Command" type of a Haptek file. A "Script" type file always has a higher priority over a "Command" type file so if Hal's moods are all "Command" type then any kind of Haptek file defined as "Script" type will always work and never be overridden when Hal automatically changes his moods. And that means that your own custom scripted animations or long running Haptek presentations will always work and never crap out because of a Hal mood change. So it's recommended that you change all Haptek moods to "Command" type if you want to get the most out of a Hal Windows GUI like the "My Halinator". Why? Because you will be able to fully control your Haptek character inside of Hal without even having to type in any text commands to control all the action. Simple point and click controls is the standard way I do most everything nowadays, and it also all works with any kind of Hal brain script and not just Hal Windows brains. But the changing of mood files to "Command" type is purely optional and completely your choice so do whatever you want. If you don't want to do things like play long running or infinite looping Haptek scripts inside of Hal then you probably don't need to change your Haptek moods to "Command" type. But you still also always have the other option of configuring your Hal to use a specified Haptek character with "Command" type moods by assigning a unique PSN file with the character name so only that character will use the new mood files assigned to it.

 

This version of the Hal Windows Brain is able to function as a real operating system interface
and is NOT A TOY OR MAKE BELIEVE. The first set of commands listed below will actually automatically connect the Ultra Hal program directly into the Windows Management Instrumentation Service in order to perform real system queries or other related functions that require the WMI Service in order for things to work properly. The WMI Service commands and functions listed below are limited to only working on a local computer. However, the actual brain code can be modified for certain WMI commands so that they will work with other computers connected on a network. That basically means that Hal can obtain system information about a remote computer and Hal can also actually control things like hardware devices on a remote computer. But this version of the Hal Windows Brain does not support the remote network functions of the WMI Service, only the local computer is supported. I already have many remote network commands made but as of right now they would probably only be available within a full version of a Hal Windows Brain.

 

The Windows Management Instrumentation Service must also not be disabled or else no WMI commands will work. The usual default "Startup Type" for WMI Service is "Automatic" so that's the recommended setting that it should be if it isn't already.

 

WMI Service Description as explained by Microsoft:
Provides a command interface and object model to access management information about operating system, devices, applications and services. If this service is stopped, most Windows-based software will not function properly. If this service is disabled, any services that explicitly depend on it will fail
to start.

 

Command List/Hal Output:
Many commands have an alias or shorten form that can also be used.
The alias names will be listed right next to the standard command names.
Commands with parameters are represented as: CommandName <Parameter>

 

Hal Windows Management Instrumentation Service Commands:
All queried system information reported by Hal is real.
Any Hal output with a backslash, such as a full path, is represented with a forward slash instead.

 

bios report
Analyzing system bios. Analysis complete. System bios summary for computer system name firehawk02: bios Name : phoenix-awardbios v6.00pg. Version : intelr-42302e31. Manufacturer : Phoenix Technologies, ltd. Sm-bios Version : 3.02.

cd report
Analyzing system cd-rom drives. Analysis complete. 2 cd-rom drives are installed on this Computer, System Name: firehawk02: Drive: E: Drive: F:.

video report
Analyzing system video. Analysis complete. System video summary for computer system name firehawk02: Video Component Name: intel(r) 82845g/gl Graphics Controller. Description: intel(r) 82845g/gl Graphics Controller. Video Processor: intel(r) 82845g/gl Chip. Adapter ram: 64 Megabytes. Video Mode Description: 1024 by 768 by 65536 colors.

memory report
Analyzing system memory. Analysis complete. System memory summary for computer system name firehawk02: Total Physical Memory : 504 Megabytes. Memory Module : A1. Full Capacity : 512 Megabytes. Socket Width : 64 Pins.

hardware report, analyze system

analyze system
Analyzing system. Analysis complete. The system is currently operating within normalized parameters. The current primary Operating System Interface is M5 Windows Management Multitronic Instrumentation Service. Hardware summary for computer system name firehawk02: Primary System Processor Specifications: Name: intel(r) pentium(r) 4 central processing unit 2.53 Gigahertz. Manufacturer: genuineintel. Description: x86 Family 15 Model 2 Stepping 4. Current Clock Speed: 2532 Megahertz. System Memory Specifications: Total Physical Memory: 504 Megabytes. Hard Drive Specifications: Manufacturer: (Standard disk drives). Model: Maxtor 4d080h4. Size: 76 Gigabytes. Video Component Specifications: Name: intel(r) 82845g/gl Graphics Controller. Description: intel(r) 82845g/gl Graphics Controller. Video Processor: intel(r) 82845g/gl Chip. Adapter ram: 64 Megabytes. Video Mode Description: 1024 by 768 by 65536 colors. End of system analysis report. Provided by Zabaware Incorporated.

process total
Analyzing system processes. Analysis complete. The total number of processes currently running is 32.

process load, processor load

process load
Analyzing system processor. Analysis complete. The central processing unit load is currently at 77%.

cancel print jobs
Cancel print jobs now in progress. Cancel print jobs now done.

 

More About System Service Parameters:
The System ClipBoard Service Name is: ClipSrv. The System ClipBoard Display Name is: ClipBook.
So either ClipSrv or ClipBook would be a valid parameter. Consult your own system's service list for more about service names and display names.
As far as system service names are concerned a display name is really nothing more then just an alias for the actual service name.

All Hal Windows service command parameters used to be case sensitive but are NOT case sensitive anymore. So something like "clipsrv" typed as all lower case should work.
In addition to NOT being case sensitive the service name can now also be shortened because substrings are now also acceptable.
So something like "clip" typed as all lower case should also work.
If a shortened form of a name does not work properly then you can try to re-issue the command again by the full service name with case sensitivity.

 

servicestat ClipSrv
The specified service Start Mode is Manual and the Current State is Stopped.

servicepath <servicename> OR servicepath <displayname>

servicepath ClipSrv
The specified service Path is c:/windows/system32/clipsrv.exe.

processpath <processname>

processpath taskmgr.exe
The specified process Path is c:/windows/system32/taskmgr.exe.

eject cd drives
All cd drives ejected.

retract cd drives
All cd drives retracted.

(Additional cd drive functions can found futher down within this command list)

 

Process Functions: processcheck, processpid, processrun, and terminate
<processname> parameters are NOT case sensitive for any process related function.
But some of the below examples will have case sensitivity for process names, such as "HalAsst.exe".
However, "halasst.exe" would also work.

 

processcheck HalAsst.exe
My main program process is running and my fully integrated system wide self-awareness neuro-net is currently active.

processcheck notepad.exe
The specified process is running. Would you like me to terminate it for you?

processcheck 1760
The specified process is running. Would you like me to terminate it for you?

processcheck taskmgr.exe
The specified process is not running.

 

processpid HalAsst.exe
My main program process is currently running and the pid number is 592.

processpid taskmgr.exe
The specified process is running and the pid number is 3580.

 

processrun <processname>
Process names are executables without the full path.
The "processrun" function is designed to launch system related programs which are usually located in either "C:\WINDOWS" or "C:\Windows\System32".
Works with system programs such as Windows Task Manager/taskmgr.exe, Notepad/notepad.exe, Calculator/calc.exe, etc.
Does NOT use or need system shortcuts to programs. Finds programs located within the scope of the main system shell.
Does NOT work with programs located in "C:\Program Files" because those are NOT considered as system programs.
If the process name specified is a process that is already running then Hal will tell you so and he will also state the PID number as well.
If the process is already running then Hal will report the information about it regardless of the kind of process that it may be, system or otherwise.
Works with the following system program file types: (EXE, BAT, COM, or PIF).
The old Hal Windows "shellrun" command used to work with a few additional system program file types (such as CMD, MSC, etc)
but "shellrun" did not report PIDs, so "shellrun" is no longer used and "processrun" has fully replaced it.

 

processrun taskmgr.exe
The specified process is now running and the pid number is 3632.

processrun notepad.exe
The specified process is now running and the pid number is 1488.

processrun calc.exe
The specified process is now running and the pid number is 1732.

processrun HalAsst.exe
The specified process could not be started because it is already running with the pid number of 1552.

processrun wmplayer.exe
The specified process could not be started and only system related programs can be ran using the process run function.

terminate <processname> OR terminate <PIDnumber>

terminate taskmgr.exe
The requested process is now terminated.

terminate 1972
The requested process is now terminated.

 

get productid, get product id, product id

get productid
The Microsoft Windows Product Identification Number for this computer is 00100-oem-001100-00100.

get registeredowner, get registered owner, registered owner

get registeredowner
The Microsoft Windows Registered Owner for this computer is Richard Amico, and me, Amanda Interactive.

get registeredorg, get registered org, registered organization

get registeredorg
The requested organization information could not be obtained from the system registry of this computer.

get startpage, get start page

get startpage
The Internet Explorer Start Page for this computer is http://www.google.com/.

get lastclose, get last close, last close

get lastclose
My main program Last Close Time is July 17, 2007 8:09:03 pm.

get laststart, get last start, last start

get laststart
My main program Last Start Time is July 17, 2007 8:31:39 pm.

get aimbot2 password, aimbot2 password

get aimbot2 password
The current valid aimbot2 password is bigsecret.

Agressive Female Impersonations: seven of nine

do seven of nine
I am, Borg. Designation Seven of Nine. You will be assimilated as we have very efficient sex together. Resistance is futile. I am, going to make you f**king come whether you like it or not. You have no choice. You will comply.

End of Agressive Female Impersonations

Sample Key Press Functions: press escape, press end, press pause

press escape
Escape Key Function done.

press end
End Key Function done.

press pause
Pause Key Function done.

End of Sample Key Press Functions

Sample Process Priority Functions: set high priority, set normal priority

set high priority
My Main Program Priority Level is now Set To High.

set normal priority
My Main Program Priority Level is now Set To Normal.

End of Sample Process Priority Functions

analyze interface
Analyzing interface. Analysis complete. My main program window state number is currently 15 which means that it's active and visible.

enable always on top
My Main Program Interface Display is now Set To Always On Top.

disable always on top
My Main Program Always On Top Setting is now disabled.

activate haptek console
The Haptek Console is now active.

close haptek console
The Haptek Console is now closed.

activate new happlayer
New happlayer window now running.

activate empty happlayer
Empty happlayer window now running.

move happlayer window: Moves a HapPlayer AX window to the current location of the mouse cursor.

move happlayer window
The happlayer window has been moved to screen coordinates 100 by 150.

activate happlayer console
Happlayer Console is now active.

move happlayer console: Moves a HapPlayer AX Console window to the current location of the mouse cursor.

move happlayer console
The Happlayer Console window has been moved to screen coordinates 250 by 425.

select happlayer standard: Performs a remote click operation on the HapPlayer AX Console window "standard" button.

select happlayer standard
Happlayer Console Standard Function now done.

select happlayer empty: Performs a remote click operation on the HapPlayer AX Console window "empty" button.

select happlayer empty
Happlayer Console Empty Function now done.

Other remote control operations on the HapPlayer AX Console window.

clear happlayer history
Happlayer Console History List is now cleared.

clear happlayer command
Happlayer Console Command List is now cleared.

clear happlayer query
Happlayer Console Query List is now cleared.

drop happlayer command
Happlayer Console Drop Command List is now done.

retract happlayer command
Happlayer Console Retract Command List is now done.

drop happlayer query
Happlayer Console Drop Query List is now done.

retract happlayer query
Happlayer Console Retract Query List is now done.

close happlayer console
The Happlayer Console window is now closed.

End of other remote control operations on the HapPlayer AX Console window.

enable happlayer topmost
Happlayer Topmost is now enabled.

disable happlayer topmost
Happlayer Topmost is now disabled.

hide happlayer screen
Happlayer Screen is now hidden.

show happlayer screen
Happlayer Screen is now showing.

close happlayer window
The Happlayer window is now closed.

close all happlayers
All Happlayer windows are now closed.

hide display screen: "Display Screen" refers to the Haptek screen area contained within the Hal program window.

hide display screen
My Main Program Display Screen is now hidden.

show display screen
My Main Program Display Screen is now showing.

hapconfig: Used for "on-the-fly" changes of the actual Haptek display screen area running inside of the Hal program window. The Haptek display screen area can automatically be resized and/or moved to a different location within the Hal program window by using this command. Haptek display screen changes are only temporary and always revert back to their original settings whenever the Hal program window is closed and then re-opened.
hapconfig <X-DisplayPosition> <Y-DisplayPosition> <DisplayWidth> <DisplayHeight> - All 4 parameters must be 3 digits long and all 4 parameters must be entered. There are also other easier to use Hal Windows commands that only require 2 parameters or no parameters for altering the Haptek display screen area but "hapconfig" is the most powerful and most reliable one for changing around the Haptek display screen area inside of the Hal program window. See other related commands below.

hapconfig 002 045 100 150
My Main Program display screen is now altered.

hapstat
My Main Program Haptek display screen is located at the relative window coordinates of 3 by 3 and its absolute size is 544 by 394 pixels.

move display screen: Moves the Haptek display screen area to the current mouse cursor position located within the Hal program window. Relocation to a mouse cursor position outside of the Hal program window will move the Haptek display screen area to that relative outside position, which will also cause it to partially or fully disappear.
The Haptek display screen area cannot actually be moved out of Hal and onto the Desktop or into another window...keep dreaming...as of right now it's still all just relative! However, I did recently make some new HTML's that run a Haptek character right on the Desktop and also inside of Windows Media Player and Winamp.
And absolutely any Haptek character can be universely remote controlled running inside of any kind of window by using the Hal Windows "My Halinator" GUI.

move display screen
My Haptek display screen is now moved.

hapmove <X-DisplayPosition> <Y-DisplayPosition> - Both parameters must be 3 digits long and both parameters must be entered.

hapmove 050 150
My Main Program display screen is now moved.

hapsize <DisplayWidth> <DisplaySize> - Both parameters must be 3 digits long and both parameters must be entered.

hapsize 200 300
My Main Program display screen is now resized.

haprestore: Simply closes the Hal program window in order to automatically reset the Haptek display screen settings. You can also just simply close the Hal program window yourself which is basically doing the same thing. "haprestore" is nothing more then an alias for the Hal Windows command "close interface". However, there are other commands available that can reset or restore the main Hal program window without having to close it, such as "reset interface". See other related commands within this list.

haprestore
Now restoring my Haptek display.

"hide control arrows" and "show control arrows": These two commands refer to the Haptek background left and right control arrows located at the top left corner of the Haptek display screen area inside of the Hal program window.
The additional Hal Windows commands to actually resize or move the control arrows are already obselete and no longer used. However, if many people seem to have an interest in using them they may become available again, but for now hiding and showing are the only control arrow commands that Amanda Interactive and I ever use.

hide control arrows
My Main Program Control Arrows are now hidden.

show control arrows
My Main Program Control Arrows are now showing.

hide comm boxes
My Main Program Comm Boxes are now hidden.

show comm boxes
My Main Program Comm Boxes are now showing.

hide input box
My Main Program Input Box is now hidden.

show input box
My Main Program Input Box is now showing.

hide output box
My Main Program Output Box is now hidden.

show output box
My Main Program Output Box is now showing.

tranhide: Hal Windows transparency commands will almost always usually override the current transparency set on any kind of window which also includes the Hal program window.
However, the new transparency level set on a window is only temporary and will be lost whenever the transparent window is closed or whenever another transparency command is issued to undo a current transparency.
The "tranhide" and "transhow" commands will either set or undo a full transparency on the Hal program window only. The "wintran" command will set a transparency on any window specified by the window title name.
You can refer to the other win type functions like "wintran" and "winclose" located further down in this command list.

tranhide, interface tran on

tranhide
My Main Program Interface Display is now completely transparent.

transhow, interface tran off

transhow
My Main Program Interface Display is now visible again.

hide interface: Performs an actual operating system window hide operation as opposed to just setting a full transparency to the main Hal program window.
Optional Hal Windows GUI's provide a Hal Windows user with the ability to talk to Hal while his main program window is completely hidden, or minimized, or both.
The "My Halinator" Demo GUI is included and designed to be used with this version of the Hal Windows Brain.
The "My Halinator" Demo GUI also has its own set of very advanced high level commands and functions and is not a toy, but rather a real system console window used for controlling both the Ultra Hal and Haptek applications as well as the entire Desktop Environment and Windows Operating System.

hide interface
My Main Program Interface Display is now hidden.

show interface
My Main Program Interface Display is now showing.

minimize interface, min interface

minimize interface
My Main Program Interface Display is now minimized.

restore interface
My Main Program Interface Display is now restored.

reset interface
My Main Program Interface Display is now reset.

close interface
Closing Interface.

minimize all, min all

minimize all
All windows are now minimized.

restore all
All windows are now restored.

show secret menu
Secret Menu is now showing.

hide secret menu
Secret Menu is now hidden.

"display agent size" and "conceal agent size": These two commands just simply hide or show the agent size control located in the Hal program window whenever an MS Agent character is being used with the Hal program.
The other listed agent commands such as "hide agent" and "show agent" can be used on the MS Agent character whether the character is being used by the Hal program or not.
If more than one MS Agent character exists then a Hal Windows agent command will perform its function on the most recently active MS Agent window.
That means that a user can select any MS Agent by simply clicking on it just prior to issuing the agent command to the Hal program. So just click the Agent, make Hal active, and then issue the command...it's easy!
But try to remember that you only have to do all that extra selecting and clicking stuff only if you have more than one MS Agent running at the same time, otherwise just issue the command if you are only running one MS Agent character.

display agent size
Agent Size is now showing.

conceal agent size
Agent Size is now hidden.

hide agent
Microsoft Agent is now hidden.

show agent
Microsoft Agent is now showing.

minimize agent, min agent

minimize agent
Microsoft Agent is now minimized.

maximize agent, max agent

maximize agent
Microsoft Agent is now maximized.

restore agent
Microsoft Agent is now restored.

"enable agent topmost" and "disable agent topmost": In general, MS Agent characters will always have the topmost (always on top) setting by default. However, the "disable agent topmost" command will override the topmost default setting which allows a user to overlap other windows on top of the MS Agent.
I created these commands so that a user doesn't have to always move the MS Agent out of the way if the MS Agent is blocking a user's view of another window or the Desktop. Finally, no more Agent interference...it's too bad I don't use MS Agent characters anymore.
The Hal Windows "wintran" command can also be used to set different transparency levels to absolutely any kind of MS Agent character since MS Agent characters are really nothing more than just program windows.
The command "wintran x Microsoft Agent" will set the transparency by the value of x, x being any number ranging from 0 (No Transparency) to 9 (Full Transparency).
The "Microsoft Agent" parameter is just simply the window title name that almost all MS Agent characters have...yes that's right, they all have the same window title name even though you can't see it but your Hal now can.

enable agent topmost
Microsoft Agent is now set to always on top.

disable agent topmost
Microsoft Agent always on top setting is now disabled.

"close chat log" and "close pad" just simply closes the Hal Pad window.

close chat log
Chat Log now closed.

close pad
Pad now closed.

set default position: Just simply moves the Hal program window to the monitor screen's default position (0,0), which is the top left corner.
The "My Halinator" GUI has very convenient point and click button controls to move the Hal program window to the five most common screen positions. Top Left, Top Right, Bottom Left, Bottom Right, and Dead Center.

set default position
Default Position is now set.

screen resolution
Analyzing System Video. Analysis Complete. The current screen resolution is 1024 by 768 pixels.

monitor size
Analyzing System Video. Analysis Complete. The current system monitor size is 1024 by 768 pixels.

interface display size
My main program interface display size is currently 550 by 400 pixels.

get mouse position
The current mouse cursor coordinates are 208 by 641.

retrieve mouse, retrieve mouse cursor

retrieve mouse
The mouse cursor is now located at the top left corner of my main program window.

"get pixel color" and "get pixel value": Only returns decimal values and not hex values. Full version Hal Windows Brains can return either decimal or hex values and also have a built-in hex converter function that can be used for anything.
Hex Converter Function: hex to decimal, decimal to hex, hex to string, string to hex, or have Ultra Hal speak/converse in Hex Mode. When Hal speaks in Hex Mode his GetResponse output string is automatically converted into hex.
The automatic hex conversion provides Hal with the ability to fluently speak in his native machine code language of hex.
A Hal user also has the option to input hex values instead of a worded sentence when talking to Hal, but a Hal user would have to know what their hex input really means in order to have an intelligent hex chat with Hal.
An RC4 based string encryption function is also an optional mode contained within some full versions of the Hal Windows Brain.

("get pixel color" and "get pixel value" are two different commands and not an alias, see below.)

get pixel color: Default pixel mode is BGR. Returns the BGR color decimal value of the specified pixel located under the mouse cursor. BGR is considered default mode because that's the mode that most people usually work in for most Ultra Hal related imaging projects such as creating a new Hal program window skin. Hal window skin files usually use BGR values by default.

get pixel color
Analyzing Specified Pixel. Analysis Complete. The b-g-r decimal value of the pixel color under the mouse is 5937804.

get pixel value: Optional pixel mode for RGB values. Returns the RGB value instead of the default BGR value.

get pixel value
Analyzing Specified Pixel. Analysis Complete. The r-g-b decimal value of the pixel color under the mouse is 9212506.

move input box: Moves the Hal program input box to the current location of the mouse cursor.

move input box
My Main Program Input Box has now been moved to the relative window coordinates 70 by 68.

move output box: Moves the Hal program output box to the current location of the mouse cursor.

move output box
My Main Program Output Box has now been moved to the relative window coordinates 268 by 341.

move comm boxes: Moves both of the Hal program input and output boxes to the same current location of the mouse cursor. When the input and output boxes overlap each other the output box is usually the topmost visible control, which also of course still continues to function correctly as does the input box as well.

move comm boxes
My Main Program Comm Boxes have now both been moved to the relative window coordinates 112 by 310.

check user privileges: The Hal program cannot log himself in as a system administrator and run his program with full system privileges in this version of the Hal Windows Brain.

check user privileges
Analyzing System User Accounts. Analysis Complete. We both have full system administrator privileges.

check user privileges
Analyzing System User Accounts. Analysis Complete. We both have no system administrator privileges, but if you correctly confirm the password I can log myself in as a system administrator for you.

adminrun <username> <domain> <password>: Runs programs under the specified username, domain, and password. The Windows Operating System "Secondary Logon service" or "RunAs service" must not be disabled if you want this function to work. However, the "adminrun" function is also not available in this version of the Hal Windows Brain.
adminrun

is it dinner time: Hal just plays the c:/windows/media/ding.wav sound by automatically launching a hidden system "Sound Recorder" window and then automatically closes the hidden window after the sound finishes playing.
So a Hal user sees nothing and only hears the "ding" sound. This is merely just a simple example of how to have Hal play a wave sound automatically when he performs a command or function.
This method is just another way to have Hal play wave sound effects and can be used in combination with other things such as a Haptek animation.
If used with a Haptek animation you can do something like play two different sounds simultaneously, an ogg file type with Haptek and a wave file type with Sound Recorder.
So even though the Haptek application no longer supports wave file playback you can still do it with Hal while also playing a Haptek script.

is it dinner time
Was that the dinner bell?

All winfunc type commands that require a window title name as a parameter will accept any sort of unique valid substring of a window title name.
Window title parameters used to also be case sensitive but are NO longer that way due to some recent upgrades.
The substring "Notepad" would be a valid parameter for the window title "Untitled - Notepad".
And now the words "notepad" or "untitled" would both also be valid parameters because of the recent upgrades.
The word "pad" would also be a valid parameter because the word "pad" is a valid substring that is all lower case within the full window title "Untitled - Notepad".

For learning purposes the below examples assume that window title parameters are case sensitive.
And <WindowTitle> represents absolutely any kind of window that a Hal user specifies and not just the window title of examples often used within these instructions such as "Notepad".

winontop <WindowTitle>

winontop Notepad
The window Notepad is now set to always on top.

winofftop <WindowTitle>

winofftop Notepad
The window Notepad is now set to not always on top.

winread <WindowTitle>

winread Notepad
The window Notepad contains the following information: This is just a test!

winstate <WindowTitle>

winstate Notepad
The Notepad window state number is currently 7 which means that it's not active but it's visible.

winstatus <WindowTitle> - Reports window status bar information. The window status bar, usually located at the bottom of a window, does not need to be set as viewable/visible for the specified window. In other words, Hal can always see status bar information for a specified window even if you can't actually see it yourself.
If the specified window does not have a status bar or the status bar information is currently null then Hal will tell you that the window has no readable status bar information.

winstatus Calculator
The window Calculator contains no readable status bar information.

winstatus Notepad
The window Notepad contains the following status bar information: Ln 595, Col 1.

winstatus My Documents
The window My Documents contains the following status bar information: 33 objects 2.36 kb My Computer.

winstatus system32
The window system32 contains the following status bar information: 2,363 objects (Disk free space: 53.1 gb) 399 mb My Computer.

winstatus Task Manager
The window Task Manager contains the following status bar information: Processes: 32 central processing unit usage: 77% Commit Charge: 202M / 1231M.

winactive <WindowTitle> - Activates the specified window.

winactive Notepad
The window Notepad is now active.

winmax <WindowTitle> - Maximizes the specified window.

winmax Notepad
The window Notepad is now maximized.

winmin <WindowTitle> - Minimizes the specified window.

winmin Notepad
The window Notepad is now minimized.

winrestore <WindowTitle> - Restores the specified window.

winrestore Notepad
The window Notepad is now restored.

winhide <WindowTitle>

winhide Notepad
The window Notepad is now hidden.

winshow <WindowTitle>

winshow Notepad
The window Notepad is now showing.

winmove <WindowTitle> - Moves a window to the current mouse cursor position.