plato:env_install:begin_customization

002 - Begin Customization

Once the installation is complete and CYBIS is up and running the process of installing CYBIS R2 may begin.

Pre-Check

  • Perform the following with dtCyber down

The developer package on the ftp site is named 20250326.retro1.red.target.zip and all four of the distributions noted below are available along with this package. The disks directory contains the CYBIS replacement images.

CDC.IO Installation

  • Install by unzipping/untarring into a suitable directory and TEST cdc.io from the developer's FTP site at Retro1.org or from these available packages1):

  • Quick tests:

    • Version:
      • Windows> cdc.io version
      • Linux> ./cdc.io version
      • The Result:

        Package cdc.io Command cdc.io Version 4.0.1.1 End of Function.

    • Banner:
      • Windows> cdc.io banner -t “testing” -c “gothic”
      • Linux> ./cdc.io banner -t “testing” -c “gothic”
      • The Result:

        # # # # # # # ## ## ## # ### # ## #### # # # # ###### ### ##### ###### # # ## ### ### ##### # ### ## # ##### ## #### ## # ## ## ## # ## ## ### ## ## ## ## ## ## # ## ### ## # ## ## ## ## ## ## ### ## ## ## # ## # ## ## ## ## ## # ## # # ## ## # ## # ## ## ## ### # ### ### # ## ## # ### ### ### ### ## ## ### ### ###### ### ## ## ## ## # # ### # # # # ## # #### # # End of Function.

  • Extensive test:
    • Windows> cdc.io c.analyze -c “Path-to-disks-directory”
    • Linux> ./cdc.io c.analyze -c “Path-to-disks-directory”
    • The Result: A VERY long and detailed analysis of the packs and their contents.
  • Preview the list of cdc.io subcommands

In This Article

This article illustrates the path to achieving the following objectives:

  • Modification of the cyber.ini file
  • Replacement of the CYBIS packs
  • Establishment of a “Baseline Backup”
  • Establishment of the “System Group”

2.1 Edit cyber.ini

Sections [cyber] and [manual]

Color Optional

Changing the color, as a visual cue, is a helpful but optional step in this procedure. The color choices configured in these are merely examples.

The console sections are here to illustrate the defaults (commented with a ;) and modified values (as examples).

  1. Add displayName=<something> to differentiate the various interaction points.
  2. Add console=console.windows or console=console.linux and then establish the corresponding section in the ini file.
    1. Example console.windows
      [console.windows]

; fontName=comic sans ms
colorBG=000000
colorFG=00ff00
; fontSmallHeight=15
; fontMediumHeight=20
; fontLargeHeight=30
; fontSmall=8
; fontMedium=12
; fontLarge=24
; scaleX=10
; scaleY=12
; timerRate=100
; widthPX=1100
; heightPX=800
    2. Example console.linux
      [console.linux]

; fontName=lucidatypewriter
colorBG=black
colorFG=green
; fontSmallHeight=15
; fontMediumHeight=20
; fontLargeHeight=30
; fontSmall=8
; fontMedium=12
; fontLarge=24
; widthPX=1100
; heightPX=800
  3. Add the following lines to the configuration [equipment.nos287]:
    DD885,0,3,03,disks/DQ26_RTR1
DD885,0,3,04,disks/DQ27_GEN1
  4. Optional consider commenting out the helpers that you don't need.

2.1.1 Replace the CYBIS Disks

Before Proceeding

Double-check that you have a valid backup as recommended in the previous step.

Replace the following packs in directory ./disks using the ones downloaded above:

  • DQ20_BINARY
  • DQ21_CYB0
  • DQ22_CYB1
  • DQ23_PUB0
  • DQ24_PUB1
  • DQ25_UOL

Two additional packs are included in this distribution:

  • DQ26_RTR1
  • DQ27_GEN1

These disks contain the new structures which support Y2K fixes, system corrections, revived lessons, and hundreds of other enhancements.

2.1.2 Create Baseline Backup

Using cdc.io's c.backup subcommand, back up the entire PLATO structure to a target directory. Because the structure will be maintained by git, it is recommended that the structure be targeted OUTSIDE of the dtCyber project location.

cdc.io c.backup -c "Path-To-Cluster" -b "Path-to-Backup-Location"

By taking a backup NOW - many future hours can be saved if a problem arises.

2.1.3 Establish Group 's'

The CYBIS/R1 system (as distributed) had a version of Group s that was properly configured for system development users. These records, once established, formed the baseline for systems person.

CYBIS/R2 is distributed without a standard Group s file to give the hobbyist the option of copying over their own file into the new system. If the hobbyist wants to start with a fresh installation of the Group s file, one is supplied on the system and may be activated by issuing the cdc.io c.pfrename command:

cdc.io c.pfrename -c "Path-To-Cluster" hobbyist s

This will activate the Group s file with the following records and passwords:

  • admin/s/passme
  • admin1/s/passme
  • admin2/s/passme
  • admin3/s/passme

If you wish to COPY the Group s file from an existing installation, you may use the following cdc.io c.pfcopy subcommand:

cdc.io c.pfcopy -I "Path_to_Origin_Cluster" -O "Path_to_Target_Cluster" -f "system.s@system" -t "system.s@system"

This command tells cdc.io to copy the file from the Origin Cluster to the Target Cluster with a -from Cluster File Specification of system.s@system (Group system File s on PLATO pack system) -to system.s@system (Group system File s on PLATO pack system).

CDC.IO

The command above performs a SIMULATION of what would happen including the simulation of all I/O Operations. To physically commit the changes, you must supply the -W (WRITE) option switch between cdc.io c.pfcopy and -I “….

Success

If everything completes successfully - you may now proceed!

003 - Deadstart New Disks

1)
Unzip the contents to a folder and add it to your path for convenience.
  • plato/env_install/begin_customization.txt
  • Last modified: 2026/01/03 18:34
  • by Site Administrator