From 04df028ce4c5647a37564fdcc534a20775638b15 Mon Sep 17 00:00:00 2001 From: wwarthen Date: Wed, 29 Oct 2025 21:04:32 +0000 Subject: [PATCH] deploy: d0ac04045a4a9988a6cda80c6bade76adb9652d6 --- Applications/index.html | 141 ++++++++++++++++++++------------------- Catalog/index.html | 6 +- Hardware/index.html | 47 +++++++++---- Introduction/index.html | 2 +- SystemGuide/index.html | 2 +- UserGuide/index.html | 2 +- index.html | 4 +- search/search_index.json | 2 +- sitemap.xml.gz | Bin 127 -> 127 bytes 9 files changed, 117 insertions(+), 89 deletions(-) diff --git a/Applications/index.html b/Applications/index.html index 87538484..91b9253c 100644 --- a/Applications/index.html +++ b/Applications/index.html @@ -368,7 +368,7 @@

RomWBW Applications Guide \ Version 3.6 \ MartinR \& Phillip Summers () \ -22 Oct 2025

+29 Oct 2025

Summary

RomWBW is supplied with a suite of software applications that enhance the use of the system. Some of these applications have been written @@ -625,7 +625,7 @@ contents in hexadecimal.

Keyboard Echo

K - Echo any key-presses from the terminal. Press ‘ESC’ key to quit. This facility provides that any key stroke sent to the computer -will be echoed back to the terminal. File down loads will be echoed as +will be echoed back to the terminal. File downloads will be echoed as well while this facility is ‘on’.

Load Hex

L - Load a Intel Hex data via the terminal program. The load @@ -647,8 +647,8 @@ operation and is the companion to the I operation. Use clip leaded LEDs to confirm the data written.

Program Memory

P xxxx - Program memory location xxxx. This routine will allow you -to program a hexadecimal value ‘into memory starting at location xxxx. -Press ’Enter’ on a blank line to return to the Monitor prompt.

+to program a hexadecimal value into memory starting at location xxxx. +Press ‘Enter’ on a blank line to return to the Monitor prompt.

The limitation around programming memory is that it must be entered in hexadecimal. An alternative is to use the L command to load a program that has been assembled to a hex file on the remote computer.

@@ -739,14 +739,13 @@ directory.

TastyBASIC

TastyBASIC offers a minimal implementation of BASIC that is only 2304 bytes in size. It originates from Li-Chen Wang’s Palo Alto Tiny BASIC -from around 1976. It’s small size is suited the tiny memory capacities -of the time. This implementation is by Dimitri Theulings and his -original source can be found at -https://github.com/dimitrit/tastybasic.

+from around 1976. It’s small size suited the tiny memory capacities of +the time. This implementation is by Dimitri Theulings and his original +source can be found at https://github.com/dimitrit/tastybasic.

Features / Limitations

@@ -1034,10 +1033,10 @@ identify which character-input/output device is to be used as the serial device for transfer.

When your console is the serial device used for the transfer, no progress information is displayed as this would disrupt the x-modem file -transfer. If you use an alternate character-input/output devices as the +transfer. If you use an alternate character-input/output device as the serial device for the transfer then progress information will be displayed on the console device.

-

Due to different platform processor speeds, serials speeds and flow +

Due to different platform processor speeds, serial speeds and flow control capabilities the default console or serial device speed may need to be reduced for a successful transfer and flash to occur. The Set Console Interface/Baud code option at the Boot Loader can be used to @@ -1060,12 +1059,12 @@ that progress information can be displayed during the transfer.

Option ( \< ) - Revert to Original Baud Rate

Programming options

Option ( U ) - Begin Update

-

The will begin the update process. The updater will expect to start +

This will begin the update process. The updater will expect to start receiving an x-modem file on the serial device unit.

X-modem sends the file in packets of 128 bytes. The updater will cache 32 packets which is 1 flash sector and then write that sector to the flash device.

-

If using separate console, bank and sector progress information will +

If using separate console, bank and sector progress information will be shown

BANK 00 s00 s01 s02 s03 s04 s05 s06 s06 s07
 BANK 01 s00 s01 s02 s03 s04 s05 s06 s06 s07
