In a previous video Micro Tutorial here at Experts Exchange, I presented my CapsLockOSD program, which is a utility that constantly shows the state of the CapsLock key (ON or OFF) in the system tray. This video Micro Tutorial presents a modified version of CapsLockOSD with two enhancements: (1) the ability to create a stand-alone executable (an EXE file) that can run on a system without AutoHotkey installed and (2) an option to run automatically whenever Windows starts. If you do not require either of these new features, you may stick with the previous version of the program.
Note: The video does not demonstrate how to compile the AHK source code into an EXE file, so I've included Steps 5 and 6 below to explain that.
Test all the features of CapsLockOSD as shown in my previous video to confirm that they all work correctly in this enhanced version.
4. Test the new feature that starts CapsLockOSD with Windows
Right-click the CapsLockOSD icon, then left-click Start with Windows.
Right-click the CapsLockOSD icon again and confirm that the Start with Windows menu item is checked.
Restart Windows and confirm that CapsLockOSD is running.
5. Compile the CapsLockOSD program
Read my Experts Exchange article that explains how to compile AutoHotkey source code (an AHK file) into a stand-alone executable (an EXE file): AutoHotkey - Getting Started
Use the "more compiling options" feature explained in that article so that you will have a custom icon for the EXE file, namely, the CapsLockOSD.ico that you downloaded in Step 2.
6. Test the EXE file
Put the EXE file on a different computer — one without AutoHotkey installed.
Run the EXE file on that other computer.
Test all the features, as you did with the AHK file, to confirm that the EXE file on the computer without AutoHotkey runs the same.
That's it! If you find this video to be helpful, please click the thumbs-up icon below. Thank you for watching!
Generally, a Service Code of SC899-00 will be caused by incorrect drivers on a Windows computer. Ensuring you have correct drivers installed and are not using Microsoft IPP Class Drivers and are not using a WSD port, are the most common solutions. …