Commands for working with INI files
There are two special commands that can be used with Windows INI type files. The LIST INI command can display a value defined in the file, while the SET INI command can change or delete a value. The following are examples of how these commands can be used:
|
LIST INI system.ini drivers wave
|
display value of "wave" in "drivers" section
|
|
SET INI system.ini drivers wave file.dll
|
change value of "wave" to "file.dll"
|
|
SET INI system.ini drivers wave
|
delete the "wave" value name from the file
|
The difference between BOOT and EXEC in the UEFI Version
The BOOT and EXEC commands are very similar in that both will start a UEFI application (which typically has an .EFI extension). However, the BOOT command differs in the following ways:
· It does not allow parameters
· It will unload and remove all drive assignments (0: to 9: as well as C: to Z:)
· It makes all UEFI file systems available to the UEFI application
· It expects to be launching a kernel loader that will not return.
If the kernel loader returns control to the program, the C: drive will be made available again; however, all other drive assignments would need to be reestablished.
Executing a script from interactive mode, or from another script
The RUN command will execute a script, either from the command prompt, or from another script. If executed from the command prompt, you will be returned to the prompt when execution completes. If a RUN command is executed from a script, it will return to the calling script when execution completes, and continue where it left off. Note that when executing a script with the RUN command, all open file systems, registry files, and registry keys will remain open when the script completes, unless explicitly closed by the script. This differs from running a script from the OS command line, where all open items will be closed automatically when the script completes.
Executing TBScript or native programs
The Professional version of TBOSDT includes the TBScript engine which allows you to build scripts that include logical and mathematical operations. For complete details see the TBScript.
Pausing execution of a script
The INTERACTIVE command can be used to pause execution of a script to examine the results to that point, or to manually execute some commands for testing or debugging purposes. All mounted file systems, open registry files, and open registry keys will remain as they were before the pause. To continue execution of the script from where it left off, type EXIT.
Rebooting or shutting down the system
The REBOOT command can be used to reboot or shut down the system. Using REBOOT without any parameters will reboot the system, while REBOOT /s will shut it down. The /f option can be used to force a reboot if necessary, and if available.
Exiting interactive mode
The EXIT command will exit TBOSDT when running in interactive mode. All mounted (open) file systems, registry files, and registry keys will be closed. In the case where the INTERACTIVE command is used to pause script execution (as explained above), the EXIT command will cause TBOSDT to continue script execution at the point where it left off.