@@ -1105,7 +1104,7 @@ ROM. Option ( 3 ) - Calculate and display CRC32 of a 1024k (2x512Kb)
 ROM.

 
Can be used to verify if a ROM image has been transferred and flashed
 correctly. Refer to the Tera Term section below for details on
-configuring the automatic display of a files CRC after it has been
+configuring the automatic display of a file’s CRC after it has been
 transferred.

 
In Windows, right clicking on a file should also give you a context menu
 option CRC SHA which will allow you to select a CRC32 calculation to be
@@ -1120,7 +1119,7 @@ be worthwhile if you are:

 
  • Doing development on RomWBW drivers
    • 
 
 
    Macros can be used to automate sending ROM updates or images and for my
-own purposed I have set up a separate macro for transferring each of the
+own purpose I have set up a separate macro for transferring each of the
 standard build ROM, my own custom configuration ROM and update ROM.
    
 
    An example macro file to send an *.upd file, using checksum mode and
 display the crc32 value of the transmitted file:
    
@@ -1217,13 +1216,17 @@ following guidelines.
    
 table if desired. Feedback to the RomWBW developers on these guidelines
 would be appreciated.
    
 
    Notes
    
-
    Notes * All testing was done with Tera Term x-modem, Forcing checksum
-mode using macros was found to give the most reliable transfer. *
-Partial writes can be completed with 39SF040 chips. Other chips
    
-require entire flash to be erased before being written. * An SBC V2-005
-MegaFlash or Z80 MBC required for 1mb flash support. The Updater assumes
-both chips are same type * Failure handling has not been tested. *
-Timing broadly calibrated on a Z80 SBC-v2 * Unabios not supported
    
+
      
+
    • All testing was done with Tera Term x-modem, Forcing checksum mode
+  using macros was found to give the most reliable transfer.
      • 
+
    • Partial writes can be completed with 39SF040 chips. Other chips
      
+  require entire flash to be erased before being written.
      • 
+
    • An SBC V2-005 MegaFlash or Z80 MBC required for 1mb flash support. The
+  Updater assumes both chips are same type
      • 
+
    • Failure handling has not been tested.
      • 
+
    • Timing broadly calibrated on a Z80 SBC-v2
      • 
+
    • Unabios not supported
      • 
+
    
 
    User Application
    
 
    RomWBW provides the facility for a user to build, include and execute
 their own custom application directly from the applications menu at
@@ -1252,7 +1255,7 @@ from the templated code.
    
 
    If required, the user application may make use of the Z80 interrupt
 system but if the user application wishes to rely on HBIOS functionality
 then it must adhere to the HBIOS framework for managing interupts.
-Alternatively, if the user appliction has no need for the HBIOS then it
+Alternatively, if the user application has no need for the HBIOS then it
 may use its own custom code for handling interrupts. In that case, a
 hard reset, rather than an HBIOS warm start, would be necessary to
 return control to RomWBW.
    
@@ -1447,12 +1450,12 @@ all contain essentially the same set of applications.
    
 
    For systems starting CP/M from a disk created from an image file, there
 are a small number of additional applications stored in the USER 2
 area of the disk. These applications do not form part of CP/M, but
-rather are small utilities used for test purposes during develpment
-work. They may, or may not, fuction correctly with any given hardware or
-software configuration. Documentation for these untilities is very
-limited, though the source files maybe found in the /Source folder. Note
-that these utiltites are not available when starting CP/M from the ROM
-image or from a floppy disk.
    
+rather are small utilities used for test purposes during development
+work. They may, or may not, function correctly with any given hardware
+or software configuration. Documentation for these utilities is very
+limited, though the source files may be found in the /Source folder.
+Note that these utiltites are not available when starting CP/M from the
+ROM image or from a floppy disk.
    
 
    A number of the CP/M applications available are described in more detail
 in the following sections, each with an indication as to whether that
 application may be found on the ROM-disk, a boot-disk, or both.
    
@@ -1825,21 +1828,20 @@ reboot of the system.
    
 
    The functionality is highly dependent on the capabilities of your
 system.
    
 
    Syntax
    
