DOS nodes user manual

Albireo DOS node

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 1).

Physical drives

  • 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 reset2), Albireo node will assign drive A: to SD: and drive B: to UMS:.

Non volative memory

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.

Limitations

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

M4 DOS node

The M4 node supports the M4 Board from Duke.

Physical drives

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

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

The Library

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.

RSX

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.

|CPR

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.

|DSK

Handle configuration of the physical drive DSK:.

Without parameter

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
With one parameter

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"

|HTTPGET

Syntax: |HTTPGET,“url”

Download a file from an URL to the Library.

|LIBRARY

List the Library contents.

Without parameter

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
With one parameter

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

|M4.DISABLE

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.

|M4.FLASHROM

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

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

|M4.NETCONFIG

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.

|M4.NETSTAT

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

|M4.UPGRADE

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.

|M4.VERSION

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

|M4.ROMOFF

Syntax: |M4.ROMOFF,slot

Disable the ROM slot from the M4 Board ROM area.

|M4.ROMON

Syntax: |M4.ROMON,slot

Enable the ROM slot from the M4 Board ROM area.

|SNA

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.

Non volatile memory

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.

Limitations

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.

FatFs DOS node

The FatFs node supports media formatted using FAT4).

Physical drives

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

Non volatile memory

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.

Limitations

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.

Nova node

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

Physical drives

The Nova node provides no additional physical drives.

Non volatile memory

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 DOS node

Zero node is mainly an example with to real usage.

Physical drives

  • 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 756).

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

Non volatile memory

The Zero node does not provide non volatile memory.

1)
neither ntfs nor other fat types are supported by the Albireo
2) , 3) , 5)
while keeping CONTROL key pressed during boot
4)
FAT12, FAT16 et FAT32
6)
if no extension is provided then the fill value is 0
7)
without AMSDOS binary header
8)
the ASCII code 32 is the space