Skip to content

Commit aee9b4a

Browse files
author
Mark Pruden
committed
Minor improvement in documentation by reordering Sections discussing CLRDIR
1 parent 9f2bee0 commit aee9b4a

File tree

5 files changed

+90
-103
lines changed

5 files changed

+90
-103
lines changed

Doc/ChangeLog.txt

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,7 @@ Version 3.6
2323
- MGG: Added sample program source files for all language disk iamges
2424
- WBW: Added support for S100 Dual CF Interface
2525
- WBW: Added support for S100 ESP32 SD Interface
26+
- MAP: User guide. Reorder sections around disk formatting
2627

2728
Version 3.5.1
2829
-------------

Doc/RomWBW Applications.pdf

-70 KB
Binary file not shown.

Doc/RomWBW User Guide.pdf

-111 KB
Binary file not shown.

Source/Doc/Applications.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1332,6 +1332,11 @@ Use `CLRDIR` with caution as changes made to disks by `CLRDIR` cannot be undone.
13321332
If `CLRDIR` is used on disk containing data then the directory area will be
13331333
reinitialised and the data previously stored will be lost.
13341334

1335+
**WARNING**: Earlier versions of the `CLRDIR` application do not
1336+
appear to check for disk errors when it runs. If you attempt to run
1337+
`CLRDIR` on a drive that is mapped to a slice that does not actually fit
1338+
on the physical disk, it may behave erratically.
1339+
13351340
`\clearpage`{=latex}
13361341

13371342
## CPUSPD (CPU Speed)

Source/Doc/UserGuide.md

Lines changed: 84 additions & 103 deletions
Original file line numberDiff line numberDiff line change
@@ -1117,100 +1117,6 @@ starting the operating system. Even better, you can use an auto-submit
11171117
batch file to customzie the assignments at startup without any user
11181118
intervention.
11191119

1120-
## Disk Operations/Commands
1121-
1122-
With some understanding of how RomWBW presents disk space to the
1123-
operating systems, we need to go over the options for actually setting
1124-
up your disk(s) with content.
1125-
1126-
### Preparing Media for First Use
1127-
1128-
You can initialize the media in-place using your RomWBW system.
1129-
Essentially, this means you are creating a set of blank directories on
1130-
your disk so that files can be saved there.
1131-
This is somewhat analogous to partitioning of a hard disk
1132-
or doing a low level format of a floppy disk.
1133-
1134-
Initilizing a Floppy disk is covered in the section [Floppy Disk Formatting],
1135-
or for a Hard disk the section [Hard Disk Preparation] covers the steps to
1136-
manually setup a hard disk for first use.
1137-
1138-
### Clearing (Formatting) Drives
1139-
1140-
This is somewhat analogous to doing a FORMAT operation on other systems.
1141-
1142-
With RomWBW you use the `CLRDIR` command to do this.
1143-
This command is merely "clearing out" the directory space of the drive
1144-
referred to by a drive letter and setting up the new empty directory.
1145-
1146-
Refer to $doc_apps$ for more information on use of the `CLRDIR` command.
1147-
1148-
Since `CLRDIR` works on drive letters, make
1149-
absolutely sure you know what media and slice are assigned to that
1150-
drive letter before using `CLRDIR` because `CLRDIR` will wipe out any
1151-
pre-existing contents of the slice.
1152-
1153-
After `CLRDIR` completes, the slice should be ready to use by the operating
1154-
system via the drive letter assigned.
1155-
Start by using the `DIR` command on the drive.
1156-
This should return without error, but list no files.
1157-
1158-
Here is an example of using `CLRDIR`. In this example, the `ASSIGN`
1159-
command is used to show the current drive letter assignments. Then
1160-
the `CLRDIR` command is used to initialize the directory of drive 'G'
1161-
which is slice 2 of hard disk device IDE0 ("IDE0:2").
1162-
1163-
```
1164-
B>ASSIGN
1165-
1166-
A:=MD0:0
1167-
B:=MD1:0
1168-
C:=FD0:0
1169-
D:=FD1:0
1170-
E:=IDE0:0
1171-
F:=IDE0:1
1172-
G:=IDE0:2
1173-
H:=IDE0:3
1174-
1175-
B>CLDIR G:
1176-
CLRDIR Version 1.2B May 2024 by Max Scane
1177-
1178-
Warning - this utility will overwrite the directory sectors of Drive: G
1179-
Type CAPITAL Y to proceed, any key other key to exit. Y
1180-
Directory cleared.
1181-
B>
1182-
```
1183-
1184-
### Checking Disk Layout
1185-
1186-
If you are not sure which disk layout is used for your existing
1187-
media, you can use the CP/M 2.2 `STAT` command to display information
1188-
including the number of "32 Byte Directory Entries"
1189-
for a drive letter on the corresponding hard disk.
1190-
1191-
- If it indicates 512, your disk layout is Classic (hd512).
1192-
- If it indicates 1024, your disk layout is Modern (hd1k).
1193-
1194-
Here is an example of checking the disk layout.
1195-
1196-
```
1197-
B>STAT E:DSK:
1198-
1199-
E: Drive Characteristics
1200-
65408: 128 Byte Record Capacity
1201-
8176: Kilobyte Drive Capacity
1202-
1024: 32 Byte Directory Entries
1203-
0: Checked Directory Entries
1204-
256: Records/ Extent
1205-
32: Records/ Block
1206-
64: Sectors/ Track
1207-
2: Reserved Tracks
1208-
```
1209-
1210-
It is critical that you include `DSK:` after the drive letter in the
1211-
`STAT` command line. The important line to look at is labeled "32 Byte
1212-
Directory Entries".
1213-
12141120
# Disk Types
12151121

