Configuration files may be edited using any text editor. Or the PlatoAccess menu item Settings→Connection… may be used. If using the PlatoAccess editor the changes should be saved with File→Save Connection As…
PlatoAccess Configuration Files may have any name but must have a type or extension of .cfg
Example: Reto1Production.cfg
The contents for Retro1Production.cfg:
<?xml version="1.0" standalone='yes'?> <configuration> <session host="cybis.retro1.net" port="8005" mtdisk0="" mtdisk1="" mtboot=""/> </configuration>
The first line is a standard xml header. We need not be concerned about it - it just needs to be there.
<configuration>
and </configuration>
mark the beginning and end of our set of (usually just one) session(s) or connection(s) to a host system (CYBIS).
If more than one session entry is present a connection is opened for each. Those could be the same system or different systems.
<session host=“cybis.retro1.net” port=“8005” mtdisk0=“” mtdisk1=“” mtboot=“”/>
host=“cybis.retro1.net”
gives the internet address of the Cybis system you wish to connect to.port=“8005”
gives the host port used to connect to the host - usually 8005These first two are required but can appear in any order.
mtdisk0=“”
gives the full path of a micro TUTOR virtual disk image file referred to as disk 0.mtdisk1=“”
gives the full path of a micro TUTOR virtual disk image file referred to as disk 1.mtdisk0=””
must be set.These micro TUTOR virtual disk image files have a file type/extension of .mte
<session host="cybis.retro1.net" port="8005" mtdisk0="C:/PlatoAccess/mydisk.mte" mtdisk1="" mtboot="doit"/>