Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
software:firmwareos:zsos:start [2018/06/10 03:20]
admin
software:firmwareos:zsos:start [2018/07/18 19:17] (current)
admin
Line 1: Line 1:
-<note warning>​The content of the page below is being actively edited ahead of the release of ZSOS 0.30 and may be incomplete/​not accurate</​note>​ 
- 
 ====== ZSOS ====== ====== ZSOS ======
 +
 ===== Overview ===== ===== Overview =====
-ZSOS (Z80 SBC OS) is a CP/M 3 distribution ​with a BIOS customized ​for the S100Computers.com Z80 Single Board Computer. John Monahan of the S100Computers.com website designed this board in late 2015 as a "​starter board" for new users to "​bootstrap" ​a new S-100 system from scratch. The S-100 Z80 SBC contains a Z80 CPU, ROM, RAM, an interface for an IDE drive or IDE→CF adapter, and a USB-based ​terminal. Typically in the past, these functions would have required a set of S-100 boards - the Z80 CPU (w ROM socket), a RAM card, and a Serial I/O card.+ 
 +ZSOS (Z80 SBC OS) is a CP/M 3 distribution for the S100Computers.com Z80 Single Board Computer. John Monahan of the S100Computers.com website designed this board as a "​starter board" for new users to "​bootstrap" ​an S-100 system from scratch. The S-100 Z80 SBC contains a Z80 CPU, ROM, RAM, an interface for an IDE drive or IDE→CF adapter, and a USB-based ​serial connection. Typically in the past, these functions would have required a set of S-100 boards - the Z80 CPU (w ROM socket), a RAM card, a CF/IDE storage ​card, and a Serial I/O card.
  
 **For a complete description of the board including build instructions** visit the [[http://​www.s100computers.com/​My System Pages/SBC Z80 Board/SBC Z80 CPU Board.htm|S100Computers.com Z80 SBC Page]]. **For a complete description of the board including build instructions** visit the [[http://​www.s100computers.com/​My System Pages/SBC Z80 Board/SBC Z80 CPU Board.htm|S100Computers.com Z80 SBC Page]].
  
-**For questions or discussion about this board or ZSOS**, please visit the [[https://​groups.google.com/​forum/#​!forum/​s100computers|S100Computers Google Group]] - which John M. has kindly asked we used for all discussion related to the S100Computers.com boards.+**For questions or discussion about this board or ZSOS**, please visit the [[https://​groups.google.com/​forum/#​!forum/​s100computers|S100Computers Google Group]] 
 + - which John M. has kindly asked we used for all discussion related to the S100Computers.com boards.
  
 ===== Credits ===== ===== Credits =====
-These images are based on John Monahan'​s original CP/M 3 BIOS for the S100Computers Z80 CPU & IDE boards, with the addition of contributions by David Fry for the LBA addressing code, Dave Mehaffy (aka yoda) for details of image creation, and testing by the members of the S100Computers Google Group.+ 
 +These images are based on John Monahan'​s original CP/M 3 BIOS for the S100Computers Z80 CPU & IDE boards, with the addition of contributions by David Fry for the LBA addressing code & CF compatibility improvements, Dave Mehaffy (aka yoda) for details of image creation, and testing by the members of the S100Computers Google Group.
  
 ===== Downloads ===== ===== Downloads =====
 +
 ==== ZSOS Distribution ==== ==== ZSOS Distribution ====
-=== Upcoming Versions === 
-ZSOS v0.30 is undergoing final preparations for release. ​ Check back here soon! 
  
 === Latest/​Current Version === === Latest/​Current Version ===
-**{{:​software:​firmwareos:​zsos:​zsos-0.11-11mar2016.zip|ZSOS v0.11 (11-MAR-2016)}}  ** +{{:​software:​firmwareos:​zsos:​zsos-0.30.zip|ZSOS v0.30 (28-MAY-2018)}} 
-  * Non-banked CP/M 3 +  ​* ​Choice of 2 images files: 
-  * 44K Transient Program Area **//(updated!)//​ ** +    * Non-banked CP/M 3 w/43K Transient Program Area 
-  * Includes support for a single drive on the CF card (A:) +    ​Banked CP/M 3 w/53K Transient Program Area 
-      * User Area 0: CP/M 3 Base Files +  * Includes support for a single drive on the CF card (A:)     ​ 
-      * User Area 1: <​Reserved for future S100Computers board utilities folder> +     ​* User Area 0: CP/M 3 Base Files 
-      * User Area 2: SuperSoft Utilities +     ​* User Area 1: XMODEM + Kermit + MBASIC 5.29 
-      * User Area 3: DDTZ Debugger (will need to be built from source) +     ​* User Area 2: SuperSoft Utilities 
-      * User Area 4: BDS Tiny C +     ​* User Area 3: DDTZ Debugger (will need to be built from source) 
-      * User Area 5: Games **//​(new!)//​ ** +     ​* User Area 4: BDS Tiny C 
-      * User Area 6: Turbo Pascal 3.0 **//​(new!)//​ ** +     ​* User Area 5: Games 
-      * User Area 7: Development Utilities ​//​updated!//​ +     ​* User Area 6: Turbo Pascal 3.0 
-      * User Area 8: <​Available for additional user files> ​**//​(updated!)//​ ** +     ​* User Area 7: Development Utilities 
-      * User Area 9: <​Available for additional user files> **//​(updated!)//​ ** +     ​* User Area 8: <​Available for additional user files> 
-  * **//Additional Changes//**  +     ​* User Area 9: <​Available for additional user files> 
-    * CPM3.SYS set to Read Only/​System ​ +  ​Latest Windows cpmtools included in the .zip, along with Windows batch file and linux script to load User Areas 8 & 9 
-    * CP/M 3 Base Files in User Area 0 set to System +  * Additional Changes 
-    * Console Character ​I/O Routines (CHARIO3.ASM) updated to output all ASCII characters to the DLP USB Device This fixes VT100 programs.+    * Improved CF card compatibiliy ​Thanks ​to David Fry for the debugging work to make this happen.  ​ 
 +    * CP/M I/O devices respect the IOBYTE switches on the Z80 SBC at boot, and can be remapped on the fly after boot. 
 +    * Added SWEEP.EXE to User Area 0 
 +    * Removed some files from User Area 0 that only worked under SIMH
   * Latest Windows cpmtools included in the .zip, along with batch files and linux script to load User Areas 8 & 9   * Latest Windows cpmtools included in the .zip, along with batch files and linux script to load User Areas 8 & 9
  
 === Old Versions === === Old Versions ===
 +{{:​software:​firmwareos:​zsos:​zsos-0.11-11mar2016.zip|ZSOS v0.11 (11-MAR-2016)}} \\
 {{:​software:​firmwareos:​zsos:​zsos-0.10-02feb2016.zip|ZSOS v0.10 (02-FEB-2016)}} {{:​software:​firmwareos:​zsos:​zsos-0.10-02feb2016.zip|ZSOS v0.10 (02-FEB-2016)}}
  
 ==== Source Code & Development Environment ==== ==== Source Code & Development Environment ====
 +
 +FIXME
 +
 The ZSOS .zip file includes copies of all files that were modified from John M's original CP/M 3 files. For a description of the tools used to create these image files (without even having access to the Z80 SBC hardware!) see the [[:​software:​firmwareos:​zsos:​devenv|ZSOS Development Environment page]] (Under Construction) The ZSOS .zip file includes copies of all files that were modified from John M's original CP/M 3 files. For a description of the tools used to create these image files (without even having access to the Z80 SBC hardware!) see the [[:​software:​firmwareos:​zsos:​devenv|ZSOS Development Environment page]] (Under Construction)
  
 +FIXME
 ===== Setting Up ZSOS on the S100Computers Z80 SBC ===== ===== Setting Up ZSOS on the S100Computers Z80 SBC =====
 +
 ==== Overview ==== ==== Overview ====
-This writeup covers the installation initial bring-up of the ZSOS CP/M 3 distribution on the [[http://​www.s100computers.com/​My%20System%20Pages/​SBC%20Z80%20Board/​SBC%20Z80%20CPU%20Board.htm|S100Computers.com Z80 SBC]]. ​ Please read through this carefully, many common questions/​pitfalls are addressed.+ 
 +This writeup covers the installation initial bring-up of the ZSOS CP/M 3 distribution on the [[http://​www.s100computers.com/​My%20System%20Pages/​SBC%20Z80%20Board/​SBC%20Z80%20CPU%20Board.htm|S100Computers.com Z80 SBC]]. Please read through this carefully, many common questions/​pitfalls are addressed.
  
 The instructions below assume the following: The instructions below assume the following:
 +
   * The builder has completed the steps outlined on the [[http://​www.s100computers.com/​My%20System%20Pages/​SBC%20Z80%20Board/​SBC%20Z80%20CPU%20Board.htm|board build page]].   * The builder has completed the steps outlined on the [[http://​www.s100computers.com/​My%20System%20Pages/​SBC%20Z80%20Board/​SBC%20Z80%20CPU%20Board.htm|board build page]].
   * The board booting and is operating properly with the SBC Monitor input/​output working on the console device that the builder intends to use prior to trying to run ZSOS.   * The board booting and is operating properly with the SBC Monitor input/​output working on the console device that the builder intends to use prior to trying to run ZSOS.
   * The builder plans to operate SBC using the onboard RAM and ROM chips (configuration of jumpers for other RAM/ROM boards is outside the scope of this document).   * The builder plans to operate SBC using the onboard RAM and ROM chips (configuration of jumpers for other RAM/ROM boards is outside the scope of this document).
-  * The only boards in the S-100 bus are the Z80 SBC and //​optionally//​ the [[http://​www.s100computers.com/​My%20System%20Pages/​Console%20IO%20Board/​Console%20IO%20Board.htm|Propeller Console Board]] +  * The only boards in the S-100 bus are the Z80 SBC and //​optionally// ​ the [[http://​www.s100computers.com/​My%20System%20Pages/​Console%20IO%20Board/​Console%20IO%20Board.htm|Propeller Console Board]] 
-   + 
-It is recommended that the user start with the '​nonbanked'​ ZSOS image which is somewhat simpler in internal operation than the '​banked'​ image. ​ The jumper configuration shown below is valid for either image. +It is recommended that the user start with the '​nonbanked'​ ZSOS image which is somewhat simpler in internal operation than the '​banked'​ image. The jumper configuration shown below is valid for either image. 
-  ​+ 
 +==== SBCMON Monitor ROM Version ==== 
 +**For use with ZSOS v0.30 and higher, the Z80 SBC should be configured with the SBCMON Monitor ROM version 2.3 or higher.** ​ Updates were made in SBCMON 2.3 to allow the banked version of ZSOS to boot reliably and to improve CF card compatibility. ​ SBCMON can be found on the [[http://​www.s100computers.com/​My%20System%20Pages/​SBC%20Z80%20Board/​SBC%20Z80%20CPU%20Board.htm|S100Computers Z80 SBC page]]. 
 ==== CompactFlash Card Adapter Configuration/​Installation ==== ==== CompactFlash Card Adapter Configuration/​Installation ====
-The recommended CompactFlash (CF) -> IDE adapter is the [[http://​www.sybausa.com/​index.php?​route=product/​product&​product_id=612|SYBA IDE to CF Adapter, Direct Insertion, part number SD-CF-IDE-DI.]] It can be purchased from [[https://​www.amazon.com/​Syba-SD-CF-IDE-Connects-3-5-Inch-Interface/​dp/​B000YUMLPI|Amazon]],​ eBay, and other sellers.+ 
 +The recommended CompactFlash (CF) → IDE adapter is the [[http://​www.sybausa.com/​index.php?​route=product/​product&​product_id=612|SYBA IDE to CF Adapter, Direct Insertion, part number SD-CF-IDE-DI.]] It can be purchased from [[https://​www.amazon.com/​Syba-SD-CF-IDE-Connects-3-5-Inch-Interface/​dp/​B000YUMLPI|Amazon]],​ eBay, and other sellers.
  
 Jumper JP3 on the adapter should be set to the '​2-3'​ position to allow the adapter to be powered from Pin 20 of the IDE connector, as shown in the photo below. Jumper JP3 on the adapter should be set to the '​2-3'​ position to allow the adapter to be powered from Pin 20 of the IDE connector, as shown in the photo below.
  
-==== Compact Flash Card Selection ==== +==== Compact Flash Card Selection ​& Write Testing ​==== 
-Updates included in the most recent versions of the SBC Monitor ROM & ZSOS have greatly improved CF card compatibility with the Z80 SBC, so most cards should work at this point.+ 
 +Updates included in the most recent versions of the SBC Monitor ROM & ZSOS have greatly improved CF card **read** ​compatibility with the Z80 SBC.  However some CF cards may still have problems with **writes**. ​ Following a successful boot of ZSOS, the following command can be run at the CP/M A> prompt to verify writes are working:​\\ 
 +<​key>''​PIP A:​[VG10]=A:​*.*[G1]''</​key> ​ \\ 
 +The expected output should be a list of files copied, and then a return to the A> prompt with no errors. The copied files can then be deleted using the following commands:​\\ 
 +<​key>''​USER 10''</​key>​ \\ 
 +<​key>''​ERASE *.*''</​key>​ \\ 
 +<​key>''​USER 0''</​key> ​
  
 ==== Board Configuration ==== ==== Board Configuration ====
-Click on the image below for an ultra-high resolution photo of the board. ​ White jumpers have been installed to make the jumper configurations across the board clearly visible. 
  
-===  IDE Pin 20 Power === +Click on the image below for an ultra-high resolution photo of the board. White jumpers have been installed to make the jumper configurations across the board clearly visible.
-If using the recommended SYBA SD-CF-IDE-DI adapter, Jumper P104 can be installed ​on the Z80 SBC to send power to the adapter via IDE Pin 20.  See photo below.+
  
-<note warning>​**If using a different CF->IDE adapter than the recommended part, the user __must__ confirm that the adapter can accept power over IDE Pin 20 and pass it to the CF card prior to installing this jumper ​Accidental connection of this optional power signal to ground through an adapter that grounded IDE Pin 20 could result in damage to the user's S-100 hardware!**<​/note>+[[https://​www.retrobrewcomputers.org/lib/​exe/​fetch.php?​media=software:​firmwareos:​zsos:​z80_sbc_w_jumpers.jpg|{{:​software:​firmwareos:​zsos:​z80_sbc_w_jumpers.jpg?​direct&​600 ​ |z80_sbc_w_jumpers.jpg}}]]
  
-FIXME Add photo FIXME+=== IDE Pin 20 Power === 
 + 
 +If using the recommended SYBA SD-CF-IDE-DI adapter, Jumper P104 can be installed on the Z80 SBC to send power to the adapter via IDE Pin 20. See photo below. 
 + 
 +<note warning>​**If using a different CF→IDE adapter than the recommended part, the user __must__ ​ confirm that the adapter can accept power over IDE Pin 20 and pass it to the CF card prior to installing this jumper. Accidental connection of this optional power signal to ground through an adapter that grounded IDE Pin 20 could result in damage to the user's S-100 hardware!**</​note>​ 
 + 
 +{{:​software:​firmwareos:​zsos:​p104_ide_power.jpg?​nolink&​|p104_ide_power.jpg}}
  
 === Recommended Wait State Configurations === === Recommended Wait State Configurations ===
-There are various speeds of Z80 CPU and 8255 parallel port interface chip available. ​ The following table shows recommended I/O wait state configurations for maximum CF card compatibility. ​ While developing ZSOS 0.30, 1 wait state was needed to achieve stable operation with an 8 MHz Z80 and a 5 MHz 8255.  The data in the table is extrapolated from this experience to account for different combinations of Z80 oscillator clock and 8255 speed rating. ​ Starting with a 4 MHz oscillator in U46 and moving to faster speeds later on is a good practice when bringing up a new board for the first time. 
  
-<note important>​Not all of the combinations below have been tested - the numbers below are are a reasonable starting pointIt is possible more wait states could be needed ​for some combinations. ​ It is also possible that less might work for specific 8255'​s/​CF cards ​Please report back via the S100Computers Google Group with any experiences in this area so the table can be updated.</​note>​+There are various speeds ​of Z80 CPU and 8255 parallel port interface chip availableThe following table shows recommended I/O wait state configurations ​for maximum ​CF card compatibilityWhile developing ZSOS 0.30, 1 wait state was needed to achieve stable operation ​with an 8 MHz Z80 and a 5 MHz 8255
  
-^ Z80 Clock Speed (U46) ^ 8255 Rated Speed ^ # of I/O Wait States ^ Tested? ^ +<note important>​The data in the table below is based on an extensive set of tests conducted with 3 different CF cards, ​4 MHz and 8 MHz CPU oscillators,​ and 5 MHz and 8 MHz 8255 chips. However, chip to chip and system-to-system verification may still impact timings and these numbers should only be considered as a starting point.</​note>​
-|  ​4 MHz  ​| ​ 5 or 8 MHz  ​| ​ 0  |  No  | +
-|  8 MHz  |  ​5 MHz  ​| ​ 1  |  Yes  | +
-|  ​8 MHz  ​| ​ 8 MHz  |  0  |  No  | +
-|  10 MHz  |  5 MHz  |  2  |  No  | +
-|  10 MHz  |  8 MHz  |  1  |  No  |+
  
-The photos below show the jumper configurations for 01, and 2 wait states.+^Z80 Clock Speed (U46)^8255 Rated Speed^# of I/O Wait States^Tested?​| 
 +|  4 MHz  |  5 MHz  |  ​ ​| ​ Yes  | 
 +|  4 MHz  |  8 MHz  |  0  |  Yes  | 
 +|  8 MHz  |  5 MHz  |  **1**  |  Yes  | 
 +|  8 MHz  |  8 MHz  |  0  |  Yes  |
  
-FIXME Add photos FIXME+**Note:** Operation of the Z80 SBC at 10 MHz was **not successful** during ZSOS development - the ROM Monitor would not come up, even with multiple combinations of RAM, I/O, and ROM wait states tested. ​ This is consistent with John M's comments in the '​Running the Board at 8MHz' section of his [[http://​www.s100computers.com/​My%20System%20Pages/​SBC%20Z80%20Board/​SBC%20Z80%20CPU%20Board.htm|write-up at S100Computers.com]] that 10 MHz operation is unreliable. 
 + 
 +Jumper configuration for 0 I/O wait states: 
 + 
 +{{:​software:​firmwareos:​zsos:​0_io_wait_states.jpg?​nolink&​|0_io_wait_states.jpg}} 
 + 
 +Jumper configuration for 1 I/O wait state: 
 + 
 +{{:​software:​firmwareos:​zsos:​1_io_wait_state.jpg?​nolink&​|1_io_wait_state.jpg}}
  
 === IOBYTE DIP Switchs === === IOBYTE DIP Switchs ===
-The configuration of the IOBYTE DIP switches is often a point of confusion for users of this board. ​ The bits which are controlled by the DIP switches are attached to '​pull-up'​ resistor, and the switches connect to ground. ​ So an open/off switch produces a '​1'​ bit in the IOBYTE, and a closed/on switch produces a '​0'​ bit in the IOBYTE. 
  
-The short explanation is:  +The configuration of the IOBYTE DIP switches is often a point of confusion for users of this board. The bits which are controlled by the DIP switches are attached to '​pull-up'​ resistor, and the switches connect to ground. So an open/off switch produces a '​1'​ bit in the IOBYTE, and a closed/on switch produces a '​0'​ bit in the IOBYTE. 
-  * Bits are numbered from the right side (0) to the left (7).  The left 2 DIP switches are not connected to anything, those bits are used instead as the status bits for the DLP USB->Serial adapter.+ 
 +The short explanation is: 
 + 
 +  * Bits are numbered from the right side (0) to the left (7). The left 2 DIP switches are not connected to anything, those bits are used instead as the status bits for the DLP USBSerial adapter.
   * Only bits 5, 1, and 0 are currently in use by SBC Monitor (2.3) and ZSOS (0.30).   * Only bits 5, 1, and 0 are currently in use by SBC Monitor (2.3) and ZSOS (0.30).
-  * The default configuration set by the pull-up resistors (all DIP switches open/off) uses the Propeller Console Board as the console. +  * The default configuration set by the pull-up resistors (all DIP switches open/off/'​1'​) uses the Propeller Console Board as the console. 
-  * Setting Bit 5 to closed/on '​enables'​ Bit 1 and Bit 0 +  * Setting Bit 5 to closed/on/'​0' ​'​enables'​ Bit 1 and Bit 0 
-    * Setting Bit 0 to closed/on re-directs console to the DLP USB->Serial adapter +      * Setting Bit 0 to closed/on/'​0' ​re-directs console to the DLP USBSerial adapter 
-    * Setting Bit 1 to closed/on re-directs console to the DLP USB->Serial adapter +      * Setting Bit 1 to closed/on/'​0' ​re-directs console to the DLP USBSerial adapter
-The photos below illustrate some possible combinations.+
  
-FIXME Add photos ​FIXME+The photos ​below illustrate the switch numbering and some possible combinations.
  
-The operation of the DIP switches is different between the SBC Monitor ROM and ZSOS.  The SBC Monitor always respects the DIP switch positions. ​ ZSOS reads the DIP switches during boot and sets an initial mapping of BIOS routines for the separate physical ''​USBSER:''​ and ''​PRPCON:''​ devices to the logical ''​CON:''​ CP/M 3 console. The CP/M 3 DEVICE utility can be used to remap the console input and output between devices from the CP/M 3 prompt - for example it is possible to boot with the SBC Monitor and initial ZSOS prompt on the DLP USB->Serial device, then run DEVICE and re-map to the Propeller Console board on the fly without rebooting. ​ This is an example of the flexibility of CP/M 3 which allows for many physical character I/O devices to be defined and re-mapped to the logical devices by the user from the command prompt. ​ Note that any remapping done with the DEVICE utility is lost on the next reboot.+{{:​software:​firmwareos:​zsos:​iobyte_dip_numbering.png?​nolink&​}} 
 + 
 +{{:​software:​firmwareos:​zsos:​iobyte_bit5_open_.png?​nolink&​}} 
 + 
 +{{:​software:​firmwareos:​zsos:​iobyte_bit5_closed_1.png?​nolink&​}} 
 + 
 +{{:​software:​firmwareos:​zsos:​iobyte_bit5_closed_2.png?​nolink&​}} 
 + 
 +The operation of the DIP switches is different between the SBC Monitor ROM and ZSOS. The SBC Monitor always respects the DIP switch positions. ZSOS reads the DIP switches during boot and sets an initial mapping of BIOS routines for the separate physical ''​USBSER:'' ​ and ''​PRPCON:'' ​ devices to the logical ''​CON:'' ​ CP/M 3 console. The CP/M 3 DEVICE utility can be used to remap the console input and output between devices from the CP/M 3 prompt - for example it is possible to boot with the SBC Monitor and initial ZSOS prompt on the DLP USBSerial device, then run DEVICE and re-map to the Propeller Console board on the fly without rebooting. This is an example of the flexibility of CP/M 3 which allows for many physical character I/O devices to be defined and re-mapped to the logical devices by the user from the command prompt. Note that any remapping done with the DEVICE utility is lost on the next reboot.
  
 ==== CompactFlash Card Preparation ==== ==== CompactFlash Card Preparation ====
 +Click on the thumbnails below to see screenshots of this process.
   - Download the latest ZSOS image from the main ZSOS wiki page.   - Download the latest ZSOS image from the main ZSOS wiki page.
-  - Unzip the zip file+  - Unzip the zip file.
   - Insert CF card into a USB card reader and attach to modern computer'​s USB port   - Insert CF card into a USB card reader and attach to modern computer'​s USB port
-  - Download the '​Etcher'​ software from [[https://​etcher.io/​]]. ​ This is a cross-platform software for writing images to flash media such as CF, SD, etc.  It limits the devices that it will flash to to removable devices to avoid accidentally overwriting operating system drives, etc.+  - Download the '​Etcher'​ software from [[https://​etcher.io/​|https://​etcher.io/​]]. This is a cross-platform software for writing images to flash media such as CF, SD, etc. It limits the devices that it will flash to to removable devices to avoid accidentally overwriting operating system drives, etc.
   - Run the Etcher software (note - Etcher often takes a few seconds to load and appear even on fast PCs.)   - Run the Etcher software (note - Etcher often takes a few seconds to load and appear even on fast PCs.)
-    ​- Select the image to be written, either the '​banked'​ or '​unbanked'​ .img file +      ​- Select the image to be written, either the '​banked'​ or '​unbanked'​ .img file. 
-    - An error message will appear that this does not appear to be a bootable image. ​ Etcher does not know about the format of this CP/M image, so click '​Continue'​. +      - An error message will appear that this does not appear to be a bootable image. Etcher does not know about the format of this CP/M image, so click '​Continue'​. 
-    Select ​the drive to be written to +      '​Change'/​select ​the drive to be written to with green check marks 
-    - Click the '​Flash'​ button - see screenshots below +      - Click the 'Flash!' button 
-    - After flashing is complete, close '​Etcher'​ software+      ​After the flash is completed, a screen will be displayed showing that it was successful. 
 +      - After flashing is complete, close '​Etcher'​ software
   - Eject/​unmount USB drive and remove CF card   - Eject/​unmount USB drive and remove CF card
  
-FIXME Add photos FIXME+{{:​software:​firmwareos:​zsos:​etcher_select_image.png?​direct&​200|Select image file}}{{:​software:​firmwareos:​zsos:​etcher_click_continue.png?​direct&​200|Click '​continue'​}}{{:​software:​firmwareos:​zsos:​etcher_select_drive.png?​direct&​200|Click '​Change'​ to select drives}}{{:​software:​firmwareos:​zsos:​etcher_drive_checked.png?​direct&​200|Check drives to flash}}{{:​software:​firmwareos:​zsos:​etcher_flash.png?​direct&​200|Click '​Flash'​}}{{:​software:​firmwareos:​zsos:​etcher_flash_complete.png?​direct&​200|Flash successful!}}
  
 ==== First Boot ==== ==== First Boot ====
-At this point, make sure your S100 system is turned off, insert the CF card in the CF->IDE adapter, and boot it up.  When the SBC Monitor prompt has loaded, the '​P'​ command should boot into ZSOS.  A screenshot of the boot process is shown below. 
  
-FIXME Add photos FIXME+At this point, make sure your S100 system is turned off, insert the CF card in the CF→IDE adapter, and boot it up. When the SBC Monitor prompt has loaded, the '​P'​ command should boot into ZSOS. Click the thumbnail below to see a screenshot of a successful boot.
  
-For users who are new to CP/M 3, the CP/M 3 User's Guide is an extremely useful referenceFIXME Add file/link FIXME+{{:​software:​firmwareos:​zsos:​zsos_firstboot.png?​direct&​200|}}
  
-===== Adding additional files to the image =====  +==== CP/M 3 Manuals ​====
-FIXME Update for 0.30 FIXME +
-To add additional files to the image in User Area 8 and/or 9:+
  
-  ​WindowsAdd the files to be added the folders '​8'​ and/or '9'​. ​Run '​addusersfiles.bat+The following CP/M 3 manual are available. ​ Recommended for new users: 
-  * LinuxEnsure you have the cpmtools package installedAdd the text in the diskdef-s100ide file to the top of the file /​etc/​cpmtools/​diskdefsAdd the files to be added to the directories '​8'​ and/or '​9'​. Run '​adduserfiles.sh'​.+  ​{{:software:​firmwareos:​zsos:​cpm3_users_guide.pdf|CP/M 3 User's Guide}} 
 +  * {{:​software:​firmwareos:​zsos:​cpm3_command_guide.pdf|CP/M 3 Command Guide}} ​  
 +Recommended for advanced users: 
 +  * {{:​software:​firmwareos:​zsos:​cpm3_programmers_guide.pdf|CP/M 3 Programmer's Guide}} 
 +  * {{:software:​firmwareos:​zsos:​cpm3_system_guide.pdf|CP/M 3 System Guide}} 
 +These manuals are also included ​in the ZSOS .zip distribution.
  
-A new files named '​zsos-0.10-02feb2016-extended.img'​ will be created. ​Write this image to a CF card. +===== Adding additional ​files to the image ===== 
 + 
 +Additional files can be added to the image in User Area 8 and/or 9 by following the procedure below. ​ For the purposes of this procedure, the '​version string'​ of the image is in the form ''​zsos-x.yy'',​ where ''​x.yy''​ is the version number of the image. For ZSOS v0.30, the version string would be ''​zsos-0.30''​. 
 + 
 +  * Windows 
 +    * Copy the files to be added to the CF card image to the folders '​8'​ and/or '​9'​ within the unzipped ZSOS distribution folder.  
 +    * Open the Windows Command Prompt  
 +    * Change directories to the unzipped ZSOS distribution folder 
 +    * Run '​addusersfiles.bat'​ with the '​version string'​ as a parameter. ​ For example, for ZSOS v0.30, the command to run would be <​key>''​adduserfiles zsos-0.30''</​key>​ 
 +  * Linux 
 +    * Ensure you have the cpmtools package installed.  
 +    * Add the text in the diskdef-s100ide file to the top of the file /​etc/​cpmtools/​diskdefs.  
 +    * Copy the files to be added to CF card image to the directories '​8'​ and/or '​9'​ within the unzipped ZSOS distribution directory.  
 +    * Open a bash terminal 
 +    * Change directories to the uzipped ZSOS distribution directory.  
 +    * Run '​adduserfiles.sh'​ with the '​version string'​ as a parameter. ​ For example, for ZSOS v0.30, the command to run would be <​key>''​./​adduserfiles.sh zsos-0.30''</​key>​ 
 + 
 +New files named '''​zsos-x.yy-banked-extended.img'''​ and ''​zsos-x.yy-nonbanked-extended''​' will be created. ​Select either the nonbanked or banked ​image and proceed with the instructions above for writing ​to a CF card.
  
 ===== Where to get additional CP/M Software ===== ===== Where to get additional CP/M Software =====
 +
 There is a huge archive of CP/M software at [[http://​www.classiccmp.org/​cpmarchives/​|http://​www.classiccmp.org/​cpmarchives/​]] There is a huge archive of CP/M software at [[http://​www.classiccmp.org/​cpmarchives/​|http://​www.classiccmp.org/​cpmarchives/​]]
  
 ===== References ===== ===== References =====
 +
   * [[http://​www.s100computers.com/​My System Pages/SBC Z80 Board/SBC Z80 CPU Board.htm|S100Computers.com Z80 SBC]]   * [[http://​www.s100computers.com/​My System Pages/SBC Z80 Board/SBC Z80 CPU Board.htm|S100Computers.com Z80 SBC]]
   * [[http://​www.s100computers.com/​Software Folder/​Altair Simmulator/​Altair Software.htm|S100Computers.com AltairZ80 Simulator Description]]   * [[http://​www.s100computers.com/​Software Folder/​Altair Simmulator/​Altair Software.htm|S100Computers.com AltairZ80 Simulator Description]]
Line 148: Line 212:
   * [[http://​www.moria.de/​~michael/​cpmtools/​|cpmtools Homepage]]   * [[http://​www.moria.de/​~michael/​cpmtools/​|cpmtools Homepage]]
   * [[http://​www.cpm8680.com/​cpmtools/​|Wild Turkey cpmtools for Windows]]   * [[http://​www.cpm8680.com/​cpmtools/​|Wild Turkey cpmtools for Windows]]
 +
 +
software/firmwareos/zsos/start.1528615227.txt.gz · Last modified: 2018/06/10 03:20 by admin
Driven by DokuWiki Recent changes RSS feed Valid CSS Valid XHTML 1.0