12161122
## RAM & ROM Disks
@@ -1500,7 +1406,9 @@ There are two approaches to preparing disks for use by RomWBW.
15001406
including files to a disk.
15011407

15021408
This section of the document describes the manual process of preparing
1503-
empty disks that are ready for use by an operating system.
1409+
empty disks that are ready for use by an operating system.
1410+
This is somewhat analogous to partitioning and formatting of a hard disk
1411+
or doing a low level format of a floppy disk.
15041412

15051413
Alternatively, you can use the pre-built RomWBW disk images to quickly
15061414
create disk media that already has a large selection of files and
@@ -1728,12 +1636,7 @@ You need to initialize each slice for CP/M to use it.
17281636
This is somewhat analogous to doing a FORMAT operation on other systems,
17291637
and is done using the `CLRDIR` command.
17301638

1731-
This is covered in the section [Clearing (Formatting) Drives]
1732-
1733-
**WARNING**: Earlier versions of the `CLRDIR` application do not
1734-
appear to check for disk errors when it runs. If you attempt to run
1735-
`CLRDIR` on a drive that is mapped to a slice that does not actually fit
1736-
on the physical disk, it may behave erratically.
1639+
This is covered in the next section [Clearing (Formatting) Drives]
17371640

17381641
Assuming you want to use additional slices, you should initialize them
17391642
using the same process. You may need to reassign drive letters to
@@ -1742,11 +1645,57 @@ You can use the `ASSIGN` command to handle this.
17421645

17431646
## Post Disk Preparation
17441647

1745-
Once a disk (either floppy or hard disk) has been initialised and
1746-
formattted you may optionally;
1648+
Once a disk has been initialised you may need to do one or more of the following;
1649+
* Clear (Format) the drive
17471650
* Make the disk bootable
17481651
* Copy system (or other) files to the disk
17491652

1653+
### Clearing (Formatting) Drives
1654+
1655+
This is somewhat analogous to doing a FORMAT operation on other systems.
1656+
1657+
With RomWBW you use the `CLRDIR` command to do this.
1658+
This command is merely "clearing out" the directory space of the drive
1659+
referred to by a drive letter and setting up the new empty directory.
1660+
1661+
Refer to $doc_apps$ for more information on use of the `CLRDIR` command.
1662+
1663+
Since `CLRDIR` works on drive letters, make
1664+
absolutely sure you know what media and slice are assigned to that
1665+
drive letter before using `CLRDIR` because `CLRDIR` will wipe out any
1666+
pre-existing contents of the slice.
1667+
1668+
After `CLRDIR` completes, the drive should be ready to use by the operating
1669+
system via the drive letter assigned.
1670+
Start by using the `DIR` command on the drive.
1671+
This should return without error, but list no files.
1672+
1673+
Here is an example of using `CLRDIR`. In this example, the `ASSIGN`
1674+
command is used to show the current drive letter assignments. Then
1675+
the `CLRDIR` command is used to initialize the directory of drive 'G'
1676+
which is slice 2 of hard disk device IDE0 ("IDE0:2").
1677+
1678+
```
1679+
B>ASSIGN
1680+
1681+
A:=MD0:0
1682+
B:=MD1:0
1683+
C:=FD0:0
1684+
D:=FD1:0
1685+
E:=IDE0:0
1686+
F:=IDE0:1
1687+
G:=IDE0:2
1688+
H:=IDE0:3
1689+
1690+
B>CLDIR G:
1691+
CLRDIR Version 1.2B May 2024 by Max Scane
1692+
1693+
Warning - this utility will overwrite the directory sectors of Drive: G
1694+
Type CAPITAL Y to proceed, any key other key to exit. Y
1695+
Directory cleared.
1696+
B>
1697+
```
1698+
17501699
### Making a Disk Bootable
17511700

17521701
To make a disk bootable you will need to follow the specific instructions
@@ -1777,6 +1726,38 @@ system and application files to your disks.
17771726
Refer to [Transferring Files] for more information on getting
17781727
files onto your disks.
17791728

1729+
### Checking Disk Layout
1730+
1731+
If you are not sure which disk layout is used for your existing
1732+
media, you can use the CP/M 2.2 `STAT` command to display information
1733+
including the number of "32 Byte Directory Entries"
1734+
for a drive letter on the corresponding hard disk.
1735+
1736+
Note: For CP/M 3 the command is `SHOW [DRIVE]`
1737+
1738+
- If it indicates 512, your disk layout is Classic (hd512).
1739+
- If it indicates 1024, your disk layout is Modern (hd1k).
1740+
1741+
Here is an example of checking the disk layout.
1742+
1743+
```
1744+
B>STAT E:DSK:
1745+
1746+
E: Drive Characteristics
1747+
65408: 128 Byte Record Capacity
1748+
8176: Kilobyte Drive Capacity
1749+
1024: 32 Byte Directory Entries
1750+
0: Checked Directory Entries
1751+
256: Records/ Extent
1752+
32: Records/ Block
1753+
64: Sectors/ Track
1754+
2: Reserved Tracks
1755+
```
1756+
1757+
It is critical that you include `DSK:` after the drive letter in the
1758+
`STAT` command line. The important line to look at is labeled "32 Byte
1759+
Directory Entries".
1760+
17801761
# Disk Images
17811762

17821763
Since it would be quite a bit of work to transfer over all the files you

0 commit comments

Comments
 (0)