Two (2) basic ways to run bootAble:
- First time run:
- Using a new bootAble distribution
- Creating a new bootAble configuration file:
- A configuration file is your saved responses to the prompts
- Therefore, you do not have to respond to prompts the next time you run bootAble
- Instead, run it with your configuration file as a parameter
- File can contain other desirable things, such as commands to copy personalized programs, scripts and the like to the CD/DVD or partition
- Question: why create more than one (1) configuration file; Answer: to boot your system up differently, perhaps as a hedge against future system configuration problems:
- Boot to WPS with Object REXX, networking and Peer
- Boot to WPS with Object REXX, no networking or Peer
- Boot to a commandline with Object REXX
- Boot to a commandline without Object REXX
- Using an existing bootAble configuration file:
- Place updated programs on the CD/DVD or partition
- Place updated drivers there
- Configuration file manually modified to add more functionality
First time run:
- Open a commandline in the folder where you unzipped the bootAble distribution
- Type and enter "bootAble.cmd" (without the quotes)
- "bootAble.cmd" calls the configuration file, "bootAble.cfg", which in turn prompts you for how you want to set up your CD/DVD or partition
- Respond to the prompts (usually requiring "Y" for "Yes", or "N" for "No")
- Possibly save results into a new configuration file
- A small number of responses will not be saved to the configuration file:
- Therefore, will have to respond to those prompts again, when you run using the configuration file
- You can fix that by manually editing the configuration file and placing your desired responses in it
- Use your configuration file as a guide for the proper command syntax
Using an existing configuration file:
- Open a commandline in the folder where you unzipped the bootAble distribution
- Type and enter a command to run bootAble with a configuration file. The syntax is:
bootAble.cmd [/v < verbose >] [< configuration file >|/@< configuration-list-file > ...]
- The optional arguments are the verbosity level and one or more configuration files
- The verbosity levels are for error checking and debugging; they are as follows:
- 1 = Progress messages
- 2 = Files copied and files parsed
- 4 = Config file parsing
- 8 = INI rc file parsing
- 64 = Error output of external commands
- 128 = All external command output
- Add the numbers together to combine levels (example: 195 = progress messages, files copied and files parsed, error output of external commands and all external command output)
- The configuration files override the defaults specified in "bootAble.cfg"
- The special form, /@configuration-list-file, results in the content of a configuration list file to be used to list additional configuration files
- If the file, "bootAble.wpslst1", contains the lines:
- bootAble.ba2k
- bootAble.mozilla
- bootAble.norman
- Then, the command:
bootAble.cmd /v 67 bootAble_WPS.Mycfg /@bootAble.wpslst1
- Produces the same results as the command:
bootAble.cmd /v 67 bootAble_WPS.Mycfg bootAble.ba2k bootAble.mozilla bootAble.norman