-
    CPUSPD [<speed>[,[<memws>][,[<iows>]]]
    
+
    CPUSPD [\<speed>[,[\<memws>][,[\<iows>]]]
    
 CPUSPD (W)armBoot
    
 CPUSPD (C)oldBoot
    
-
    <speed> is one of (H)alf, (F)ull, (D)ouble, or (Q)uad. <memws>
-is a number specifying the desired memory wait states. <iows> is a
-number specifying the desired I/O wait states.
    
+
    \<speed> is one of (H)alf, (F)ull, (D)ouble, or (Q)uad.
    
+
    \<memws> is a number specifying the desired memory wait states.
    
+
    \<iows> is a number specifying the desired I/O wait states.
    
 
    Usage
    
 
    Entering CPUSPD with no parameters will display the current CPU speed
 and wait state information of the running system. Wait state information
 is not available for all systems.
    
-
    To modify the running speed of a system, you can specify the
-** parameter. To modify either or both of the wait states,
-you can enter the desired number. Either or both of the wait state
-parameters may be omitted and the current wait state settings will
-remain in effect.
    
+
    To modify the running speed of a system, you can specify the \<speed>
+parameter. To modify either or both of the wait states, you can enter
+the desired number. Either or both of the wait state parameters may be
+omitted and the current wait state settings will remain in effect.
    
 
    Notes
    
 
    The ability to modify the running speed and wait states of a system
 varies widely depending on the hardware capabilities and the HBIOS
@@ -1914,18 +1916,18 @@ not operate correctly on non-RomWBW systems.
    
 
 
    The purpose of this utility is to allow the copying of whole disk slices
 from one disk slice to another slice
    
-
    This tool is only supported by RomWBW HBIOS, it uses HBIOS for all its
+
    This tool is only supported by RomWBW HBIOS; it uses HBIOS for all its
 disk IO. UNA UBIOS is not supported by this tool.
    
 
    This tool is running on CP/M 2.2 or 3.0 and has access to full 64kb of
 RAM, with a minimum of 48kb TPA
    
-
    This tool only works with hard disk devices, other media types like
+
    This tool only works with hard disk devices; other media types like
 floppy, are not supported at this time. This tool works across different
 hard disk device types, even of different physical type
    
 
    Both hd1k and hd512 are fully supported, however copying from one layout
 type to the other is not supported.
    
-
    During operation data is copied in a single read/write pass, data is not
-verified by default. If there is a write error, it will be reported, and
-operation will stop.
    
+
    During operation, data is copied in a single read/write pass; data is
+not verified by default. If there is a write error, it will be reported,
+and operation will stop.
    
 
    Syntax
    
 
    This tool operates at the disk level via RomWBW, thus all disk
 identifiers are in the RomWBW \<disk>.\<unit> format.
    
@@ -1941,7 +1943,7 @@ unattended mode, so you will not be asked to confirm the copy operation.
    
 U - Unattended. Will complete copy without confirmation from the user.
    
 V - Verify. Does an additional read and verify after write.
    
 
    Usage
    
-
    When run COPYSL will perform command line argument validation and
+
    When run, COPYSL will perform command line argument validation and
 display an error if they are illegal. Also any disk IO errors will cause
 COPYSL to exit.
    
 
    When specifying slice number(s) a check is made that the slice number is
@@ -2203,7 +2205,7 @@ in the RomWBW distribution.
    
 
 
 
    Most of the hardware platforms that run RomWBW support the use of
-EEPROMs – Electronically Erasable Programmable ROMs. The FLASH
+EEPROMs – Electrically Erasable Programmable ROMs. The FLASH
 application can be used to reprogram such ROMS in-situ (in-place), thus
 making it possible to upgrade ROMs without a programmer or even removing
 the ROM from your system.
    
@@ -2228,7 +2230,7 @@ file
    
 /N8VEMSBC: Force N8VEM SBC (v1, v2), Zeta (v1) SBC bank switching
    
 
    Usage
    
 
    To program your EEPROM ROM chip, first transfer the file to your RomWBW
-system. Then use the command FLASH WRITE *`*. The
+system. Then use the command FLASH WRITE\<filename>. The
 application will auto-detect the type of EEPROM chip you have, program
 it, and verify it.
    
 
    You can use the FLASH READ form of the command to read the ROM image
@@ -2546,7 +2548,7 @@ support most of the hardware variations included with RomWBW.
    
 
 
 
    Display or change the label of a disk slice.
    
-
    The label applied is only used as informational purposes, displayed by
+
    The label applied is only used for informational purposes, displayed by
 RomWBW when an OS is booted. It has no correlation with any OS volume
 label scheme that may exist. i.e. It does not affect the CP/M 3 disk
 label as applied by the SET command
    
@@ -2569,7 +2571,7 @@ means only bootable media.
    
 
    This will only display labels for the first 64 slices of any device.
 Slices higher than this are currently ignored.
    
 
    Only bootable RomWBW disk images have a label, which is defined by the
-OS which is booted. i.e. NZ-COM has a label of “ZSDOS 1.1” since that is
+OS that is booted. i.e. NZ-COM has a label of “ZSDOS 1.1” since that is
 the booted OS. Prior to RomWBW 3.5 all disk images were defined with the
 label “Unlabeled”.
    
 
    Etymology
    
@@ -2642,7 +2644,7 @@ may fail to discover ports that are ‘write-only’.
    
 
 
 
    System Configuration (SYSCONF) is a utility that allows system
-configuration to be set, dynamically and stored in NVRAM provided by an
+configuration to be set dynamically and stored in NVRAM provided by an
 RTC chip.
    
 
    (SYSCONF) is both a ROM utility (‘W’ Menu option), and a CP/M
 application. Noting however the CP/M application is not included on an
@@ -2672,8 +2674,6 @@ Commands:
   (R)eset - Init NVRAM to Defaults
   (H)elp [{SW}] - This help menu, or help on a switch
   e(X)it - Exit Configuration
-
-$

    When you run (SYSCONF) for the first time the NVRAM will be uninitialised, and can be initialised using the (R)eset command, which @@ -2688,7 +2688,7 @@ itself.

    will just report the missing hardware and exit immediately.

    To exit from the application use the (Q)uit command.

    Commands and Syntax

    -

    The following are the accepted commands, unless otherwise specified a +

    The following are the accepted commands, unless otherwise specified. A “Space” character is used to delimit parameters in the command.

    @@ -2769,7 +2769,7 @@ this replaces the (AUTO_CMD) variable defined in build configuratio - + @@ -2920,7 +2920,7 @@ that ZPM3 is in the file called CPM3.SYS, but it is normal for ZPM3.

    considered its own operating system. Each slice can be made bootable with its own system tracks.

    SYSCOPY uses drive letters to specify where to read/write the system -boot images. However, at startup, the boot loaded will require you to +boot images. However, at startup, the boot(?) loaded will require you to enter the actual disk device and slice to boot from. So, you need to be careful to pay attention to the device and slice that is assigned to a drive letter so you will know what to enter at the boot loader prompt. @@ -2930,13 +2930,13 @@ because the operating system is not loaded yet.

    currently assigned to a drive letter, you will need to assign a drive letter first.

    Not all disk formats include space for system tracks. Such disk formats -cannot contains a system boot image and, therefore, cannot be made +cannot contain a system boot image and, therefore, cannot be made bootable. The best example of such disk formats are the ROM and RAM disks. To maximize usable file space on these drives, they do not have -system tracks. Obviously, ROM operating system is supported by choosing -a ROM operating system at the boot loader prompt. Any attempt to write a -system boot image to disk media with no system tracks will cause SYSCOPY -to fail with an error message.

    +system tracks. Obviously, the ROM operating system is supported by +choosing a ROM operating system at the boot loader prompt. Any attempt +to write a system boot image to disk media with no system tracks will +cause SYSCOPY to fail with an error message.

    The system boot images are paired with the ROM version in your system. So, you must take care to update the system tracks of any bootable disk when you upgrade your ROM firmware.

    @@ -3047,7 +3047,8 @@ displays the value of the counter.

    TIMER /Z

    Usage

    Use TIMER to display the current value of the counter.

    -

    Use TIMER /C to display the value of the counter continuously.

    +

    Use TIMER /C to display the value of the counter continuously. Press +any key to exit.

    Use TIMER /Z to zero the seconds counter.

    The display of the counter will be something like this:

    2859 Ticks 24.18 Seconds 0:00:24.18 HH:MM:SS

    @@ -3063,7 +3064,8 @@ which is typically 50Hz. This means that the seconds fraction will increment 0.02 seconds with each timer tick.

    The primary use of the TIMER application is to test the system timer functionality of your system. However, it can be used to capture the -value before and after some process you want to measure elapsed runtime.

    +value before and after some process you want to measure the elapsed +runtime of.

    Etymology

    The TIMER command is an original product and the source code is provided in the RomWBW distribution.

    @@ -3089,7 +3091,7 @@ provided in the RomWBW distribution.

    If your RomWBW system has a sound card based on either an AY-3-8190 or YM2149F sound chip, you can use the TUNE application to play PT or MYM sound files.

    -

    Note: TUNE will detect an AY-3-8910/YM2149 Sound Module re-gardless of +

    Note: TUNE will detect an AY-3-8910/YM2149 Sound Module regardless of whether support for it is included in the RomWBW HBIOS configuration

    Syntax

    TUNE<filename> **

    @@ -3433,10 +3435,13 @@ files between systems using a serial port.

    XM L<library> <filename>
    XM LK<library> <filename>
    XM R<filename>

    -

    The following may be added to the action codes: | S: Send a file | -L: Send a file from a library | R: Receive a file | K: Use 1K -blocksize (send operations) | C: Force use of checksum (receive -operations) | X: Force 128-byte protocol (receive operations) | +

    The following may be added to the action codes:

    +

    S: Send a file
    +L: Send a file from a library
    +R: Receive a file
    +K: Use 1K blocksize (send operations)
    +C: Force use of checksum (receive operations)
    +X: Force 128-byte protocol (receive operations)
    0-9: Specifies HBIOS character unit for transfers

    <filename> is the name of a file to send or receive

    <library> is the name of a library (.lbr) to extract a file to send

    @@ -3465,7 +3470,7 @@ the following:

  • On your host computer, specify the name to assign to the received - file and initiate and XModem receive operation.

    + file and initiate an XModem receive operation.

    • Please refer to the documentation of your host computer’s terminal @@ -3541,7 +3546,7 @@ the following:

  • Enter one of the ZMD receive commands specifying the name you want to give to the received file (no filename required for ZModem - transfers).

    + transfers).[“ZMD does not do ZModem transfers”]

  • On your host computer select a file to send and initiate an XModem diff --git a/Catalog/index.html b/Catalog/index.html index 98d04c3e..e836c7f5 100644 --- a/Catalog/index.html +++ b/Catalog/index.html @@ -336,7 +336,7 @@

    RomWBW Disk Catalog \ Version 3.6 \ Mark Pruden \& Mykl Orders () \ -22 Oct 2025

    +29 Oct 2025

    RomWBW Distribution File Catalog

    This document is a reference to the files found on the disk media distributed with RomWBW. Specifically, RomWBW provides a set of floppy @@ -3025,6 +3025,10 @@ instructions.

    • + + + + diff --git a/Hardware/index.html b/Hardware/index.html index 353b9b51..d888aa2f 100644 --- a/Hardware/index.html +++ b/Hardware/index.html @@ -396,7 +396,7 @@

    RomWBW Hardware \ Version 3.6 \ Wayne Warthen (wwarthen@gmail.com) \ -22 Oct 2025

    +29 Oct 2025

    Overview

    Supported Platforms

    This section contains a summary of the system configuration target for @@ -1252,17 +1252,18 @@ of the SIO ports, for ease of use with modern computers.

    TimoutTimeout Timeout in seconds in the range 0-15, 0 = immediate
    COLOR VDU TEST
    Z80TYPE.COMZ80 Chip Variant Detection
    ZEXALL.COM Z80 Instruction Set Exerciser

    Supported Hardware

    Notes: