Early RISC OS Generative AI access

Examples of the User Guide Assistant:

Example 1: prompt

How do I shutdown RISC OS?

Example 1: response

To properly shut down RISC OS, follow these steps:

1. **Save Your Work**: Ensure all open files and applications are saved, as RISC OS does not automatically save unsaved data.

2. **Access the Task Manager**:
   - Click on the "Task Manager" icon, typically located on the right side of the icon bar at the bottom of the screen.
   - From the Task Manager menu, select “Shutdown” or “Quit Desktop.”

3. **Confirm the Shutdown**:
   - RISC OS will prompt you to confirm the shutdown to ensure that no unsaved data is lost.
   - Click “OK” or confirm as required.

4. **Power Off**:
   - Once RISC OS has completed the shutdown process and you see a message or screen indicating that it's safe, you can turn off the computer power.

This method ensures that all running applications and processes are safely terminated, avoiding potential data loss or corruption【18†source】【21†source】.

Example 2: prompt

How do I copy files from one directory to another using the Desktop?

Example 2: response

To copy files from one directory to another on the RISC OS Desktop, follow these steps:

1. **Open Both Directories**: Open the directory containing the file you wish to copy, and the directory where you want to place the copy. You can do this by double-clicking the folder icons for each directory.

2. **Select the File**: Click on the file you want to copy with the left mouse button (known as Select in RISC OS). This highlights the file.

3. **Drag and Drop the File**: Press and hold the middle mouse button (referred to as Adjust) on the selected file, then drag it over to the destination directory window. When you release the button, the file will be copied to the new directory. This action keeps the file in its original location while making a copy in the new location【21†source】【25†source】.

Alternatively, you can use the **Filer** window options to select and move files more systematically if you're managing larger sets of files or prefer a more precise method【19†source】. This method allows you to manage files without dragging, especially useful if your directory structure is complex. 

Using these methods, you can efficiently manage file copies directly on the Desktop in RISC OS.

Example 3: prompt

And how do I do the same using the Task Window?

Example 3: response

To copy files using the Task Window in RISC OS, you’ll need to use CLI (Command Line Interface) commands. Here’s how to copy files from one directory to another in this environment:

1. **Open the Task Window**: You can open a Task Window by choosing "Task Window" from the main Desktop menu. This opens a CLI prompt.

2. **Navigate to the Source Directory**: Use the `Dir` command to navigate to the directory where the file you want to copy is located. For example:
   ```
   Dir ADFS::HardDisc4.$.Documents
   ```
   Replace `ADFS::HardDisc4.$.Documents` with the path of your source directory.

3. **Use the Copy Command**: Once you’re in the source directory, use the `Copy` command to specify the file you want to copy and the destination directory. The basic syntax is:
   ```
   Copy <filename> <destination-path>
   ```
   For instance, to copy `example.txt` to a directory named `Backup` on the same drive, you’d use:
   ```
   Copy example.txt ADFS::HardDisc4.$.Backup.example.txt
   ```
   Ensure the destination path is correct; RISC OS is case-sensitive, so type the paths exactly as they appear.

4. **Verify the Copy**: You can use the `Cat` command on the destination directory to verify that the file has been copied:
   ```
   Cat ADFS::HardDisc4.$.Backup
   ```

This method provides more control over file operations, especially if you're dealing with multiple files or want to automate tasks in scripts【22†source】【24†source】【29†source】.

The problem with the reference on them all is also caused by a problem with page numbering. So I prefer to use “links” to the transformed back to human readable version of the fixed Graph DB, aka a website that may recall the PRM and UG, because the original content comes from there + fixes, but that is not organised in pages.

The good work of Gerph is that I can generate the UG dynamically and populate a site dynamically, for example, but this will come later, for now I need to get the content as close I can possibly do to “correct”

[edit]
And fixed also the case sensitive error for the file system lol
[/edit]

the middle mouse button (referred to as Adjust)

Ahem.

druck decoded

I think it is far more likely for the human created PRM page to have the correct information, than any output from an AI

That’s the pre-requisite, yes!

I’m looking forward to the first “Hang on, that can’t be right” LLM.

