Added first RomWBW App help files
This commit is contained in:
parent
20d9a123cb
commit
b325379050
54
romwbw/01assign.help
Normal file
54
romwbw/01assign.help
Normal file
@ -0,0 +1,54 @@
|
|||||||
|
|
||||||
|
///1ASSIGN
|
||||||
|
|
||||||
|
Syntax:
|
||||||
|
|
||||||
|
ASSIGN D:[=[{D:|<device>[<unitnum>]:[<slicenum>]}]][,...]
|
||||||
|
|
||||||
|
Explanation:
|
||||||
|
|
||||||
|
Using the ASSIGN command, on a RomWBW system the drive
|
||||||
|
letter assignments can be listed or changed.
|
||||||
|
|
||||||
|
Drive letters can be swapped, assigned to devices or slices
|
||||||
|
or unassigned.
|
||||||
|
|
||||||
|
Multiple (un)assignments can be concatenated using commas.
|
||||||
|
|
||||||
|
A device or slice can only be assigned to a single drive
|
||||||
|
letter.
|
||||||
|
|
||||||
|
Author:
|
||||||
|
|
||||||
|
Wayne Warthen (wwarthen@gmail.com)
|
||||||
|
|
||||||
|
///2Examples
|
||||||
|
|
||||||
|
A>ASSIGN
|
||||||
|
|
||||||
|
Display all active drive assignments
|
||||||
|
|
||||||
|
A>ASSIGN /?
|
||||||
|
|
||||||
|
Display version and usage
|
||||||
|
|
||||||
|
A>ASSIGN /L
|
||||||
|
|
||||||
|
Display all possible devices
|
||||||
|
|
||||||
|
A>ASSIGN C:=D:
|
||||||
|
|
||||||
|
Swaps C: and D:
|
||||||
|
|
||||||
|
A>ASSIGN C:=FD0:
|
||||||
|
|
||||||
|
Assign C: to floppy unit 0
|
||||||
|
|
||||||
|
A>ASSIGN C:=IDE0:1,D:=IDE0:2,E:=FD0:
|
||||||
|
|
||||||
|
Assign C: to IDE unit0, slice 1, D: to IDE unit0, slice2
|
||||||
|
and E: to floppy unit 0
|
||||||
|
|
||||||
|
A>ASSIGN C:=
|
||||||
|
|
||||||
|
Unassign C:
|
47
romwbw/02mode.help
Normal file
47
romwbw/02mode.help
Normal file
@ -0,0 +1,47 @@
|
|||||||
|
|
||||||
|
///1MODE
|
||||||
|
|
||||||
|
Syntax:
|
||||||
|
|
||||||
|
MODE /?
|
||||||
|
MODE COM<n>:
|
||||||
|
[<baud>[,<parity>[,<databits>[,<stopbits>]]]] [/P]
|
||||||
|
|
||||||
|
Explanation:
|
||||||
|
|
||||||
|
MODE is used to display and/or modify the configuration
|
||||||
|
of a serial device of a RomWBW system.
|
||||||
|
|
||||||
|
<baud> is numerical baudrate
|
||||||
|
<parity> is (N)one, (O)dd, (E)ven, (M)ark, or (S)pace
|
||||||
|
<databits> is number of data bits, typically 7 or 8
|
||||||
|
<stopbits> is number of stop bits, typically 1 or 2
|
||||||
|
/P prompts the user prior to setting new configuration
|
||||||
|
|
||||||
|
Notes:
|
||||||
|
|
||||||
|
Parameters not provided will remain unchanged.
|
||||||
|
The device must support the specified configuration.
|
||||||
|
|
||||||
|
Author:
|
||||||
|
|
||||||
|
Wayne Warthen (wwarthen@gmail.com)
|
||||||
|
|
||||||
|
///2Examples
|
||||||
|
|
||||||
|
A>MODE /?
|
||||||
|
|
||||||
|
Display command usage
|
||||||
|
|
||||||
|
A>MODE
|
||||||
|
|
||||||
|
Display configuration of all serial ports
|
||||||
|
|
||||||
|
A>MODE COM0:
|
||||||
|
|
||||||
|
Display configuration of serial unit 0
|
||||||
|
|
||||||
|
A>MODE COM1: 9600,N,8,1
|
||||||
|
|
||||||
|
Set serial unit 1 configuration
|
||||||
|
|
22
romwbw/03syscopy.help
Normal file
22
romwbw/03syscopy.help
Normal file
@ -0,0 +1,22 @@
|
|||||||
|
|
||||||
|
///1SYSCOPY
|
||||||
|
|
||||||
|
Syntax:
|
||||||
|
|
||||||
|
SYSCOPY <dest>[=<src>]
|
||||||
|
|
||||||
|
Explanation:
|
||||||
|
|
||||||
|
SYSCOPY is used to copy a system image to or from the re-
|
||||||
|
served tracks of a disk on a RomWBW system.
|
||||||
|
|
||||||
|
This is used for RomWBW adaptions of CP/M 2.2 and CP/M 3.
|
||||||
|
|
||||||
|
<dest> and <src> may be a drive or a file reference
|
||||||
|
|
||||||
|
If <src> is not specified, the system image will be read
|
||||||
|
from the current drive
|
||||||
|
|
||||||
|
Author:
|
||||||
|
|
||||||
|
Wayne Warthen (wwarthen@gmail.com)
|
17
romwbw/04talk.help
Normal file
17
romwbw/04talk.help
Normal file
@ -0,0 +1,17 @@
|
|||||||
|
|
||||||
|
///1TALK
|
||||||
|
|
||||||
|
Syntax:
|
||||||
|
|
||||||
|
TALK TTY:|CRT:|BAT:|UC1:
|
||||||
|
|
||||||
|
Explanation:
|
||||||
|
|
||||||
|
TALK is a minimal tool to talk directly to a character
|
||||||
|
device.
|
||||||
|
|
||||||
|
Use Ctrl+Z to exit TALK.
|
||||||
|
|
||||||
|
Author:
|
||||||
|
|
||||||
|
Wayne Warthen (wwarthen@gmail.com)
|
99
romwbw/05fat.help
Normal file
99
romwbw/05fat.help
Normal file
@ -0,0 +1,99 @@
|
|||||||
|
|
||||||
|
///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.
|
||||||
|
|
37
romwbw/06tune.help
Normal file
37
romwbw/06tune.help
Normal file
@ -0,0 +1,37 @@
|
|||||||
|
|
||||||
|
///1TUNE
|
||||||
|
|
||||||
|
Syntax:
|
||||||
|
|
||||||
|
TUNE <filename>
|
||||||
|
|
||||||
|
Explanation:
|
||||||
|
|
||||||
|
TUNE plays PT2/PT3/MYM sound files.
|
||||||
|
|
||||||
|
<filename> of sound file to load and play
|
||||||
|
Filename extension determines file type
|
||||||
|
(.PT2, .PT3, or .MYM)
|
||||||
|
|
||||||
|
Notes:
|
||||||
|
|
||||||
|
- Supports AY-3-8910, YM2149, etc.
|
||||||
|
- Max Z80 CPU clock is about 8 MHz or sound chip will not
|
||||||
|
handle speed.
|
||||||
|
- Higher CPU clock speeds are possible on Z180 because extra
|
||||||
|
I/O wait states are added during I/O to sound chip.
|
||||||
|
- Uses hardware timer support on systems that support a timer.
|
||||||
|
Otherwise, a delay loop calibrated to CPU speed is used.
|
||||||
|
- Delay loop is calibrated to CPU speed, but it does not com-
|
||||||
|
pensate for time variations in each quark loop resulting
|
||||||
|
from data decompression.
|
||||||
|
An average quark processing time is assumed in each loop.
|
||||||
|
- Most sound files originally targeted MSX or ZX Spectrum
|
||||||
|
which used 1.7897725 MHz and 1.773400 MHz respectively for
|
||||||
|
the PSG clock. For best sound playback, PSG should be run at
|
||||||
|
approx. this clock rate.
|
||||||
|
|
||||||
|
Author:
|
||||||
|
|
||||||
|
Wayne Warthen (wwarthen@gmail.com)
|
||||||
|
|
Loading…
Reference in New Issue
Block a user