100 lines
3.3 KiB
Plaintext
100 lines
3.3 KiB
Plaintext
|
|
||
|
|
///1FAT
|
||
|
|
|
||
|
|
Syntax:
|
||
|
|
|
||
|
|
FAT DIR <path>
|
||
|
|
FAT COPY <src> <dst>
|
||
|
|
FAT REN <from> <to>
|
||
|
|
FAT DEL <path>[<file>|<dir>]
|
||
|
|
FAT MD <path>
|
||
|
|
FAT FORMAT <drv>
|
||
|
|
|
||
|
|
CP/M filespec: <d>:FILENAME.EXT (<d> is CP/M drive letter)
|
||
|
|
FAT filespec: <u>:/DIR/FILENAME.EXT (<u> is device #)
|
||
|
|
|
||
|
|
Explanation:
|
||
|
|
|
||
|
|
FAT is used to manipulate and exchange files with a FAT
|
||
|
|
(DOS) filesystem. It runs on any HBIOS hosted CP/M implemen-
|
||
|
|
tation.
|
||
|
|
|
||
|
|
The first parameter defines the action to perform on the FAT
|
||
|
|
filesystem.
|
||
|
|
|
||
|
|
Author:
|
||
|
|
|
||
|
|
Wayne Warthen (wwarthen@gmail.com)
|
||
|
|
|
||
|
|
///2Examples
|
||
|
|
|
||
|
|
A>FAT DIR 2:/
|
||
|
|
|
||
|
|
Shows the root directory of device 2
|
||
|
|
|
||
|
|
A>FAT COPY C:TEXT.TXT 2:/BOOK/
|
||
|
|
|
||
|
|
Copy the file TEXT.TXT from CP/M drive C: to the directory
|
||
|
|
/BOOK on device 2.
|
||
|
|
|
||
|
|
A>FAT COPY 2:/BOOK/TEXT.TXT C:
|
||
|
|
|
||
|
|
Vice versa
|
||
|
|
|
||
|
|
A>FAT REN
|
||
|
|
A>FAT DEL
|
||
|
|
A>FAT MD
|
||
|
|
A>FAT FORMAT
|
||
|
|
(not yet finished)
|
||
|
|
|
||
|
|
///3Notes
|
||
|
|
|
||
|
|
Partitioned or non-partitioned media is handled automatical-
|
||
|
|
ly. A floppy drive is a good example of a non-partitioned
|
||
|
|
FAT filesystem and will be recognized. Larger media will
|
||
|
|
typically have a partition table which will be recognized by
|
||
|
|
the application to find the FAT filesystem.
|
||
|
|
|
||
|
|
Although RomWBW-style CP/M media does not know anything
|
||
|
|
about partition tables, it is entirely possible to have
|
||
|
|
media that has both CP/M and FAT file systems on it. This
|
||
|
|
is accomplished by creating a FAT filesystem on the media
|
||
|
|
that starts on a track beyond the last track used by CP/M.
|
||
|
|
Each CP/M slice on a media will occupy a little over 8MB.
|
||
|
|
So, make sure to start your FAT partition beyond
|
||
|
|
(slice count) * 8MB.
|
||
|
|
|
||
|
|
The application infers whether you are attempting to refer-
|
||
|
|
ence a FAT or CP/M filesystem via the drive specifier (char
|
||
|
|
before ':').
|
||
|
|
A numeric drive character specifies the HBIOS disk unit num-
|
||
|
|
ber for FAT access. An alpha (A-P) character indicates a
|
||
|
|
CP/M file system access targeting the specified drive let-
|
||
|
|
ter. If there is no drive character specified, the current
|
||
|
|
CP/M filesystem and current CP/M drive is assumed.
|
||
|
|
For example:
|
||
|
|
|
||
|
|
2:README.TXT refers to FAT file README.TXT on disk unit #2
|
||
|
|
C:README.TXT refers to CP/M file README.TXT on CP/M drive C
|
||
|
|
README.TXT refers to README.TXT on current CP/M drive
|
||
|
|
|
||
|
|
Files with SYS, HIDDEN, or R/O only attributes are not given
|
||
|
|
any special treatment. Such files are found and processed
|
||
|
|
like any other file. However, any attempt to write to a
|
||
|
|
read-only file will fail and the application will abort.
|
||
|
|
|
||
|
|
It is not currently possible to reference CP/M user areas
|
||
|
|
other than the current user. To copy files to alternate user
|
||
|
|
areas, you must switch to the desired user number first or
|
||
|
|
use an additional step to copy the file to the desired user
|
||
|
|
area.
|
||
|
|
|
||
|
|
Accessing FAT filesystems on a floppy requires the use of
|
||
|
|
RomWBW HBIOS v2.9.1-pre.13 or greater.
|
||
|
|
|
||
|
|
Files written are not verified.
|
||
|
|
|
||
|
|
Wildcard matching in FAT filesystems is a bit unusual as im-
|
||
|
|
plemented by FatFs. See FatFs documentation.
|
||
|
|
|