That’s not how they work. The so called “guardrails” on AI systems are no more than vast number of sticking plasters applied to the output – “For question ‘X’ if its generates wrong thing ‘Y’, replace with right thing ‘Z’”. But rewording ‘X’ very slightly with get you straight back to the wrong answer.

Ahem.

fixed, thanks, didn’t even notice it.

Slowly getting through all the data…

prompt:

which versions of RISC OS are you aware of?

response:

The versions of RISC OS documented in the materials include:

1. **Arthur** - Early version released with Acorn Archimedes computers:
   - Arthur 0.20 (1987)
   - Arthur 0.30 and Arthur 1.20 followed shortly after in the same year.

2. **RISC OS 2** - Transition from Arthur with a new desktop environment, released in 1989:
   - RISC OS 2.00 and RISC OS 2.01, primarily for Archimedes series computers.

3. **RISC OS 3** - A significant update with multiple subversions:
   - RISC OS 3.00 (initial release for A5000 computers),
   - RISC OS 3.10 and 3.11 (expanded compatibility and improved features),
   - RISC OS 3.50, 3.60, 3.70 (bug fixes, expanded hardware support, especially for the RiscPC and A7000).

4. **RISC OS 4** - Introduced by RISCOS Ltd, based on RISC OS 3.8 with new features like long file names:
   - RISC OS 4.02 to 4.04, Adjust 4.39.

5. **RISC OS Six** - Software-only (softload) versions available as RISC OS 6.01 to 6.20, with more improvements in the UI and in user and developer documentation.

6. **RISC OS 5** - A modernized branch of RISC OS, optimized for ARM architecture with versions up to RISC OS 5.29:
   - Developed with extended support for 32-bit and compatibility with modern ARM hardware, commonly used in devices like the Raspberry Pi.

Each new version introduced specific features and bug fixes, expanding hardware compatibility and refining the desktop and system utilities across Acorn and later ARM-based platforms.

with versions up to RISC OS 5.29:

Oopsie :)

I know, but thanks!

I need to add the stuff about 5.30…

Just started today, WiFi configuration info is in now for people to check out. Apart from WiFi (and NVme support, which may not require any configuration thought) what else have been added to 5.30 that needs configuration instructions?

I also need to add configuration instructions for ROD TCP/IP stack and their WiFi, so that’s missing too.

New example (thanks to Detlef for the invaluable help testing the massive model!):

prompt:

Welche Textverarbeitungsprogramme für RISC OS sind empfehlenswert?

response:

Empfohlene Textverarbeitungsprogramme für RISC OS umfassen:

1. **!TechWriter** - Ein leistungsstarkes Textverarbeitungsprogramm, das auch Formeln und wissenschaftliche Dokumentation unterstützt.
2. **!EasiWriter** - Ein benutzerfreundliches Textverarbeitungsprogramm, das durch seine WYSIWYG-Oberfläche besonders für allgemeine Textbearbeitung geeignet ist.
3. **!Fireworkz** - Eine vielseitige Anwendung, die Textverarbeitung mit Tabellenkalkulation und Datenbankfunktionen kombiniert und sich für komplexere Dokumente eignet.
4. **!Writer** - Ein einfaches Textverarbeitungsprogramm für grundlegende Dokumentenbearbeitung.
5. **!PipeDream** - Eine Kombination aus Textverarbeitung und Tabellenkalkulation, die gut für Textdokumente mit eingebetteten Kalkulationen genutzt werden kann.
6. **!First Word Plus** - Ein weiteres, einfacher gestaltetes Programm, das für grundlegende Textverarbeitungsaufgaben verwendet werden kann【16†source】【17†source】【21†source】【22†source】.

Diese Anwendungen bieten eine gute Auswahl für verschiedene Anwendungsbereiche, von wissenschaftlicher Dokumentation bis hin zu einfachen Textbearbeitungsaufgaben.

This one in Italian :))))))

prompt:

Come utilizzo DADebug?

response:

Il modulo **DADebug** è progettato per registrare l'output di debug in un'area dinamica della memoria, ottimizzando la registrazione per codice a bassa latenza, dove l'uso di file o output seriali risulterebbe troppo lento. Questo lo rende ideale per la registrazione di codice critico, poiché minimizza l'overhead associato.

