DOS nodes user manual

The Albireo node supports the Albireo from PulkoTronics.

Caution: be sure that the microSD card as well as USB mass storage you are using are formatted with fat32 ¹⁾.

• SD: Internal microSD card reader.
• UMS: Plugged USB mass storage (USB stick, hard disk…).

Albireo node alters the logical drives default assignation. When persistency is reset²⁾, Albireo node will assign drive A: to SD: and drive B: to UMS:.

Albireo node provides non volatile memory management. The contents of the non volatile memory is stored in a file named “!UNIDOS!.NVM” which is located at the root of the microSD card.

Albireo node cannot rename files from a directory to another, neither on SD: nor on UMS:.

The M4 node supports the M4 Board from Duke.

• M4: Internal microSD card.
• DSK: DSK file reader (read-only).

M4 node alters the logical drives default assignations. When persistency is reset³⁾, M4 node will assign drive B: to M4: (drive A: is left unchanged).

M4 node provides handling for a library of files which are normally used by emulators. It stores disc images (DSK files), cartridges images (CPR files) and snapshots (SNA files). These files are physically located in a directory named “Library” at the root of the microSD card (this directory will be automatically created if it does not already exist).

The Library can contain sub-directories and files with long file name using upper case and lower cas (case is actually ignored when reading files). Moreover, file type recognition is based on their contents and it is not mandatory to keep legacy file extensions.

Additional RSX such as |CPR, |DSK, |SNA will let you use files from the Library, while |HTTPGET provides a way to directly download files to the Library.

M4 node hosts several RSX which let you manage the Library, the built-in ROM board, the WIFI network and other M4 Board configuration status.

Syntax: |CPR,“path to a CPR file from the Library”

Boot a CPR cartridge from the Library like if it was physically plugged to your Amstrad Plus. Please note that the provided path must not include the “Library/” prefix which is automatic.

This command is dedicated to Amstrad Plus and won't work on CPC.

Handle configuration of the physical drive DSK:.

Syntax: |DSK

Display the name of the DSK file from the Library which is currently mounted in the drive DSK:. Please note that the path do not include the “Library/” prefix.

|DSK
Demos/Back2Futurs.dsk

Syntax: |DSK,“path to a DSK file from the Library”

Mount a DSK file from the Library into the physical drive DSK: . Please note that the provided path must not include the “Library/” prefix which is automatic.

|DSK,"Demos/Back2Futurs.dsk"

Syntax: |HTTPGET,“url”

Download a file from an URL to the Library.

List the Library contents.

Syntax: |LIBRARY

List all file from the root of the Library.

|LIBRARY
eDSK: The Insider (UK) (1989) [Original] [UTILITAIRE].dsk
eDSK: SymbOS-CPC-AppsStandard.dsk
eDSK: SymbOS-CPC-BootFast.dsk
eDSK: SymbOS-CPC-BootRaw.dsk
eDSK: Digitracker (UK) (128K) (1993) (PD) [UTILITAIRE].dsk
eDSK: Quasar CPC 3 (1993)(Futurs)(Disk 2 of 2).dsk
[Dir] PlayCity
eDSK: Discology (F) (1989) (CPM) (Version 6.0) [UTILITAIRE].dsk
eDSK: CPM 2.2 - zexall.dsk
[Dir] Jeux
[Dir] Demos
eDSK: Quasar CPC 2 (1993)(Futurs)(Disk 2 of 2).dsk
eDSK: Quasar CPC 3 (1993)(Futurs)(Disk 1 of 2).dsk
eDSK: Quasar CPC 2 (1993)(Futurs)(Disk 1 of 2).dsk
[Dir] Utilitaires
 SNA: Barbarian.sna
 SNA: Take It Easy.sna
 CPR: Batman The Movie.cpr

Syntax: |LIBRARY,“path into the Library”

List the file from the Library which are located in the provided path (the path can contain wildcards). Please note that the provided path must not include the “Library/” prefix which is automatic.

|LIBRARY,"Demos/"
eDSK: Back2Futurs.dsk
eDSK: Climax (2003)(Les Sucres En Morceaux)(Disk 1 of 2).dsk
eDSK: Climax (2003)(Les Sucres En Morceaux)(Disk 2 of 2).dsk
 DSK: Prodatron Megademo (1992)(BENG)(Disk 2 of 2).dsk
eDSK: Tire Au Flan (2002)(Overlanders).dsk
 DSK: ASIC Intro 1 - Plasma Plus (F) (128K) (2000) [CPC+] [DEMO].dsk
eDSK: phX.dsk
eDSK: Still Rising (Offset).dsk
eDSK: The Demo (1991)(Logon System)(Disk 1 of 2).dsk
eDSK: _5KB 3 (1999)(5KB).dsk
eDSK: DTC (UK) (128K) (2006) [DEMO].dsk
 CPR: CRTC3_(Flower Corp_2017).cpr
 CPR: Eerie_Forest_(Logon_System_2017).cpr

Syntax: |M4.DISABLE

Totally disable the M4 Board (including its built-in ROM board) until the next M4 reboot.

This is useful when you need to start a program which is not compatible with the M4 Board.

Syntax: |M4.FLASHROM,“path”,slot

Flash the ROM slot with the contents of the file provided through the path.

Syntax: |M4.NETCONFIG,“configuration”

Configure the M4 Board network. This command is identical to the RSX |NETSET from built-in M4 Board ROM. Please refer to the documentation from Duke.

Syntax: |M4.NETSTAT

Display the network status of the M4 Board. This command is identical to the RSX |NETSTAT from built-in M4 Board ROM. Please refer to the documentation from Duke.

Signal: 0xCE
IP 192.168.0.48
Netmask: 255.255.255.0
Gateway: 192.168.0.254
DNS1: 80.10.246.2
DNS2: 80.10.246.129
MAC: 2C:F4:32:65:38:15

Syntax: |M4.UPGRADE

Update the M4 Board firmware from the internet. This command is identical to the RSX |UPGRADE from built-in M4 Board ROM. Please refer to the documentation from Duke.

Syntax: |M4.VERSION

Display the firmware version of the M4 Board. This command is identical to the RSX |VERSION from built-in M4 Board ROM. Please refer to the documentation from Duke.

M4 v2.0.7
ESP v2.0.7

Syntax: |M4.ROMOFF,slot

Disable the ROM slot from the M4 Board ROM area.

Syntax: |M4.ROMON,slot

Enable the ROM slot from the M4 Board ROM area.

Syntax: |SNA,“path to a SNA file from the Library”

Synchronize the CPC state according to the content of trhe provided SNA file from the Library. Please note that the provided path must not include the “Library/” prefix which is automatic.

M4 node provides non volatile memory management. The contents of the non volatile memory is stored in a file named “!UNIDOS!.NVM” which is located at the root of the microSD card.

M4 node cannot delete non empty directories from M4:.

Error handling is a bit weak compared to other nodes because of M4 Board firmware flaws in this regard.

The FatFs node supports media formatted using FAT⁴⁾.

• IDE: master drive connected to the IDE bus (compatible with X-Mass and Symbiface II).

FatFs node alters the logical drives default assignations. When persistency is reset⁵⁾, M4 node will assign drive B: to IDE: (drive A: is left unchanged).

FatFs node provides non volatile memory management. The contents of the non volatile memory is stored in a file named “!UNIDOS!.NVM” which is located at the root of the drive IDE:.

Please note that the FatFs automatically disables its non volatile memory management when a Nova card is detected.

FatFs node needs to allocate memory to operate. Because of that, it prevents UniDOS from providing the same strong AMSDOS compatiblity than with other nodes. Nervertheless, if you own a Nova, it will automatically use it to avoid main memory usage and ensure a much better AMSDOS compatibility (almost as good as with other nodes).

Because of FatFs being a huge library for a little Z80, this node also have poor performance compare to others. Notably, its non volatile memory management is quite slow. If you own another board supported by UniDOS, always prefer its non volatile memory handling to the one from FatFs node. For instance, usage of the Nova is strongly advised.

The Nova node supports the non volatile memory of the Nova de PulkoTronics.

The Nova node provides no additional physical drives.

The Nova node provides non volatile memory management. The contents of the non volatile memory is stored into the last page of the Nova memory.

Zero node is mainly an example with to real usage.

• ZERO: “Empty” files provider.

This drive is read-only and let you generate on-the-fly files of any size. File size and fill byte are depending on the provided file name. For instance, a file “123.75” will provide a file of 123 bytes with the fill value 75⁶⁾.

Caution: the generated files are ASCII files⁷⁾, you could for instance load them with Protext (INSERT 20.32 will insert 20 spaces⁸⁾ in your currently edited file) or through the |LOAD RSX.

The Zero node does not provide non volatile memory.