|
|
**AlbiDOS is the DOS driver for MicroSD card reader and USB mass storage of the Albireo expansion card from PulkoTronics.**
|
|
|
|
|
|
It provides as much as possible a backward compatiblity with default AMSDOS ROM. Then, it matches all AMSDOS and Firmware cassette manager APIs and you should simply rely on AMSDOS and Firmware documentation.
|
|
|
It provides as much as possible a backward compatibility with default AMSDOS ROM. Then, it matches all AMSDOS and Firmware cassette manager APIs and you should simply rely on AMSDOS and Firmware documentation.
|
|
|
|
|
|
Anyway, a few additional things are available and are explained here after.
|
|
|
Anyway, a few additional things are available and are explained below.
|
|
|
|
|
|
Additionally, do not hesitate to come and chat with us at [#cpc](https://webchat.freenode.net/#cpc) or [#cpc-fr](https://webchat.freenode.net/#cpc-fr) (freenode IRC network).
|
|
|
|
|
|
**Installation:**
|
|
|
- AlbiDOS can work in any ROM slot but, for a better experience, it should always be in a slot with a lower number than AMSDOS or other compatible DOS (such as iMPdos).
|
|
|
- AlbiDOS can work in two different modes (the current mode is displayed at boot screen):
|
|
|
- Integrated: AMSDOS was found in a higher slot number and all fallback and compatibility mecanism are installed.
|
|
|
- Integrated: AMSDOS was found in a higher slot number and all fallback and compatibility mechanism are installed.
|
|
|
- Standalone: AMSDOS was not found an AlbiDOS will just handle Albireo drives (no fallback is possible).
|
|
|
- AlbiDOS can also be installed in ROM slot 7 for maximum compatibility (some old softwares are relying directly on ROM slot 7 to handle DOS instead of using system-friendly way). In that case you should install AMSDOS to slot 15 to ensure its memory allocation is always &A700 (also for maximum compatibility). Any additional AMSDOS compatible DOS (such as iMPdos) should be then installed between 7 and 15 (to take advantage of AlbiDOS RSX passthrough feature).
|
|
|
- This is the better way to have softwares which are manually initializing ROM 7 as DOS to work on MicroSD card or USB stick through AlbiDOS.
|
... | ... | @@ -18,37 +18,37 @@ Additionally, do not hesitate to come and chat with us at [#cpc](https://webchat |
|
|
|
|
|
**Using drives and path:**
|
|
|
- AlbiDOS handles file path in all API provided with a filename.
|
|
|
- Basic LOAD"path" command (as well as OPENIN"path" or RUN"path") can be used for navigation in the file system it select the current media and directory).
|
|
|
- Basic SAVE"dir/" command (as well are OPENOUT"dir/") can be used to create a directory "dir" in the current path.
|
|
|
- Basic LOAD"path" command (as well as OPENIN"path" or RUN"path") can be used for navigation in the file system, it selects the current media and directory).
|
|
|
- Basic SAVE"dir/" command (as well as OPENOUT"dir/") can be used to create a directory "dir" in the current path.
|
|
|
- Paths are formed this way: [DEVNAME:][path/]file. Where DEVNAME can be either a logical drive or a DOS device name.
|
|
|
- Logical drives are A and B (user number can be appened like with AMSDOS but with no effect on non-AMSDOS devices). By default A points to the MicroSD card and B to the USB Mass Storage device.
|
|
|
- Logical drives are A and B (user number can be appended like with AMSDOS but with no effect on non-AMSDOS devices). By default, A points to the MicroSD card and B to the USB Mass Storage device.
|
|
|
- DOS device names are:
|
|
|
- SD for the MicroSD card.
|
|
|
- UMS for the USB Mass Storage device.
|
|
|
- DFA for the floppy disc A.
|
|
|
- DFB for the floppy disc B.
|
|
|
- SD for the MicroSD card,
|
|
|
- UMS for the USB Mass Storage device,
|
|
|
- DFA for the floppy disc A,
|
|
|
- DFB for the floppy disc B,
|
|
|
- TAPE for the tape.
|
|
|
- Path can have up to 8 directories in depth: dir1/dir2/.../dir7/dir8.
|
|
|
- ":" is referencing the root of the current (or predecessing) drive.
|
|
|
- ":" is referencing the root of the current (or preceding) drive.
|
|
|
- LOAD":" go back to root for current path.
|
|
|
- LOAD":file": open file at the current drive root.
|
|
|
- "/" is referencing the parent directory.
|
|
|
- LOAD"/": go to parent directory for current path.
|
|
|
- LOAD"/file": open file at the parent directory from the current path.
|
|
|
- LOAD"dirA1/dirB1//dirA2/file" is equivalent to LOAD"dirA2/file".
|
|
|
- LOAD"DEVNAME:" selects de provided DEVNAME as the media associated with the current drive.
|
|
|
- LOAD"DEVNAME:" selects provided DEVNAME as the media associated with the current drive.
|
|
|
- AlbiDOS retains the current active disc ROM (AMSDOS or AlbiDOS), current drive (A or B), current media selected for each drive, and path so that you will get them back at next reboot. This information is stored in a file named !ALBIREO.CFG at root of MicroSD card.
|
|
|
- |DISC then reboot: you will reboot using current floppy drive by default (could be A or B).
|
|
|
- |DOS then reboot: you will reboot using current Albireo drive by default (could be A or B).
|
|
|
- LOAD"dir1/dir2" then reboot, the default path will remain dir1/dir2.
|
|
|
|
|
|
**Integration with other DOS:**
|
|
|
- AlbiDOS integrates a passtrough for RSX and BIOS vectors, which means that when it is not ativated (for instance after a |DISC was issued or when another DOS took over read/write indirections), it will just pass commands to this ROM in a transparent manner.
|
|
|
- AlbiDOS integrates a passthrough for RSX and BIOS vectors, which means that when it is not activated (for instance after a |DISC was issued or when another DOS took over read/write indirections), it will just pass commands to this ROM in a transparent manner.
|
|
|
- |DOS activates AlbiDOS.
|
|
|
- |DISC, |DISC.IN, |DISC.OUT calls are wrapped to the next ROM implementing them (which is usually AMSDOS, but which could also be RODOS or any DOS ROM dealing with disc drives).
|
|
|
- |TAPE, |TAPE.IN and |TAPE.OUT are installing back firmware tape read/write indirections.
|
|
|
- All other RSX will be redirected the ROM owning read/write indirections (it ensures that |ERA, |REN, |DIR, and so on will always be used from the proper ROM).
|
|
|
- Relevant CTRL x BIOS vectors will be exclusively redirected to the AMSDOS ROM when it owns indirections (whereever it is located, not necessary in slot 7).
|
|
|
- Relevant CTRL x BIOS vectors will be exclusively redirected to the AMSDOS ROM when it owns indirections (wherever it is located, not necessary in slot 7).
|
|
|
|
|
|
**New file types**
|
|
|
- AlbiDOS handles two new file binary types:
|
... | ... | @@ -68,7 +68,7 @@ Additionally, do not hesitate to come and chat with us at [#cpc](https://webchat |
|
|
- With one parameter it works exactly like with AMSDOS.
|
|
|
- With two parameters, it let you select which media to attach to a drive.
|
|
|
- |REN,"new file or directory name","path to file or directory to rename": now a full path to the file to rename can be given. Please note that the new file name shall still be a stock file name (|REN cannot be used to move files).
|
|
|
- |ERA,"pattern to file or directory": now a full path to the file to delete can be given and confirmation is asked on directories and read-only files (note that erasing a symbolic link will actually delete the link itsel, not its target).
|
|
|
- |ERA,"pattern to file or directory": now a full path to the file to delete can be given and confirmation is asked on directories and read-only files (note that erasing a symbolic link will actually delete the link itself, not its target).
|
|
|
- |DIR,"pattern": patten can now include a path.
|
|
|
|
|
|
**New RSX:**
|
... | ... | @@ -154,6 +154,6 @@ Nothing special. |
|
|
- During catalog display:
|
|
|
- Sizes display switches automatically between KB, MB, GB or TB depending on the actual size.
|
|
|
- Directories are marked [DIR] instead of putting the size.
|
|
|
- Indication about read-only directories is skipped because of compatiblity limitation in buffer storage (you need to use |INFO or |DIR to see this information).
|
|
|
- Indication about read-only directories is skipped because of compatibility limitation in buffer storage (you need to use |INFO or |DIR to see this information).
|
|
|
|
|
|
|