This is a cache of https://vccplus.brianholman.com/manuals/working-with-os9/shell/. It is a snapshot of the page as it appeared on 2026-11-21T00:01:48.390+0000.
Which program heard me? · Working with OS-9 — A Comprehensive Manual · VCC Plus
← Manual LibraryVCC Plus 3.7.1 · Reading on the web

Try the exercises in VCC Plus. Example links download files here; open them in the app to work beside the emulator.

The complete book · PDF editionBook 11: Working with OS-9 — A Comprehensive Manual

51 pages · VCC Plus 3.7.1 · Keep a copy to read or print.

Download PDF
Contents

Chapter 1 of 14

Which program heard me?

Your station needs a log. At the keyboard you can name a disk, ask the time, or start a second command interpreter. The first puzzle is who hears those keystrokes. On this CoCo the answer changes twice between power-on and the first command.

Boot your practice station

In Machine → Configuration Profiles…, select NitrOS-9 L2 V3.3.0, choose Create Fresh Starter Media… and name the personal copy Beacon Station. Load that copy, confirm the restart and choose Run. Use the same working images for this book. If you are returning from the quick start, you can also use its personal practice set if the new names are unused. The quick start shows the controls.

The prepared profile enters the boot command at RGB-DOS. The CoCo boots the system on HD0 and eventually starts Shell+ at the terminal. Click the CoCo display. Wait for the prompt ending in /DD:. The text before the path identifies the terminal and shell process, such as {Term|02}. If you see the BASIC OK prompt, follow the return trip to OS-9.

Open Media → Virtual Hard Disks…. Identify the image files assigned to HD0 and HD1. The guest uses /dd for its default system disk. On this profile /h0 reaches that same disk. /h1 holds your practice work. Close the drive window and click the CoCo display again.

Read the system’s morning instructions

At Shell+ enter:

list /dd/startup

You are reading a file already run during boot. Near the top, two echo commands explain the welcome banner. The file keeps the shell resident, loads a set of utilities, and loads a networking module. Farther down it creates windows and starts shells on window devices. Seeing a networking module in this listing does not grant a guest permission to use a Mac shell. That decision belongs to VCC Plus.

The kernel and I/O modules must already be running for that file to be readable. The boot code brought in the operating system, including the modules in OS9Boot. The system startup process arranges the initial environment. The shell can then execute the readable startup procedure. Changing a startup command and rebuilding the set of boot modules act at different stages. Keep the system image intact during these exercises. Later chapters let you inspect modules while the station runs.

Predict two search paths

Make a new practice directory on your private HD1 and enter it.

makdir /h1/station
chd /h1/station
pwd
pxd

pwd returned /H1/station, the current data directory. pxd returned /DD/CMDS, the current execution directory. If the directory already exists, inspect its contents before reusing it. A new copy of the practice media gives you fresh names.

The guest prints /H1/station for pwd and /DD/CMDS for pxd beneath the same Shell+ prompt.

When you ask a utility to open an ordinary relative filename, the data directory supplies the starting point. When you type a program name, Shell+ can find a resident module or search for executable material using its command search rules. The execution directory supplies the usual location of disk commands. A leading slash starts a path at a named device. You can therefore stand in your station directory, run list from the command environment and read /dd/startup from the system disk.

Prediction. You will shortly type build report. Which disk will receive the two-line file? The answer is HD1 because report is a relative data filename and the current data directory is /H1/station. The shell’s ability to find build is a different lookup.

Original VCC Plus manuals © 2026 Brian K. Holman. Third-party references retain their authors’ copyrights and licenses. Artwork notices. Edition 3.7.1; source and export identity. Printable edition: PDF source and export identity.

A closer look

Open original