LOADWB starts the Workbench. Normally, this is in the Startup-sequence file that starts Workbench when booting. If you close the Workbench, LOADWB can restart it from a Shell.
The -DEBUG option makes a special developer menu, Debug, available in the Workbench menu bar. If the DELAY option is specified, LOADWB waits three seconds before executing to allow disk activity time to stop. The CLEANUP option automatically performs a cleanup of the initial disk window.
Workbench snapshots the current paths in effect when the LOADWB command is executed. It uses these paths for each Shell started from Workbench. NEWPATH allows you to specify a new path that is snapshot from the current Shell.
If you quit the Workbench and are working through a Shell, enter:
to return the Workbench. Entering LOADWB when the Workbench is already loaded has no effect.
1> PATH DF2:bin ADD
1> LOADWB NEWPATH
loads the Workbench. Any Shells started from the icon have the same path as the Shell used to run the LOADWB NEWPATH command.
Sets the write-protect status of a device.
LOCK sets or unsets the write-protect status of a device or partition. The LOCK remains on until the system is rebooted or until the LOCK is turned off with the LOCK OFF command.
An optional passkey can be specified. If the passkey is used to lock a hard disk partition, the same passkey must be specified to unlock the partition. The passkey can be any number of characters long.
The Work partition is locked. You can read the contents of Work with commands such as DIR, LIST, or MORE but you cannot alter the contents of the partition. If you try to edit the contents of a file on Work, a requester indicates that Work is write-protected. For example, if you try to create a new directory by entering the following:
the following message appears:
Can't create directory Work:Test
Disk is write-protected
To unlock the partition, enter:
Locking a device is only good for the duration of the current session. Resetting or turning off the Amiga cancels the lock.
Retensions, rewinds, or skips forward SCSI (Small Computer System Interface) tapes.
MAGTAPE [DEVICE <device name>] [UNIT <n>] [RET | RETENSION] [REW | REWIND] [SKIP <n>] |
|
By default, MAGTAPE uses SCSI device unit 4. To change the default, you must use both the DEVICE and UNIT keywords.
The RET | RETENSION option runs the tape to the end and rewinds it. The REW | REWIND option rewinds the tape. The SKIP <n> option skips <n> files on the tape.
MAGTAPE tests to see if the unit is ready before sending the command. If your tape is not on-line, repeat the command.
1> MAGTAPE DEVICE second_scsi.device UNIT 0 REW
MAKEDIR creates new, empty directories with the names you specify. The command works within only one directory level at a time, so any directories on the given paths must already exist. The command fails of a directory or a file of the same name already exists in the directory in which you attempt to create a new one.
MAKEDIR does not create a drawer icon for the new directory.
creates a directory called Tests in the current directory.
creates a directory Xyz in the root directory of the disk in DF1:.
1> CD DF0:
1> MAKEDIR Documents Payables Orders
creates three directories on the disk in DF0:: Documents, Payables, and Orders.
For more examples using MAKEDIR, see Chapter 8.
MAKELINK creates a FROM file, known as a link, that is a pointer to another file, the TO file, on the disk. When an application or command falls the FROM file, the TO file is used. By default, MAKELINK supports hard links: the FROM file and TO file must be on the same volume.
Soft links, which can link across volumes, are not currently implemented.
Normally, MAKELINK does not support directory links. To create a directory link, you must use the FORCE option. If MAKELINK detects that you are creating a circular link, such as a link to a parent directory, a Link loop not allowed message is issued.
Makes a device connected to the system available.
MOUNT reads a device's configuration parameters from a file. It then uses the parameter information to mount the devices or make them available to the system. Multiple devices can be mounted with a single command. The {device} argument specifies the names of the devices to be mounted.
MOUNT can process either DOSDrivers mount files or a traditional multiple-entry MountList file, depending on which of the following three ways the arguments are specified:
|