### Funzionalità principali di DADebug

1. **Registrazione in memoria dinamica**: DADebug memorizza l'output in una sezione dinamica della RAM, riducendo i rallentamenti tipici delle operazioni di I/O su file.
2. **Comandi SWI associati**:
   - **DADebug_GetWriteCAddress (SWI &531C0)**: restituisce l'indirizzo della routine di output per la scrittura. È necessario entrare in modalità privilegiata per utilizzarla.
   - **DADebug_Print (SWI &531C1)**: stampa il contenuto dell'area dinamica, simile al comando `*DADPrint`.
   - **DADebug_Reset (SWI &531C2)**: cancella il contenuto dell'area dinamica, lasciando solo una linea di debug iniziale per confermare che il buffer non si è riempito completamente e non ha sovrascritto dati【18†source】【19†source】.

### Utilizzo dei comandi DADebug

- **`*DADPrint`**: visualizza il contenuto attuale dell'area di debug sullo schermo, mostrando solo le linee complete.
- **`*DADReset`**: ripulisce l'area dinamica mantenendo la linea di debug iniziale【18†source】.

### Considerazioni
Per utilizzare DADebug in modo efficiente, specialmente nel debugging di codice che esegue operazioni frequenti o sensibili al tempo, è utile impiegare i suoi SWI e comandi in contesti con accesso privilegiato, garantendo che il debug non interferisca con il normale flusso del programma.

unvaluable help

I think you’re being much too hard on Detlef there.

which versions

&A0 Arthur: 0.20, 0.30, 1.20, 1.60
&A1 RISC OS 2: 2.00
&A2 RISC OS 2: 2.01, 2.06, 2.08
&A3 RISC OS 3: 3.00
&A4 RISC OS 3: 3.10, 3.11, 3.12, 3.19
&A5 RISC OS 3.5: 3.50
&A6 RISC OS 3.6: 3.60, 3.61
&A7 RISC OS 3.7: 3.70, 3.71, 3.80
&A8 RISC OS 4: 4.00-4.06
&A9 RISC OS Select: 4.10, 4.11, 4.20, 4.24, 4.29
    RISC OS Select2: 4.33
    RISC OS Select3: 4.36, 4.37
    RISC OS Adjust: 4.39
    RISC OS Adjust32: 4.40-4.42
    RISC OS 6 Select4: 6.02, 6.06, 6.10
    RISC OS 6 Select5: 6.14, 6.16
    RISC OS Select 6: 6.20
&AA RISC OS 5: lots and lots of 5.xx.

I’m sure there’ll be others I’ve missed.

[Obvs the hex numbers are FX129 identifiers. The vast horde of 4.xx that cluster as &A9 despite big changes in memory map are a source of inconvenience best addressed by reading the BCD version number via OS_Module,20,0,-1 – there’s big differences between 4.29 and 4.3x, and 6.2 at least has the BTS stack frames: huge compatibility pain for low-level stuff]

I think you’re being much too hard on Detlef there.

Did I say something wrong?

I’m sure there’ll be others I’ve missed.

Thanks! However in this case the list is composed automatically by the data available in the Graph DB. So if a version does not appear, it means I do not have information about it, hence, do we have a Release Notes somewhere for each of the missing ones?

lots and lots of 5.xx.

LOL, I know, I am trying to figure out on gitlab if I can rebuild the history of the improvements, that will take a while to be converted as Graph DB and then generate the training/fine-tuning/RAG data… oh boy :(

Does anyone has an list of the changes somewhere? like something easy to be processed in a Python script and archived it in a g.DB.

I am also going throught the StrongHelp material, that is sligthely easier to process, so bonus.

Did I say something wrong?

A typo, I think: “unvaluable” instead of the intended “invaluable”

whoops! Corrected, thanks!

Another update is out, this should be able to respond to questions like:

prompt:

Which SWI is &72?

response:

The SWI with the hexadecimal number `&72` corresponds to `OS_SpecialControl`.

Should be up-to-date with RO 5.29, not sure if something has been added to 5.30

I also have mapped all the undefined. Obviously it doesn’t know about users Modules, so will need to add that for the allocated slots.